I read this as a read-only final release-provenance audit of the exact v9 candidate - I’ll inspect the frozen evidence and ledger, independently recompute all cryptographic and provenance claims, then rerun the bundled verifier and sealed-wheel rehydration without altering the source tree.


The frozen-state receipts and ledger line are present and internally point to the requested digest. I’m now separating independently reproducible facts from receipt-only claims, with special attention to seal conventions, the 251-entry portable inventory, authority-chain derivation, and whether rehydration can truly be rerun from sealed wheels alone.


The bundled verifier rerun is a cryptographic PASS when invoked with the sealed build-time package source required by its imports. A bare system-Python invocation fails with `ModuleNotFoundError: checkin_cli`, so that invocation is not self-contained; the sealed-wheel rehydration path is the decisive portability check. I’m executing that offline path now in a disposable private directory and will verify both runtime deletion and unchanged dirty-tree/evidence digests afterward.


message: Codex error: Our servers are currently overloaded. Please try again later.

stop_reason: error


I read this as a read-only final provenance verdict - report the independently recomputed result, discrepancies, and residual risk.

# PASS

Candidate `78ecb799bc2e451f6055d892cb1f3af459dca62f4b8dd80c61ff8a3d43789538` is cryptographically consistent with the frozen v9 bundle, post-freeze receipts, and ledger line 158.

## Recomputed identities

- Candidate digest: `78ecb799bc2e451f6055d892cb1f3af459dca62f4b8dd80c61ff8a3d43789538`
- Product digest: `991768caae108104828435be8b5887fd75bd9dabdad436930e93e3cf2782133e`
- Portable-runtime digest: `01fde4b63230782dfa985dd8fd59f3afefae24be7913e2c1ac2d8f5c03f76813`
- Candidate manifest SHA-256: `f3885df7210fea08692a2e52569a8825b3e39919ab5ff08f2f88d3f3f57544fd`
- Bundle seal SHA-256: `c505c3e6af80d1b7d5a2c79c8fb353c7541bf6b374a2c8f0c74ca9ef5dc8d936`
- Post-freeze seal SHA-256: `08ae9ea2a74927e24501d0ede6b977ed0c773938bf6b6f91bb98f028ed3029ab`
- Bundle inventory: exactly 251 files; inventory digest `fbc7ebdca4c436fd5c2f9de8b1c3e288fb2f171553b7b4758374ac3ef3d5afc3`
- All bundle paths remain frozen at file mode `0400` / directory mode `0500`.

Ledger line 158 matches all five candidate/product/runtime/bundle-seal/post-freeze-seal values.

## Provenance and authority

- Both wheel ZIP inventories and every RECORD hash/size recomputed successfully.
- Hermes wheel: `d530e1dbf58f2001ea272eac44a4182ae5cf4c75b8506b103369c787e5027a7a`
- Profile wheel: `62c508d3548ed5f5fe28c1a137bbc1b6af286d48419dc9e66fa4c7c8422b4121`
- All 92 recorded loaded-module origins are installed `site-packages` paths.
- Source/wheel/installed hashes agree for the five packaged modules, including `task26_*`, `gateway.commit_observer`, and `_commit_receipts`.
- Source tree digest independently recomputed as `b34b2a12fd0ad3d4c95a58c847a2411e81272a646f5a4f5ec568d0d3640a3747`.
- Authority chains: 15 paired events/rows, seven valid revocations, no broken predecessor or cross-chain binding.
- Registry head: `8a1d29a109a284cab67f11efa4cb90a6e31768fb7e9b1b245b8a895ccc4ac80e`
- Ledger head: `3dbfc6e006649725a7bb7c4006bd8a18f14ed46cff6bd39c5b9eddaca6109d30`
- Only the requested candidate remains current.

## Runtime and behavior

- Bundled frozen verifier rerun: `TASK26_FROZEN_CANDIDATE_PASS`.
- Offline sealed-wheel rehydration rerun: `TASK26_FROZEN_CANDIDATE_PASS`, with `rehydrated_runtime_verified=true`.
- Source seven-clause rerun reproduced chain head `1b7abf3fc7799220b354c0f6b24572714cd5913b3a4868a0457bd49af395e793`.
- Installed chain head: `4d174421d8a89ace139aa0e79dddc33c8036f64745cc91ddb8cec2fb56a390dc`.
- Observer: `dnotify_signalfd_v1`, one directory resource, zero inotify watches, five chained receipts.
- Recorded and currently measured pressure both equal `130964 / 131072`; candidate process count is zero.
- Terminal cleanup has active/pending/unknown/orphan counts all zero.
- Original runtime remains absent; temporary rehydration runtime and audit directories were removed.
- Bundle and post-freeze aggregate hashes were unchanged by verification.
- Dirty-tree status stayed byte-identical at `d1c88ac107f9e0b96506a03c0ea1eb934086b3cf074d60933456a0894113c3b4`.

## Test evidence

Sealed logs support:

- Gateway: 376 files, 8,308 passed, 0 failed
- Profile: 749 passed
- Final-state/authority/provenance: 64 source + 64 installed
- Parser/policy/preview: 196 source + 196 installed
- Observer: 16 source + 16 installed
- Adversarial: 10 source + 10 installed
- Observer-resource attacks: 4 source + 4 installed
- Static checks, compile/help probes, and `pip check`: PASS

## Discrepancies and residual risk

- A bare system-Python verifier invocation fails because `checkin_cli` is not on its import path. The documented frozen invocation succeeds with the sealed build-time package source, and the genuinely portable sealed-wheel rehydration succeeds without it.
- The Gateway runner discovered 8,365 cases but summarizes 8,308 passed and 0 failed; the 57-case delta is not explicitly classified in the log summary, although it does not contradict ledger line 158.
- Portable canonical state excludes pip-remapped `../` script/data paths; those bytes remain wheel/RECORD-bound and were validated during fresh rehydration before portable normalization.
- Provenance PASS does not authorize release: ledger line 158 still states `task26_complete=false` and `release_authorized=false`.