Factory docs, home
Page navigation

See the input → responsibility → output diagram.

What it does for you: It keeps one durable record per Product that decides what delivery work may start. It binds the Product once to a store the Factory owns, and holds grants (which operations, which paths, how many runs, how long), their revocations, a stop switch and the one current owner. A Slice is frozen with its own allowance. Every production, check and branch move must then be admitted: under a live grant that, like the Slice, allows it, with no stop, by the current owner, before the Slice's deadline and within its allowance. At most one production and one check or branch move are in flight per Product at a time, and a branch move whose result is unknown blocks every later move until it is confirmed. A move is admitted only after its Verified proof is worked out again, inside the decision, from the stored Evidence, and only if the Candidate changes nothing outside the Slice's frozen paths. The delivery records beside it keep the frozen Slice, the store binding, the proof and each move's intent and receipt, each written once. They work out the Slice's measured outcome when asked, without storing a conclusion.

A broad teal bob beside a ticketed turnstile.

Meet the steward. Make room for the right small slice. Bounds admitted delivery work and keeps delivery records. Meet the whole Plumb family.

How it links: It takes Verdicts and their re-derivation from Repository Assurance, owner fences from the Attempt fence and store identities from Repository, and it records everything in the Command journal. It gives nothing to the rest of the Factory yet: the delivery flow that will call it is not built.

Honest limits:

  • Nothing calls it yet. It admits and records; it runs no Git, program or model itself, and no Slice has been delivered through it.
  • The journal and Git are never one transaction: a revocation after the final guard read may still arrive too late to stop the move, and the record shows the admitted effect. An unknown move is never settled by guessing. There is no rebind and no operator override.
  • Ownership passes only on proof that the previous owner was fenced off or let go, never by time, so a live but stuck owner blocks its successor. The gate cannot see the fence itself: it relies on the caller's fence check. Proof is re-derivation over trusted local files, not cryptography: anyone who can write the journal or the Evidence store can forge.
  • Gate state is never compacted: at 768 KiB new work is refused, while settling what was already admitted still fits.

Status: Accepted as step 1, increment 2, reviewed together with increment 1 (Repository Assurance): independent code review (Astra high) passed on 29 September 2026 in round 6, after rounds 1–5 each found something to fix). Acceptance and evidence.

Contract and limits

Shared readers keep validation consistent, and pure checks answer whether an admitted effect may still start. These checks are ready for the future delivery flow; they do not run it. See the contract and compatibility rules.

The private standalone adoption draft now lets a caller use these existing modules in its own application. Its runnable example seals a Candidate and shows why missing authority leaves the target unchanged. It was accepted locally on 1 October 2026; broader Workflow delivery remains open.

The two historical candidate descriptions below retain their original gates. The bounded local qualification separately records independent installed/full acceptance at source 7cf4b26e. That historical receipt does not qualify the union. Current combined-source review and local execution are recorded in the joint qualification record; exact-final-head CI is recorded separately.

W30 worker-origin reservation candidate

An explicit worker command upgrades the existing aggregate to /2, atomically checks original request/current claimed Attempt and Product authority, and spends the original Slice production-run allowance. Legacy /1 reads/ordinary commands/history remain unchanged. Delivery and the Implementation Workflow share one native Product ownership routine. Unknown worker/provider exposure blocks another dispatch and retains its envelope; exact replay is history. Separate Producer compatibility uses the same reservation without contacting a provider. Author focused/native checks passed; final independent review and acceptance remain open. Implementation Workflow.

W31 external verification candidate

The Verification Workflow adds explicit external check origin and profiled original dispatches under sf-product-gate/2. Legacy /1 histories remain readable. admitExternalCheck authenticates the exact native Candidate/base in the bound store; it charges checks without inventing production. recoverCheck reads the original durable witness and Verdict in the same active Journal transaction and re-judges branded Evidence after native owner exclusion. recordOutcome cannot accept a recovered observed report. Missing or corrupt witnesses never permit recollection. Final independent and installed acceptance remain open.

Neutral adoption contracts, 3 October 2026

The additive ProductGateV2 uses ProductBindingV2 provenance without registry/checkout fields. Explicit registration and protected roots, grants, ownership, limits and unknown-effect rules remain mandatory. Legacy ProductGate retains binding schema sf-product-binding/1, including its explicit W30/W31 aggregate upgrade to sf-product-gate/2. ProductGateV2 selects binding schema sf-product-binding/2 and aggregate /2 from binding onward. Both facades share one Product aggregate and refuse the other binding schema, including reopening a legacy worker aggregate through the neutral facade; /2 grants no second authority or automatic migration. The Delivery ledger remains /1. See caller setup.

Current evidence and open gates.

Source: docs/guide/product-gate.md