Historical local qualification: Source 7cf4b26e focused Core 22/22 and Dashboard 26/26 checks passed. The historical bounded local record keeps their exact scope. Historical source 7cf4b26e passed the 3,286/3,286 full checks and all 36 installed families. Independent bounded local evidence acceptance passed; exact-final-head CI is recorded separately from this frozen local proof. Module-specific and broader limits remain below.
See the input → responsibility → output diagram.
What it does for you: It runs a Slice's frozen checks against a sealed Candidate and keeps what it saw. For each check it hands the sandbox one side's own files as the program (the unchanged code or the Candidate) and the one fixture input the check names, and nothing else: the expected output stays on the host as a digest. It refuses to be set up if anything the Factory must keep private sits where the sandbox can read, and checks that again before each run, along with whether it still owns the work, what the gate says, the runtime and the time left. It finds such a thing whether it is named directly, through a link, or through the Data volume's second names for system folders. It stores observations while ownership and code resources remain valid. A write failure or lost ownership stops further work; changed or unreadable resources leave the current observation unstored and retain earlier Evidence IDs for inspection. A refusal, timeout or lost run cannot establish a pass or a fail. Beside it, a small store keeps each frozen fixture input once and checks it again on every read.

Meet the field collector. Bring back observations, not guesses. Runs a Candidate's checks in the sandbox and stores what it observed. Meet the whole Plumb family.
It refuses before anything runs if the Candidate was sealed for another Slice, store or set of checks.
A caller can read fixed diagnostic codes beside each run instead of parsing its error message. They distinguish deadlines, cancellation, refusals, uncertain execution and storage failure. A timeout or process signal describes what was observed; it does not guess why a process died. These codes change no Evidence, judgement or retry permission. Current corrective evidence.
How it links: It runs programs only through the Confined executor, stores records in the Evidence store for Repository Assurance to judge, and checks its owner's hold with the Attempt fence. It takes a sealed Candidate and the unchanged code from Repository, but never touches Git or the journal itself.
Honest limits:
- Nothing calls it yet: the delivery flow that will pass it the gate and judge its records is not built, and no real Slice has been checked with it.
- It runs each check once. There is no retry and no fallback to running code outside the sandbox.
- Its privacy check compares names and file identities at setup and before every run. It does not find a second hard link to a private file, a link made during a run is caught only before the next one, and anyone who can write the stores can forge records.
- If its owner's hold ends during a run, the run still finishes; only then is nothing more stored or started.
- Resource-drift diagnostics retain earlier Evidence IDs and the current observation without permitting a retry. Lost ownership or a failing caller clock can still throw without that diagnostic payload; an error alone does not prove nothing started.
Status: In progress. The resource-drift correction passed eight focused native cases and independent Source review. All34 earlier combined Collector checks retain their snapshot. Historical source 7cf4b26e passed the 3,286/3,286 full checks and all 36 installed families. Independent bounded local evidence acceptance passed; exact-final-head CI is recorded separately from this frozen local proof. Earlier receipts retain their historical scope. No live Slice or delivery-owner qualification.
The code pin for collection has changed. Old recipes stay unchanged and cannot start new checks; new work needs a verified recipe and a new Slice revision. See the contract and compatibility rules.
The private package adoption draft lets a caller compose collection and judgement with its own Candidate bytes, fence, snapshots and Evidence store. Compiled code has distinct resource identities. Old proof stays readable; old pins never silently authorise new code. The external consumer is implementation evidence, accepted locally on 1 October 2026, and grants no Repository integration authority.
