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.
Historical bounded qualification, 3 October 2026: independent source and retained installed stage/concert evidence passed for the frozen local profile. This supersedes earlier source/package-pending statements below for that bounded profile. Historical 7cf combined full checks and independent evidence acceptance passed for the bounded local profile; complete stress/adoption matrices, exact-final-head CI and live commissioning remain separate. Reviewed scope.
Status: Authored Delivery candidate through bounded owned local integration, read-only inspection and assessment on disposable Products. Independent source and installed stage composition retain their snapshots. 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. Complete Workflow acceptance remains open. Trace, export, external Producer dispatch and live commissioning remain separate work.
Intelligence: none — Composition moves authored bytes and re-derives stored Evidence under the Product gate; no model makes these decisions.
Contract
delivery.ts composes the Product gate, Repository, collector, fences and retained records. delivery-inputs.ts retains local input locations. No provider, Execution Run or Attempt ledger is used.
deliveryPaths(journal, root)derives absolute directories without writing. Operations open an existing journal; the root must be canonical, private, owned and outside registered checkouts. Every protected path is checked against the current confined profile.bindProduct(paths, {productId, targetRef, copy, authored, boundBy})inspects a registered primary checkout, copies committed UTF-8 blobs through Checkout Git, and creates an owned bare store. Portfolio inspection records an observation. The complete binding draft is retained before the gate binds it. Replay reads that draft first; changed authored digests, copy paths or target conflict. A store created without a retained draft is never adopted.grantAuthorityandrevokeAuthorityuse the gate's original IDs/recorded versions.requestStop(paths, {productId, stopOrdinal, expectedVersion, reason, requestedBy})andclearStop(paths, {productId, stopOrdinal, expectedVersion})require immutable caller-retained command coordinates. Read the current gate once when forming a new request: next ordinal for a stop, current ordinal for a resume, with the observed version. Preserve those original fields on every uncertain retry. The gate replays the exact original receipt before current-state checks; retrying an old resume never clears a newer stop, and retrying an old stop after clear never renews it. A stale first attempt refuses; construct a new request only for a new owner decision. Limits and operation ordering remain the gate's contract.planSlice(paths, PlanInput)reads bounded fixture directories, pins guidance when supplied, builds acceptance/recipe/environment records and freezes the gate before retaining a Slice, source locations or snapshots. At most 16 input roots, 256 files and 15 MiB per input are accepted. Review checks are refused. Restart preserves the gate's original base and freeze time; changed content or pins conflict.produceCandidate(paths, {productId, sliceRef, proposalPath})identifies the authored proposal by its raw bytes. It admits once, seals through Repository and records sealed/rejected. An interrupted seal can be repeated under current ownership. Another pending proposal is abandoned before a new one is admitted; its allowance remains spent.verifyCandidate(paths, {productId, sliceRef, candidate}, signal?)requires a complete plan before check admission. It exports the Candidate, admits a bounded epoch, rechecks authority before each process, collects real Evidence, re-exports and judges store-read records. Only a retained Verdict followed by an observed outcome is terminal. Terminal Verified, Failed and Inconclusive replay by re-derivation without a new executor process. Failed repairs require a new proposal; stale proof requires a new Slice revision.integrateCandidate(paths, {productId, sliceRef, candidate, proof, action: {id, occurrence}, dispatchId})requires the observed retained proof for this Candidate. Keep the original action ID (actionIdOf(productId, sliceRef)), occurrence and hex32 dispatch ID on every uncertain replay. It re-reads Candidate, base, frozen inputs, runtime, collector closure and Evidence before admission and inside Repository's final guard, then performs oneinvokeOnceagainst the owned bare target. No registered checkout changes. The prepared ledger record and create-once request precede Git preparation/admission; the sender's own dispatched observation is retained before its gate outcome. A Failed or Inconclusive proof never integrates.assessCandidate(paths, {productId, sliceRef, candidate, proof})re-derives the observed proof, then returnsderiveAssessmentover the frozen Slice and those exact Evidence records. Supported is synthetic local evidence, never release or customer value. No conclusion is stored.inspectDelivery(paths, {productId, sliceRef: string | null})returns the retained gate plus bounded Slice, Candidate and proof identities;nullselects all retained Slices. It reads the journal only, acquires no ownership and starts no process.
DeliveryResult reports the operation, Product, outcome, detail, replay flag, journal and gate, with Slice/Candidate/verification when available. Resource drift during collection may add bounded collectionProgress: boundary/check, completed checks and their actual Evidence IDs, unentered checks and whether an unwritten observation exists. It carries no raw observation output, new Evidence, Verdict or retry permission. integration keeps the original dispatch/prepared/occurrence, gate outcome, retained sender receipt and current Repository observation when current read authority permits one. A historical integrated result means the retained move was confirmed; it does not assert the target still names that commit. currentValidity is valid or invalidated for a retained proof; it is never integration or customer acceptance. DeliveryError has invalid-input, not-found, conflict, denied, unavailable; underlying gate, journal, repository and storage errors retain their own distinctions. R6 presentation code/detail mapping and R12 fault-tool vocabulary are not implemented by this D4 packet.
Ownership and recovery
Planning, unfinished production and new verification work acquire a real Product fence from eight reusable slots. Binding, authority commands and terminal state-first replay do not acquire ownership. Only a released or positively fenced predecessor permits a new generation. Only recognised canonical numbered slots inside this Product's own D4 fence directory are reclaimed, under SQLite exclusion. A foreign predecessor may be released or positively fenced through its public protocol but its file remains caller-owned. Contention refuses work. The gate is released before the held fence. A replacement settles a dead owner's open check as unresolved; the next bounded epoch may collect. An orphan Verdict stays inert. Unresolved integration obligations refuse ordinary planning/production/verification work. Only integrateCandidate may enter recovery: a later fence-proved owner reads the original prepared record and retained sender receipt, or inspects that original intent under current read authority. It never calls invokeOnce during reconciliation. Confirmed receipt history may settle the original outcome after revocation; an inspection still needs unrevoked read authority. Unknown remains unknown without a positive receipt and blocks every new integration.
Snapshots and Evidence have Product-specific roots; each Product's executor has eight retained slots. One Product's retained namespaces cannot consume another's allowance. Every repository read after binding requires current read authority. A grant revocation, stop, deadline or stale owner cannot be converted into a new permit by replay.
Source locations and the freeze boundary
sf-delivery-plan-sources/1 is a bounded create-once local record at delivery:sources:<productId>/<sliceId>/<revision>, written by record:<aggregate ID> after freeze. It contains Product, Slice ref, original freeze time and up to 16 sorted canonical input roots with device/inode identities. It adds no field to the existing Slice, recipe or gate schemas. Its event is delivery.sources-recorded.
Between freeze and the first source record, original path spelling is not retained. Recovery may use equal frozen content at another currently safe canonical root; all Slice/environment identities must still match. Once the source record exists, path or inode changes conflict. Missing or corrupt source/snapshot records prevent verification and cannot be repaired through planning after any Slice admission. Source identities and placement are rechecked before each collector process and after asynchronous proof re-derivation. No bytes or source paths enter public documentation.
Verification and limits
Focused tests cover real Verified/Failed, terminal replay, raw proposal identities, dirty checkout preservation, revocation, stop/resume, Product isolation, retained-root exhaustion, proof corruption, held ownership and process deaths at binding, freeze, source/snapshot retention, sealing, collection and Verdict retention. These synthetic local checks are included in the independently accepted historical 7cf full-run evidence.
The executor's accepted deadline/retention limitations still apply. The journal and Git are separate durable systems; no blind integration retry exists here. Trusted storage writers can forge state. This library integrates only a Candidate into its Factory-owned local bare repository. It does not declare delivered value, run a model or commission a live Product.
The distinct-Candidate boundary record covers twenty genuinely different seals with store-backed Verified results, exact original-proof replay after exhaustion, and refusal of a sealed twentieth Candidate under a separately frozen nineteen-check allowance. The refusal setup uses distinct pre-aborted admissions, not successful collection. Author qualification and independent source/runtime review passed; combined CI and complete Delivery acceptance remain pending. The earlier twenty rejected proposals and twenty epochs of one Candidate prove different boundaries.
Current-main recovery and remaining acceptance
The 2 October recovery ports the original D4/R7 source and both native-input observation corrections, preserving current-main contracts, qualification pins and historical receipts. Malformed native Promise data is observed within bounded traversal and still refused before effects; it never becomes accepted JSON or authority. Original stop/resume identities and foreign-fence ownership have additional regression cases.
F0 keeps the original frozen base even when the Repository target moves. Changed grant, guidance, bounds, fixtures, runtime environment or collector closure cannot repin a frozen Slice; ownership events may change but Slice/source/snapshot/admission footprints remain exact. Fresh withheld acceptance is frozen after the authored proposal; a passing advertised check does not override its failure.
A collector resource failure retains actual earlier Evidence and reports its progress without a Verdict. A storage failure or other partial/uncertain collection leaves the original dispatch open and charged; it is never labelled not-started. After this owner releases its fence, a later owner reconciles that dispatch as unresolved before considering another epoch within the original fixed attempt ceiling. No proof is invented, silently adopted or repinned.
This remains In progress for complete D4/D5 Workflow and live commission. Historical 7cf bounded stage CLI/package/full checks and independent local evidence acceptance passed. Broader Workflow adoption remains open. Remaining whole-D4 gates include the full cross-Product Candidate/Evidence swap and protected-path alias matrix; remaining R7 size/path and staging/export mutation variants; simultaneous maximum Slice/root/snapshot/state combinations and remaining counter edges; multi-contender/retained-slot/long-takeover stress; and systematic stop/revocation/deadline/crash interleavings at every asynchronous boundary. The D5 local integration/reconciliation candidate is implemented below; R6 trace, export and external Producer dispatch/account reservation remain separate. Stage CLI/package composition and combined independent evidence are tracked by the completion packet. Qualification/adaptor source pins and historical receipts are unchanged.
D5 local integration candidate
The ordered CLI reads and reconciles its original unfinished integration before earlier stages can acquire ownership. Receipt-before-outcome interruption recovers the original confirmed effect; lost acknowledgement stays unknown. Ordered recovery correction records the adapter regression; independent correction review remains pending.
sf-delivery-integration-request/1 is represented by a create-once journal aggregate keyed by the SHA-256 of the Product/Slice Action and occurrence. Its immutable input includes Candidate, proof and dispatch ID; its prepared payload retains the original sender. Exact replay compares all coordinates before any work. Another Candidate, proof or dispatch ID for that occurrence conflicts. The same journal transaction binds the original dispatch ID through its Product/dispatch-keyed command receipt; reusing even an inert pre-admission dispatch ID for another occurrence conflicts before Git preparation. The identity correction records that boundary.
A crash after request retention but before gate admission leaves an inert original occurrence. Replay reports not-dispatched and never acquires a new sender for that prepared payload. A new attempt needs a new explicit occurrence and dispatch ID under current authority. Missing/corrupt prepared records prevent reconciliation; no record or receipt is silently adopted or repaired. A withheld final guard consumes its Repository claim and records the sender's own not-dispatched; its exact replay starts nothing.
The D5 candidate record pins the author checks: real once/replay, dirty checkout preservation, failed-proof refusal, revocation/stop, final-guard withholding, moved target, inert pre-admission interruption, receipt-before-outcome recovery, and lost-acknowledgement unknown/no resend. Author checks and independent Astra extra-high source review passed on the dispatch-identity correction. Installed consumers exercise real integration, replay, assessment, read-only inspection and fact-backed Marketing. Earlier bounded source/installed reviews keep their pins. 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. Complete Workflow acceptance remains open. Historical D4/core acceptance receipts are unchanged.
External verification candidate
Verification Workflow exports verifyExternalCandidate over the same owner, gate and records. It requires the exact bound Repository identity and a caller-sealed Candidate matching the frozen Slice. A durable original dispatch witness precedes its outcome. Recovery re-derives that proof after native exclusion; without a witness the original reservation remains inconclusive. Historical proof and current validity are reported separately, including missing current resources. Original installed stage evidence remains pinned; historical 7cf bounded combined native execution and independent local evidence acceptance passed.
