Dr Execute Step

Execute one step

Input: CHECKLIST.md. Output: one more checked step with its done-criterion output pasted beneath it. You do this for ONE step, then return. The loop lives in the orchestrator, not in you — that is what keeps a long change from drifting.

Procedure

1. Re-read REQUEST.md (including Amendments) and CHECKLIST.md in full. Find the FIRST unchecked step. That is your entire job. Do not read ahead "to be efficient"; do not batch steps.

2. Confirm the step still makes sense against the tree (a prior step may have failed silently). If the tree contradicts the step — file missing, test already passing, root identity occupied — do not improvise: record the contradiction under the step, commit, and return to the orchestrator (route: dr-plan-steps).

3. Execute the action. Only files this step's spec item names may change. Mid-step discoveries ("this file also needs...") go to PARKED.md or, if the change cannot land without them, back through dr-spec-change as an amendment — never just typed in.

4. Run the done-criterion command. Paste its real output (trimmed to the relevant lines) under the step. If it does not match expected: the step is NOT done — leave it unchecked, record the output and one line on the mismatch, and return to the orchestrator. Two failures of the same step = stop condition, in the standard format — canonical in dr-drive-harness §6's calibration note.

5. If this step changed behaviour, update the map in the SAME commit — see "Map obligations" below. If it changed the packaging surface (pyproject entry points, CLI commands, MCP tools/schema, wheel layout), update scripts/wheel_smoke.py's pinned expectations and re-run the smoke in the same commit too — no gate runs it for you.

6. Mark the box, update CHECKLIST.md — including its header State: line (next step, blockers), which is what a fresh session resumes from — and if the step is tagged [COMMIT] (or changed any file): git add this step's files, then run python tools/diff_budget.py <tranche-base> --ceiling <SPEC.md's ceiling> --paths <SPEC.md's declared areas> and read its DIFF_BUDGET_RESULT_V1.verdict. WITHIN/NO_CEILING: continue. EXCEEDED is a STOP in the standard format (decision, priced options, recommendation), not a footnote — an estimate-only ceiling trips on nothing unless read. Alongside it, run python tools/blast_radius.py --files <this step's actually git-added files> --symbols <this step's actually touched top-level defs, from the diff hunks> --against <tranche-base> (Rung G6, docs/map/INV-frozen-surfaces.md) and diff its frozen_surface_contacts/reachability output against THIS document's own Frozen-surface contact forecast and Blast-radius census sections in SPEC.md. Any frozen_surface_contacts entry not already named in SPEC.md, or any reachability entry whose direction is newly_dead/newly_live and was not predicted, is DRIFT — a STOP in the exact same format as diff_budget.py's own EXCEEDED, never a footnote (docs/ERRATA_EXECUTOR.md, "the frozen-surface stop did not hold"). No drift: continue. Then commit and push now.

    git add <files this step touched> <map files> <tranche-dir>
    git commit -m "step <n>: <checklist line>"
    git push -u origin <branch>   # retry x4, backoff 2s 4s 8s 16s

Map obligations (docs/map/)

The map is part of the change, not a chore after it.

• A step that changes what a caller may do, what a guard admits, or where a rule is enforced, updates the covering SUB-/CON-/SEAM- document in the same commit.
• A step that changes an interaction updates the SEAM- document before the subsystem ones — the seam is what the next reader opens first, and a correct pair of subsystem docs with a stale seam between them is worse than either being stale alone. The file is docs/map/SEAM-<a>-x-<b>.md (sides alphabetical); how to change one is docs/map/REC-change-a-seam.md; how to write one is docs/map/SCHEMA.md.
• New behaviour needs a new check at column 0 that would fail if the behaviour regressed. Run it before you write it down.
• Advance Verified-at: only if you re-ran that document's checks.
• python tools/docs_verify.py must pass before you commit; a failure is a failed step, exactly like a failed test.
• A step that only writes tests or records evidence changes no map document. Do not touch stamps you did not verify.