Recipes

Everyday moves, in the words you'd actually say.

"Just fix it": the light path#

A settled one-step change needs no ceremony: say what you want fixed. The agent builds it and records one micro-initiative with one ticket; the ceremony skipped is shaping, never the evidence. If your "small fix" turns out to hide a real decision, expect one sharp question first.

"Prove it": verification on demand#

"Did that actually fix it?" / "Prove it's faster." The agent restates the claim falsifiably, captures baseline and treatment with identical commands, and returns a verdict with the numbers. Speed claims get measured on realistic corpus sizes, with machine load recorded; a breach under load reads as the tail arriving, not a mystery.

"I can't tell which design is right": spike it#

Questions an experiment can answer get a throwaway prototype, not a debate. Spike code lives on a proto/ branch (never merged, never in the artifact tree); the question, the answer, and the pointer land in prototypes/PROTO-NNN.md; the ruling folds into decisions.md.

"Go read the docs and tell me": research#

Questions the primary sources answer get a research note with every claim cited, and an honest "what could not be verified" section. Specs pin the research revision they consumed.

Keeping evidence re-takeable#

Measurement tickets keep the instrument and its raw output together under evidence/<TKT>/, and the instrument settles BEFORE the recorded runs; an instrument edited after the numbers were taken re-opens the evidence. A stranger should be able to re-take your numbers next month from the repo alone.

Changing how the agent works#

Say it plainly ("stop the progress reports", "always test X first"). Installed disciplines get one pushback naming the rule and its reason; then your second word is final and is recorded with the conflict noted, so future sessions honor it without re-arguing. Blockers you can act on are always reported regardless.

When doctor refuses something#

Read the message; it teaches. Refusals name the legal fields, the expected home, or the exact cure ("revision is required and starts at 1"). Fix the named thing and re-run; see the doctor reference for every code.

Editing artifacts by hand#

Artifacts are yours: hand-edit any Markdown under .green-line/work/; frontmatter contracts are checked by doctor after the fact. Bump revision only on a change of meaning (a link or a typo never bumps); after bumping something others pin, the consumers get re-checked and re-pinned.