See the input → responsibility → output diagram.
What it does for you: It checks a built-in fixture while exactly one owner holds the Attempt, and stores a report before settling anything. If a controller dies partway through, the next verify or recover settles that Attempt from its report, or proves the old work cannot resume. Only verify then starts a replacement, within the Run's Budget.

Meet the double-checker. Read it again before you settle. Checks evidence under ownership and recovers unfinished fixture Attempts. Meet the whole Plumb family.
How it links: It takes ownership from Execution, fences and workspaces from Attempt fence / workspace, fixture runs from the Local fixture worker and Verdicts from Evidence / Assurance. It gives settled Attempts back to Execution and writes its records to the Command journal.
Honest limits:
- It covers only the fixed built-in fixtures, tested on one macOS host with Node 26.8.1. It is not a sandbox for arbitrary code, its state directory is trusted rather than defended, and power loss is untested.
- A closed fence proves that the old work cannot resume, not that its process exited. Without proof, the Run stays unresolved. Nothing recovers in the background. It happens only when someone runs
verify,recoverorcancel.
Status: Accepted for trusted fixtures. Acceptance and evidence.
A separate application can try the private fixture-resource package, providing its own Journal, Evidence store and narrow GuardedContext. Its Execution and preparation/report ledger must use the same journal file; separate handles on that file are valid. This draft uses a distinct compiled protocol and was accepted locally on 1 October 2026. Historical source runs remain readable and are never silently upgraded.
