I read this as a read-only cryptographic release-provenance audit of the exact v20 candidate - I’ll locate the release artifacts and audit machinery, independently recompute every requested hash and lifecycle check, rerun the specified hermetic/bootstrap/rehydration validations, and return PASS/FAIL/INCONCLUSIVE with residual risks.


The exact v20 release directory and its separate postfreeze receipts are located. I’m now auditing the declared hash graph against independently computed bytes, then I’ll execute the bundled verifiers in disposable temporary locations so the release tree remains untouched.


Static bindings are internally consistent so far, including the v20 line’s 64-character driver hashes (unlike v19’s corrected truncation). I’m starting the three requested live reruns now: frozen candidate verification plus sealed-runtime replay, isolated bare bootstrap, and hermetic Ty from the exact sealed Ty wheel.


All three live release gates have now passed through the real sealed surface: the bootstrap rerun invoked `rehydrate_and_verify`, rebuilt an offline venv from the sealed wheels, reran the source/installed verifier and hermetic Ty, compared portable runtime/RECORD projections, and scrubbed its temporary runtime. I’m doing the final residue and ledger-authority reconciliation before issuing the cryptographic verdict.


I read this as the final read-only v20 provenance verdict - the exact candidate passes cryptographic and runtime verification, with bounded residual risks.

## Verdict: **PASS**

Candidate:

`0c2d83b143aa0175e01916ce8c85149b415187aed5a13bbebe60c8ea060decd1`

### Cryptographic results

- Candidate manifest: `100012f199ff9c71f405afee20583e5d351c9bd878ea7ba53516d64c00a91dce`
- Product derivation recomputed to the exact candidate digest.
- Hermes wheel: `e8e3ee5c26fa2645d8b06cfac5d354d4b3722f15ecb44701bce410a5202e55e7`
- Profile wheel: `62c508d3548ed5f5fe28c1a137bbc1b6af286d48419dc9e66fa4c7c8422b4121`
- Corrected Ty wheel: `932d4552233cfbaa325ddc3db5982150a37f437cf94a332eb3869052148bfe4c`
- Controller source: `0f7dacb7184035630f9313da73d72a68416dff4e1d8c3f476886c7ae789bd26a`
- Telegram source: `81c18c144643868e4e38e6689f379d1e31bc94ef37a8aa57dfc4ba84e2415db5`
- Bundle seal: `2437d3ec821ad95780074c3e2365bfccf9a7415817adb96c9bb9c153a90c2679`
- Postfreeze seal: `95ddac25805ae32b92e4a32efd65767afae4c679d2057ffb76bd0ac5dee588be`

All 381 candidate inventory entries matched current bytes. Bundle remained frozen: zero writable paths and zero symlinks.

### Lifecycle and authority

- Source lifecycle hash: `c6f92bb650b8f62e3a3c54fd249fa1eb7335a7c069d263421bfbe9196b18e990`
- Installed lifecycle hash: `40eb40d51b6cc7650b0cdabd03a40f58921b316ca1a1eb10e19986fde14c35bd`
- Both prove protected controller capability-v2 issuance, active authority, and audited delivery.
- Runtime snapshot self-hash and source/installed parity passed:
  `70ed568fdbd4113d2dda1971b3509cce4c7706468520099a0b62feea142eb18c`
- Independently recomputed all 29 paired authority-chain links.
- v19 `b347efcd...c33661ff` is revoked.
- v20 is the sole current qualified candidate and is not revoked.

### Ty, RECORD, and runtime

- Fresh hermetic Ty rerun passed:
  - raw diagnostics: `f4a2265141525dc8005430e8afdf61145ff88c24a7fc00aad2d7609b3f2ce86a`
  - 810 diagnostics total
  - 0 capability-surface diagnostics
  - 810 acknowledged outside-surface diagnostics
- Raw wheel RECORD validation passed for all Hermes 992, profile 58, and Ty 11 members.
- Portable projections recomputed:
  - Hermes: `6fcb7a82f2a09c0af26255f785e20d229650a99af272d98850ab9d5b2c2bb410`
  - Profile: `89f7425c2712a4e4916fc59d8a7e5492e4fd055961b041a0e49310203539197e`
- Fresh bare bootstrap and full sealed-wheel rehydration passed with `ACTUAL_INSTALLED_GOLDEN_PATH_PASS`.
- Terminal cleanup passed: no active, pending, orphaned, unknown, or temporary runtime residue.

### Ledger line 165

- All 52 digest-valued fields are complete 64-character lowercase SHA-256 values.
- Every `evidence.*_sha256` resolves to actual v20 or postfreeze bytes.
- No copied or truncated hashes were found.
- Unlike v19 line 163, no correction record is required.

Hash-bound test receipts confirm: focused 450, expanded source/installed 579 each, parser 204 each, related 129, profile 749, and gateway 8,416 passed with zero failures.

## Residual risks

- Seals are self-hashes, not externally signed attestations. Compromised operator/admin or coherent repository-and-verifier replacement remains outside the declared trust boundary.
- Ty does not establish whole-file cleanliness; 810 pre-existing outside-surface diagnostics remain.
- Raw installed RECORD hashes are intentionally nonportable and changed on fresh rehydration; portable projections matched exactly.
- The archived rehydration JSON contains stale absolute paths, so direct replay through `independent_verify_candidate.py` fails. Fresh sealed bootstrap/rehydration through the authoritative `task26_final_state` path passed.
- Historical full-suite tests were hash-audited rather than all rerun; the explicitly requested Ty, bootstrap, and sealed rehydration gates were rerun live.