Skip to content

Playbooks · Accountability

The No AI Slop manifesto makes owning your AI output the job

Engineers at AIE Code Summit 2026 define slop as work that costs the reader more than the sender, and make owning what you ship the core skill.

by ·4 min read·

New here? Start with the free AI Survival Kit →

The No AI Slop manifesto makes owning your AI output the job

0:00 / 6:01

This voice is generated by AI.

Part of the guide Your employer is grading your AI use. What to do before the next review

The No AI Slop manifesto makes owning your AI output the job

This week the speakers and attendees of AIE Code Summit 2026 published "No AI Slop: A Manifesto" at slopmanifesto.com. They modelled it on the Agile Manifesto, which 17 software engineers and leaders drafted at a ski lodge in Snowbird, Utah, in 2001. The new document sets out five values: "Outcomes over output", "Understanding over speed", "Our own thinking over a model's first draft", "Better work over easier work" and "Improving the system over patching the output". Dex Horthy, Philip Kiely and Kent C. Dodds are among the signatories. Its working definition is the part that matters for anyone using AI at work: "Slop is when we put less effort into producing something than we ask the consumer to spend understanding it."

That definition says nothing about whether AI touched the work. It measures who pays. The manifesto spells this out: "Using AI doesn't necessarily make something slop. Slop happens when we pass AI output along without taking responsibility for the quality or the reader's experience."

The cost has moved to the reader

The authors lay out the economics plainly. "The cost of producing a thousand-line PR or a ten-page doc is approaching zero, while the cost of reviewing it remains constant." They add that "a swarm of agents can produce more work in a single day than a person can review in our lifetime."

This is an attention story. Production is cheap now and review is the bottleneck. Every unreviewed document a colleague forwards spends someone else's hours. The manifesto's first resolution names the asset directly: "Human time and attention is incredibly valuable."

It also names one of the causes. "A lot of slop comes from pressure. Companies are pushing their people to redefine what is humanly possible." And the damage builds on itself: "The more slop sits in our knowledge base, in chat, in code, the more of it the next agent reads and copies." A team that floods its own systems with unchecked output makes every later agent worse.

Judgement is the part that keeps its value

The sentence an operator should keep is this one: "AI cannot replace human judgement, it can only amplify our judgement (or lack thereof)." AI does the routine work. You do the thinking. The manifesto puts that into a working rule: "We own the intent, taste, and consequences of what we ship, however much AI helps us make it."

The authors also explain why review is a source of leverage. "There will always be alpha in reviewing something." They state the future of code review with care: "As models improve, we may stop reading most of the code. We may still review a plan, design, or result." The reason they give for reviewing at all: "because if we don't, we just get the same output as everyone else." The person who reviews ends up with a different output from everyone running the same model, and that difference is worth paying for.

The manifesto is just as direct on measurement. What shipped, who is using it and how it helps them "matters FAR MORE than lines of code, prs merged, tokens spent, or the number of agents running in parallel." Those vanity counts are the ones a team reaches for when it wants to look busy with AI.

Your Next Move

Run the effort test before you send. Ask the manifesto's question of every AI-assisted document, pull request or message: will the reader spend longer understanding this than you spent producing it? If the answer is yes, cut it down, summarise it at the top, or hold it back until you have read it yourself.

Label agent work and check what matters. Take the manifesto's rule as your own: when an agent wrote something you are sending, say so, and check the parts that carry the stakes before it goes out. When a mistake shows up twice, turn it into an automated check so your attention goes where only judgement will do.

Report outcomes at your next review. Drop counts of prompts, tokens and pull requests from your updates. Write down what shipped, who uses it and what it changed for them. If your employer already scores AI use, our guide on showing impact when your employer grades your AI use sets out how to make that case before the next review cycle.

I build systems like the one publishing this site. → Work with me

About the author

Jo

Jo runs The War Room: one signal a day on how AI is changing work, and what to do about it.

Sources

Get the Briefing

Want more intelligence like this?

The weekly briefing, free — and the AI Survival Kit with it.

Takes 30 seconds. No spam.

More in Playbooks

See all