See the input → responsibility → output diagram.
What it does for you: Each Attempt gets its own gate and a fresh private workspace. The Attempt's work runs only while the gate is held. When recovery closes the gate, that Attempt's protected work cannot resume, so recovery can hand the work to a bounded replacement. Its workspace is removed only after checks show it is exactly the expected empty folder; anything uncertain is left in place and reported.

Meet the gatekeeper. This workspace has one owner. Gives an Attempt a private workspace and a fence against stale ownership. Meet the whole Plumb family.
How it links: It takes an Attempt's Run, epoch and worker as Execution names them. It gives the ownership and workspace checks to the Local fixture worker, the ownership check to the Repository collector (accepted, not yet called), and the closing proof to Guarded verification / recovery.
Honest limits:
- A closed gate proves that the Attempt's protected work cannot resume. It does not prove that a process has exited, and it says nothing about what the work did.
- It is only for trusted code on one machine with a local POSIX filesystem, and it has been tested only on macOS with Node 26.8.1. It is not a sandbox, it does not defend against anyone who can write to the state directory, and it has not been tested against power loss.
Status: Accepted for trusted local POSIX fixtures. Acceptance and evidence.
A catchable error after fence creation now retries cleanup of only that call's private temporary name. Cleanup remains best effort; the published file and original error are preserved. A caller still must never reconstruct or adopt an identity that was not returned. The correction passed independent source review; independent installed-package review and the coordinator's 2,121-check combined full run passed, and the correction was accepted locally on 1 October 2026; final publication review, CI and live qualification remain open.
