Nestor G Pestelos Jr · Writing · Print

The Meat Proxy Problem

Published August 19, 2026. Revised September 3, 2026.

TL;DR

Forwarding an AI's answer unread, with nothing else checking the claim, severs accountability. Telling people to validate output will not fix that. Review culture already rubber-stamps real code. The fix has to survive the same incentives.

The August 19, 2026 version is at meat-proxy-problem-20260819.

Niklas Gruhn coined the term "meat proxy" for a specific failure mode: pasting unread AI output into Slack, pull requests, or email. The person who clicks forward acts as a passive conduit. Someone else trusts the sender stands behind the text.

Gruhn's remedy is direct: read it, understand it, validate it, and state it in your own words. But "review it more carefully" was the standard advice for human-written code too. That review culture was already failing before LLMs arrived.

Why it happens

Polish hides uncertainty. A February 2026 breakdown of Anthropic's product data found that finished-looking AI output makes people less likely to double-check it. Users caught fewer missing-context problems and questioned reasoning less when an answer arrived formatted and complete. A rough draft prompts scrutiny. A clean explanation invites a quick click.

The author as first reviewer

Will Larson describes this as establishing the author as the first human in the loop. Whoever generates text with an AI must verify the claims before anyone downstream sees them. Skipping that step turns the recipient into the first real reviewer. At scale, unverified output creates a false foundation. Teams can spend weeks solving problems that do not exist because the initial memo invented a constraint.

Cindy Sridharan sets a strict standard for code: understand close to 100% of the production code an LLM generates. Weak understanding produces vague prompts. Vague prompts yield fragile code. That fragile code becomes harder to understand on the next cycle.

When independent checks exist

Peter Steinberger ships production code he never reads, relying on tests and observability. In contrast, Yaçine MTB's team stopped doing code review entirely, arguing that AI agents catch mistakes during generation.

The two practices are not equivalent. Steinberger's automated tests, compilers, and runtime dashboards run independently of the model that wrote the code. Yaçine's agents reviewing sibling agents do not provide that separation. You can delegate reading only when an external verification harness exists. A paraphrased summary in a Slack thread has no test suite.

Some model output is directly checkable: code that executes, arithmetic that balances, citations that resolve to real pages. Other output resists mechanical testing: architectural advice, strategic summaries, and open-ended commentary. Verify the first kind against tooling before forwarding. Refuse to forward the second kind unread.

The part exhortation cannot fix

Larson's rule and Sridharan's rule are personal appeals, not structural incentives. Software teams already proved that appeals collapse under deadline pressure. On r/ExperiencedDevs, an engineer described a pull request that sat unreviewed for two days, then received an approval click within sixty seconds of a direct message nudge. A 2025 Journal of Systems and Software study surveyed developers at a mid-sized company; respondents reported that reviewers avoid or superficially skim large patches.

When "did CI pass? click approve" became the default habit for human code, "read the AI's explanation carefully" became another ignored instruction. Exhortation fails because organizations reward velocity over inspection.

The personal operational line

I run personal work under a strict constraint: agent output remains marked unverified until independent tooling confirms it. Forwarding uninspected text signs your name to an unverified guess.

This rule is personal discipline, not an organizational fix. The test remains simple: would you defend this claim in your own voice if it turned out wrong? If not, you were just the pipe.

Sources

Back to top