CURRENT — single source of "what happens next"

This file always names exactly one next action. Any "continue" / "next" / "proceed" message means: execute the action below, fully (implement → test → verify against its acceptance criteria → commit → push → close the issue → update this file to the next action). No ambiguity, no re-planning.

Next action

Owner decision on M9: mission-level capability policy (design sketch: missions may declare default tool sets; tasks inherit unless overridden; conductor validates the merge). Say "next" to proceed or name a different target.

Queue (ordered, not started)

M9: mission-level capability policy
Run-record retention/pruning policy
Second real adapter (parked — owner focused on Pi)
Auto-apply policy for worker patches (deferred until capability policy exists)

Rules

One action in flight. Update this file at the END of every action.
Blocked? Move the item to "Blocked" below with the reason and stop.
Completed actions move to the log at the bottom (date + issue + result).

Blocked

(none)

Completed log

2026-09-03 — M5 workspaces + capability envelope (#20, #21) — merged, tests green
2026-09-03 — M6 named sessions + resume (#22, #23) — merged, teach/recall verified
2026-09-03 — M7 run inspection + release 0.0.6 (#24) — merged, activated
2026-09-03 — M8 conductor loop + worker-built retry (#25, #26, #27) — merged; worker authored retry in 2 refinement rounds, conductor fixed a 3-line interpolation rename; live retry verified
2026-09-03 — retry lineage + relative mission resolution (#28) — merged, 36/24/14 suites + verify green
2026-09-03 — M8 conductor loop + worker-built retry (#25, #26, #27) — merged; worker authored retry in 2 refinement rounds, conductor fixed a 3-line interpolation rename; live retry verified

1.8 KiB Raw Blame History