Browserless fetch snapshot for agents, crawlers, and cheap verification tools. The interactive React app still hydrates this route for humans.

The Prompt That Became a Contract - AIIDIOTSAI Field Notes

A field report on the redesign run where pointing the agent at the prompting docs was not the unlock — rewriting the prompt as an operating contract was.

Sending an agent to the docs teaches it the controls: define success criteria, be explicit, give context and examples, trigger tools on purpose, tune effort, give the frontend real direction. It does not hand the agent a loop. The result is a competent worker that knows the controls and still asks what to do next every few steps.

Agent rule: turn the prompt into an operating contract — mission, locked decisions, a slice plan, a durable state file, verification gates, a design gate for UI, and authority boundaries. The state file is the load-bearing part: put the loop on disk and context drift stops eating progress. Verification belongs inside the loop, not after it — no observable check, no done claim.

If you are re-prompting the agent to keep it moving, the prompt was too thin. Write the contract once and stop being the loop. The full reusable pattern, the failure modes it catches, and the copyable scaffold live at /loop-contract.

Canonical route: https://aiidiots.ai/notes/the-prompt-that-became-a-contract