See the input → responsibility → output diagram.
What it does for you: It keeps a durable record of who owns each Run and Attempt, and how each Attempt ended. A retry, a crash or a late report cannot create two owners or override a cancellation. Ownership passes to a new Attempt only when the previous one reports in, or a trusted supervisor confirms that Attempt ended or was fenced off.

Meet the conductor. One owner, one baton. Tracks Run and Attempt ownership, including how each ends. Meet the whole Plumb family.
How it links: It takes Run submissions, claims, reports and cancellations from Guarded verification / recovery. It records every step in the Command journal. It names the Run and Attempt that the Attempt fence / workspace and Evidence / Assurance pin to.
Honest limits:
- A completed Run means the Recipe ran to its end, not that the Candidate passed. Only Assurance gives a Verdict.
- It starts, stops and times nothing. A cancel request does not stop work. A stuck Attempt stays running until a trusted supervisor confirms its work ended or was fenced off, which is not proof that its process exited. A Run may use at most 20 Attempts.
- Callers are trusted local code. Crash tests killed processes; survival after power loss is not tested.
Status: Accepted for trusted local supervision. Acceptance and evidence.
The draft standalone adoption guide explains the private package and caller-owned journal. The distribution was accepted locally on 1 October 2026 (owner-designated acceptance reviewer, after independent Opus 5.5 and Fable 5.1 reviews).
W30 implementation subject candidate
submitImplementation records an explicit pre-seal request/source subject in the existing Run lifecycle. The original job digest, source commit/tree/snapshot and recipe/scenario pins remain immutable through cancellation and every Attempt transition. The legacy Candidate submission and histories retain their original meaning; a request digest never fills candidateDigest. Author focused checks passed; independent final review remains open. Implementation Workflow.
