deadreckon
mechanism · 03

The run lifecycle

Every run walks a seven-phase machine — init, plan, provider, sandbox, execute, verify, complete — and only one path reaches "done".

maps to as-built §4§6

the machine · seven phases, one way to finish
Every run walks the same seven-phase machine A left-to-right flow of seven gap-numbered phases: init (0), plan (10), provider (20), sandbox (30), execute (40), verify (50), and complete (60). The execute phase is where the turn loop runs. After execute, verify runs the dr-gate watchdog; if its checks fail the run loops back to execute for another turn, and only a signed gate lets the run move from verify to complete. The status RunStatus::Completed is reachable only through phase 60. PHASE 0 init mint id + work dir PHASE 10 plan reserved (no-op) PHASE 20 provider route + fallback PHASE 30 sandbox backend + profile PHASE 40 execute the turn loop runs PHASE 50 verify run dr-gate PHASE 60 complete promote · done signed ✓ checks fail → another turn the model takes turns here (see chapter 4)
The phases are numbered 0, 10, 20 … so new ones can slot between without rewriting state. Only phase 60 can set the run Completed, and only with a signed gate.
Follow a run
1 / 7

When you type deadreckon run, the harness moves through the same seven phases in order, writing its progress to disk at each step so the run is always recoverable.

  • init: create the run's id and working directory, plus the gate's one-time secret.
  • plan: reserved for the future; today it does nothing.
  • provider: build the route from your config and resolve the fallback chain.
  • sandbox: pick the platform-native backend and prepare its profile.
  • execute: the turn loop runs here; this is where the agent actually works.
  • verify: run the dr-gate watchdog against your definition of done.
  • complete: promote the result into the library and mark the run done.

The phases are numbered 0, 10, 20 … on purpose. The gaps leave room to slip a new phase in later (say a 15 or a 55) without rewriting every run's on-disk state.

The one-way door. A run becomes Completed only by reaching phase 60, and phase 60 refuses to run until the gate's signed marker checks out. If verify's checks fail, the run loops back to execute for another turn instead of finishing.

source