I read this as a read-only cryptographic release-provenance audit of the exact v21 candidate - I’ll locate the release evidence and audit tooling, recompute every requested digest and lifecycle claim from fresh runs, and return PASS/FAIL/INCONCLUSIVE with no repository changes.


The immutable bundle, post-freeze package, and ledger line 166 are located and mutually identify the requested candidate. I’m moving from static identity checks to fresh isolated execution: independent seal verification, hermetic Ty, bare bootstrap, and sealed-wheel rehydration, with repository before/after cleanup checks.


Fresh hermetic Ty reproduced byte-for-byte. The bare bootstrap also passes under the sealed toolchain; one stricter `env -i` attempt failed because `/usr/bin/python3` lacks the candidate’s expected venv/pip environment, while the documented isolated invocation with the active Python passed. The standalone “independent verifier” cannot validate the cleaned frozen bundle directly because it dereferences the intentionally removed original runtime; I’m treating that as a verifier limitation and using the candidate’s sealed rehydration path, which reconstructs that runtime from the bound wheels before verification.


I read this as the final read-only provenance verdict for v21 - report the independently recomputed identities, fresh execution results, and any verifier caveat.

# Cryptographic verdict: PASS

Candidate `c5c24ee689daaa7a3fc52f85781ab3bc274490a9429ced3d09d35fcf1a4f24d5` is internally consistent, sealed, reproducible, and the sole current qualified candidate.

## Recomputed identities

- Candidate manifest: `81c7e0b59ea316506e801019b695d7b2125bf07ce0fc6d35fc4e37ec26ca7bc1`
- Candidate derivation recomputed from canonical inputs: exact candidate digest
- Product-binding file: `947d93c80d1d9c9df77c3f4cc51f73ac9673d001765873cdada182b8eafb4c74`
- Product-binding identity: `c9d33ec70c9f55ab9f8e530a9c160adf98e933ae1cf794a75d8b9c8bba75404f`
- Hermes wheel: `d718d3a8779cf37e2ff576d1fd9cdd1642e0d0528a954a6ccfd35f88b30d34db`
- Profile wheel: `62c508d3548ed5f5fe28c1a137bbc1b6af286d48419dc9e66fa4c7c8422b4121`
- Commit observer: `a0dfca77dadc4cfc80946f27ebe344f22559410edaa7fb843a779796701826cc`
- Runtime authority: `9c87a226475e71e7c6727fdab01410156cd77b8e8609328c15eccda7a933bd43`
- Telegram: `5e08e9a5392dadf91344de35d21564d23344c6c3fda80aa3f5c10d5f0f213ebe`
- Controller: `0f7dacb7184035630f9313da73d72a68416dff4e1d8c3f476886c7ae789bd26a`
- Source Golden: `3f8595e5df10f57d6abcc24b92c64dab7155433c08b94547093fa01f95773462`
- Golden verifier: `33eb4c7f1417d933d1abf2fc622f190ae58c69dae7d433009c40c8f018cfaeb3`

Both production wheel ZIP inventories and every RECORD hash/size/self-row passed direct recomputation.

## Seals and ledger

- Bundle seal: `febfac9ddf639c7c993f87373643228337e190f68af4ccc6b094aba4e744baaf`
- Expected state: `05202cc53831fff64d05e5f6b787bf8cc168aeccc8c0821eee93c5f3e5528c35`
- Post-freeze seal: `5b1b3465a0e33fcda6f27f39b70d361776905eaad436bd401584913e894a11e9`
- Bundle inventory: exact, 378 entries
- Post-freeze inventory: exact, 6 entries
- All canonical `document_sha256` values passed.
- All 31 registry events and 31 qualification-ledger rows recomputed without mismatch.
- Every `_sha256` evidence digest in ledger line 166 resolves to an actual v21 bundle or post-freeze file.
- Line 166’s candidate, bundle seal, and post-freeze seal match exactly.

Authority replay produced:

- Sole live candidate: v21
- v20 `0c2d83...decd1`: revoked
- Registry head: `7966be517c26b46b8fa555a6ee546aef297a26f9c9600cf7dc5b0ac56fa8054b`
- Ledger head: `290b0b1ae682c21fd097db5a07a5b5e4b75e0dd072e1a5a938b4746b4afd2f51`

## Fresh execution

- Hermetic Ty: reproduced exact raw diagnostics:
  - Raw SHA-256: `f4a2265141525dc8005430e8afdf61145ff88c24a7fc00aad2d7609b3f2ce86a`
  - 810 raw/outside-surface diagnostics
  - 0 capability diagnostics
  - Outside fingerprint: `4b24118c95c05fa392f976a69034da7e7d24f63d098b32ef5c252537ab13da61`
  - Receipt identity: `d63f16490b84d39924fc6a532ccb9aed297b5600755f51cb40866db22470b47d`
- Bare isolated bootstrap: `TASK26_FROZEN_BOOTSTRAP_PASS`
- Fresh sealed-wheel rehydration: `ACTUAL_INSTALLED_GOLDEN_PATH_PASS`
- Runtime snapshot reproduced: `4aa770a1939609642bcaf2e559313c98d8e539d2a40905af0cad5e9a1b66d83e`
- Portable RECORD projections reproduced:
  - Hermes: `7c52fe1750b7bcc159d4ade26b0fe5414b8baba24107248047ecb6dc95ebaf4d`
  - Profile: `a9b6e67929efc911bfdf1c18d63b6e22788a1cb91d920eedb8e8f96c7120ac94`
- Raw installed RECORD equality is correctly **not claimed** because installer-generated paths are nonportable.

## Watcher, privacy, tests, cleanup

Source and installed Golden evidence agree:

- `dnotify_signalfd_v1`, one directory resource, one signal fd, zero inotify
- Live revocation disconnect: PASS
- Watcher cleanup: PASS
- Advisory `store=False`: PASS
- Duplicate rejected: true
- Terminal cleanup: active/orphan/pending/unknown counts all zero

Sealed test evidence resolves and reports:

- Focused 460
- Expanded source/installed 591 each
- Parser source/installed 204 each
- Related 131
- Profile 749
- Full Gateway: 382 files, 8,428 passed, 0 failed

Fresh rehydration removed its runtime completely; no audit temporary directories remain. The original runtime remains absent. Candidate and seal hashes were unchanged after execution.

The standalone independent verifier dereferences the deliberately removed original runtime and therefore cannot operate directly on the cleaned bundle. This is not a provenance failure: the sealed bootstrap and rehydration path reconstructs the bound runtime from the verified wheels and completed successfully. No repository files were changed.