I read this as a read-only cryptographic release-provenance audit of the exact v19 candidate - I’ll locate the bundle, ledger, audit procedures, and then independently rerun every requested verification surface before returning a strict PASS/FAIL/INCONCLUSIVE.


The correction is structurally append-only and supplies a full 64-hex installed-driver digest; I’ve also confirmed the original line’s value is copy-truncated. I’m now moving from recorded claims to independent recomputation and fresh isolated executions against the sealed bytes.


The sealed verifier and all hash bindings currently validate by inspection, while the live Hermes worktree no longer matches the candidate’s captured dirty-tree snapshot (1,342 live entries versus 166 sealed). That is a post-candidate workspace drift discrepancy, not a sealed-byte mutation; the fresh runtime reruns will determine whether it blocks provenance.


One invocation issue is procedural rather than candidate failure: the standalone verifier/final-state scripts import the sealed `gateway` package but `python -I script.py` intentionally removes the bundle root from `sys.path`. The sealed bare bootstrap passed because it installs the wheel first. I’m rerunning the two package-dependent entry points as modules from the bundle root, and extracting the Ty source directly from the sealed Hermes wheel because the old cache source has drifted.


Fresh hermetic Ty, bare bootstrap, and sealed-wheel rehydration all reproduce the sealed candidate exactly. The corrected Ty wheel’s 109 wheel RECORDs validate, the runtime-authority source is byte-identical in the Hermes wheel, and source/installed snapshots are identical. I’m completing the final no-mutation/cleanup check and classifying the standalone-verifier limitation separately from release-byte integrity.


I read this as the final read-only v19 provenance verdict - the exact sealed candidate passes, with two non-blocking operational discrepancies.

# Cryptographic verdict: PASS

Candidate:

`b347efcd931f8590e08faffd23ff70070d34b6fd48dcc2363cea9e91c33661ff`

## Verified

- Candidate derivation recomputes exactly from canonical pre-execution inputs.
- Product digest equals candidate digest.
- Wheels:
  - Hermes: `62a09f9a...ab2b3c7`
  - Profile: `62c508d3...22b4121`
  - Corrected Ty: `932d4552...48bfe4c`
- All 109 wheel RECORD inventories, hashes, and sizes validate.
- Capability identity matches source and installed modes.
- Candidate inventory: 375 evidence files; bundle seal covers 377 total files.
- Bundle seal: `0bef0efe...3992599`
- Postfreeze seal: `9e7da340...8c6f84`
- Source and installed runtime-authority snapshots are identical:
  - snapshot `2877f7b0...690aa7`
  - candidate bound
  - 3 events
  - registry head `37017156...61023`
  - ledger head `4049d9e6...56e7b`
- Production wiring is present in wheel bytes:
  - external credential-backed authority
  - forbidden bundle/profile roots
  - activation, capability-issue, and provider-transport revalidation
  - predecessor snapshot and revocation checks
- Portable RECORD projections match across rehydration; raw RECORD equality is correctly not claimed because launcher material is path-dependent.
- Observer: `dnotify_signalfd_v1`, one directory resource, zero inotify watches, five receipts.
- Recorded tests are internally consistent:
  - focused 207
  - expanded 529 source + 529 installed
  - parser 204 + 204
  - related 129
  - profile 749
  - gateway 8,406 passed, 0 failed across 381 files/12 workers
  - Ruff checks passed

## Fresh reruns

- Hermetic Ty: PASS
  - executable/member: `a7c67f97...f88d16`
  - installed RECORD: `2bf2008b...895be`
  - raw diagnostics: `f4a22651...ce86a`
  - 810 diagnostics, zero on capability surface
  - receipt: `97f22cb8...83bb`
- Bare bootstrap: `TASK26_FROZEN_BOOTSTRAP_PASS`
- Sealed-wheel rehydration: `ACTUAL_INSTALLED_GOLDEN_PATH_PASS`
- Rehydration removed its runtime completely.
- Bundle/postfreeze remain immutable: zero writable paths, zero symlinks.
- Audit temporary files were removed.

## Ledger correction

Line 164 is a valid append-only correction to line 163. It supplies the complete installed-driver hash:

`6aaf136745afbe39fa4e2fcfa0a1c0b7f4e5c111a336b192f34d24f392b357bb`

This exactly matches `receipts/installed-driver.json`. Line 163’s superseded value was truncated.

## Discrepancies and residual risk

- The live Hermes dirty tree has drifted since sealing:
  - sealed status hash: `121b6303...6a90c`
  - current status hash: `3f30c203...f529d4`
  - Therefore PASS applies only to the immutable v19 bundle, not the current worktree.
- Running `independent_verify_candidate.py` directly without a rehydrated runtime fails because its recorded original installed runtime was intentionally removed. The self-contained bare bootstrap and sealed-wheel rehydration both pass, so this is a verifier-entrypoint portability limitation rather than a byte-integrity failure.
- Trust is hash-based and unsigned; external authenticity and operator/admin compromise remain outside the sealed trust boundary.
- Candidate remains pending multi-lane review and is not release authorization.