When should you use it?
- You are about to hand a bigger job to an agent
- Numbers keep appearing without sources
- You want to stop re-checking every click yourself
Not for: Accepting a polished summary with no artifacts; Letting the agent invent screenshots or links; Skipping the guesses list because the answer sounded sure
What do you need, and what do you get?
You need
- The job and the done artifact you expect
- Whether recordings or screenshots are available
- Which metrics must be sourced
You get
- The finished artifact
- Evidence pack: recording or screenshots, source links, guesses, skips
- A clear call-out of anything omitted for lack of proof
How does it work, step by step?
- Define doneName the artifact you will open, not just a status update.
- Demand receiptsRequire recording or screenshots, linked sources, separate guesses, and skips with why.
- Kill unsourced numbersIf it cannot show how a number was produced, the number stays out.
- Review the tapeWatch or skim evidence before you widen scope.
The prompt
Our own prompt, inspired by Carnage (@0xCarnagee) and written to work in Grok Bot, ChatGPT agent, Claude and others. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Complete this job and show your work. Job: {job}. Done artifact: {artifact}. Return: 1) The finished artifact. 2) Evidence: a capture or still frames covering the steps you took. 3) Exact source link for every number. 4) Anything you guessed, listed separately. 5) Anything you bypassed, with the reason. If a figure has no proof trail, omit the figure. Do not invent evidence.
Inspired by Carnage (@0xCarnagee): X Article: The Grok Bot Team's Own Workflow (11 steps). The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- A summary without evidence trains you to trust claims you cannot audit.
- Guesses mixed into facts are worse than an explicit guesses list.
- Skipped steps need reasons; silence looks like completeness.
- Do not ask the agent to fabricate a recording it did not capture.
Our take
Trust collapses when agents deliver confident summaries without receipts. Carnage's tape rule is the fix: finished work plus screen recordings, linked sources, guesses and skips called out. Defining done as an artifact you can open, rather than a status update, is the first step. Then ask for proof: a screen capture or still images, source links, a separate list of guesses, and any skipped steps with the reason. Mixing guesses into facts is worse than listing them honestly, and silence about a skipped step looks like completeness. If the bot cannot show how a number was produced, leave the number out. Review the evidence before widening the agent's scope; that is how trust is earned rather than assumed. Never ask an agent to recreate a recording it did not capture, since that would be fabricated evidence. The extra minutes spent skimming a tape cost far less than acting on a polished summary that turns out to be wrong.
Where the time goes back: You review receipts instead of redoing the work, so bigger jobs can move earlier without blind trust.
FAQ
What counts as evidence?
When can I stop watching every run?
What if a number lacks a source?
Source and credit
Inspired by Carnage (@0xCarnagee). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- X Article: The Grok Bot Team's Own Workflow (11 steps)
- Creator
- Carnage (@0xCarnagee)
- Published on
- X
- Original date
- Aug 19, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Grok Bot
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. Evidence pack complete; unsourced number dropped.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.