Strict all-eight V2 integration checkpoint and frame baseline — 2026-09-09

Verdict

Exact committed source a3dd6962f6fd366e90e512ffbf15c21d89cd6541 completed the checked genesis-candidate runner on hbox. All eight production SBF links compiled freshly through swarm-build, the production diagnostic count was zero, and the source-pinned Product handoff, checked Upgrade gate, reproducible gate, run record, and successor campaign pack sealed.

After the runner exited, all eight link descriptors, the reproducible gate, and the campaign pack reopened with the exact source verifiers. Two independent production-only frame captures then agreed byte-for-byte and admitted the baseline in tools/gates/frames-baseline.json.

Series selection was absent and remains recorded as false. General's production CU wall and fresh runtime campaigns are separate evidence. This record is local reproducible build and frame evidence; it is not validator, deployment, devnet, or mainnet evidence. The baseline covers this exact checkpoint only. Source changes after a3dd6962... require another exact-source capture rather than inheriting these rows.

Source and builder

The runner used explicit locked package selection for every production, profile, and frame build. Its final output records eight fresh links and no shipped build diagnostics. The driver log has no scheduler already-loaded marker or runner refusal.

Production links

Each admitted ELF is an ordinary no-feature production build. Trading's separate hot-cu-profile ELF is diagnostic-only and is absent from the role manifest and release set.

The production Trading frame maximum is 64 bytes below the 4,096-byte SBPF v0 wall. This is an admitted measurement, not reusable frame budget.

Seals and independent reopen

artifact_provenance.py verify passed separately for accelerator, claims, core, custody, registry, rent, resolution, and trading. The independent reproducible-gate verification reported link_count=8, the exact source revision and source digest above. successor_campaign_pack.py verify then rehashed and authenticated the complete pack at the immutable candidate path.

Independent frame admission

Capture B was a complete fresh production tools/gate frames run against the clean exact-commit checkout. It compiled all eight packages with explicit --locked -p <package> selection in isolated scratch targets.

Capture A used the checked candidate's seven no-feature frame objects for accelerator, claims, core, custody, registry, rent, and resolution. Those objects are independently bound by each verified role descriptor. Trading was rebuilt alone without hot-cu-profile, with an isolated target and fresh top-package marker. The exact source frame parser produced all eight reports, and frames assemble canonicalized them. The capture-composition record SHA is b6836a416170e5fe0198651d4b7b6d8bdd4fa4859de4c4e731b1e34c80d9fc28; its object/report/log inventory SHA is 44a96763f259a8d9d68315fdfe7d3338260eed6dc4a70f5ece111fd3965f0788. Every object referenced by Capture A remains at its recorded absolute path.

The independent captures are byte-identical:

capture A SHA-256 = 903d616c62b15a987856482a7515e2472d8dba8801a725bcf37ec54f7470111b
capture B SHA-256 = 903d616c62b15a987856482a7515e2472d8dba8801a725bcf37ec54f7470111b

tools/gate frames accept emitted and schema validation checked:

schema=dclutch-sbf-frame-baseline-v1
commit=a3dd6962f6fd366e90e512ffbf15c21d89cd6541
link_count=8
bound_bytes=4096
sha256=d05fc4b4e97e14f92f43c4d4b1cd8e5d20f64f24a5ce26f740ffc25253f0214e

The accepted frame counts are 51 accelerator, 310 claims, 265 core, 129 custody, 66 registry, 24 rent, 240 resolution, and 996 trading. All frame objects and reports used for the composed capture are preserved under the candidate and frame evidence roots.