A guided decision exercise
Your job: bring Droids back into payments, under controls Ruth will sign.
In March an agent changed one line of rounding code and every test passed. Larkspur froze agent use. Imani wants the throughput back; Ruth wants to know what the agent cannot do. You make five decisions.
Learn: a 30-second explanation, with a link to the lab.
Decide: choose between three real options.
Predict, then see: commit to a prediction before the consequence is revealed. You are not running Droid; outcomes come from the workshop’s illustrative scoreboard.
Decision 1 of 5 · Write down what matters
What goes in the file Droid reads first?
AGENTS.md is the project briefing Droid loads before it writes code, found by searching from the working directory up to the git root. Unlike a wiki page, you don’t have to hope Droid goes looking for it. What changes an agent’s behavior is specific: exact commands, named helpers, a list of what must never happen, and permission to stop.
Go deeper in the lab →Dana has an afternoon to write Larkspur’s AGENTS.md. What does she put in it?
Make a prediction to unseal the ledger. Good engineers form a hypothesis before they look at the dashboard.