Hacker News discussion: https://news.ycombinator.com/item?id=47267947
Primary source: RFC 406i / 406.fail

Hacker News pushed a humorous but pointed document to the front page this week: RFC 406i, “The Rejection of Artificially Generated Slop.” The page proposes a standardized link that maintainers can drop into closed pull requests, bug reports, and forum threads when a submission looks like low-effort AI output. The joke format is exaggerated on purpose, but the complaint underneath it is very real.

What RFC 406i is reacting to

Confident but unverified fixes that do not match the codebase.
Hallucinated APIs, fake libraries, and generic boilerplate.
Long explanations and polished tone that make review slower instead of easier.

The document argues that the cost is asymmetric. Generating a speculative AI patch is cheap; proving that it is wrong still consumes maintainer time. That is why the page frames rejection as boundary-setting rather than debate. Instead of asking reviewers to clean up machine output, it pushes the responsibility back to the submitter to read the actual code, reproduce the problem, and validate the change manually.

Even if you ignore the satire, the engineering lesson is useful. AI-assisted contribution is only credible when the human operator can explain the architecture, narrow the bug, and show evidence that the fix works. Otherwise, repositories turn into unpaid validation queues for generated text. That is the tension this HN thread captured so well: open source wants help, but not at the cost of replacing contribution with review spam.

#ai-generated-code

RFC 406i proposes a standard rejection link for low-effort AI pull requests