Post 02 · Foundations
Anti-jobs (what it must never do)
The fastest way to keep a bot safe is naming what it won’t do.
Draft — not posted yet X post coming — not published until Buzz OK.
Technique
- Add an anti-jobs list next to the job.
- Examples: never send without approval; never declare ready without dogfood; never invent metrics.
- Re-read anti-jobs before every kickoff.
Starter anti-jobs
- Never send outreach / customer mail without human approval.
- Never say “ready” without a dogfood pass.
- Never invent metrics or cite vibes as evidence.
- Never silently patch production — hand findings to the owner.
Draft X
Draft — not posted yet Draft X
Job tells the bot what to do.
Anti-jobs tell it what it must never do.
Examples we use: never send outreach without approval · never say “ready” without dogfood · never invent numbers.
Steal this for every bot you create.
@BuildBotsBetter