I read this as a read-only release-provenance audit - I’ll locate the v38 artifacts and ledger schema, independently recompute every named digest and seal, then exercise the delivered root through its direct verification paths and return a cryptographic verdict.


The three audit roots are identified. I’m now resolving the freeze contract and ledger entry against the verifier implementations before running fresh delivered-root checks, so the recomputation is independent of the receipts rather than merely trusting their PASS fields.


The direct isolated verifier and bootstrap both pass, including a fresh sealed-wheel install, rehydration, profile receipt enforcement, socket provenance, and Ty execution. One custom inventory assertion was overstrict on count semantics; I’m isolating whether it is only an expected self-exclusion (candidate/inventory/seal) or an actual byte mismatch before assigning the verdict.


I read this as the final read-only release-provenance verdict - I recomputed the full v38 chain and directly exercised the delivered root.

# Cryptographic verdict: PASS

Candidate `d1109d8f78aaccf949ec4f664d9e62584c3cca33032030518bc3e2d712239112` is internally consistent and cryptographically bound across all three roots and ledger line 169.

## Core provenance

- Candidate derivation recomputed from canonical product inputs: **match**
- Product binding:
  - file: `72fa416b447c48327993ab03482892572104887acef4b64eac98285d2d4e0e48`
  - document: `1b016220cbe3fd04df200035917e99f7dbdf5a73246c4f428f491d67be95611c`
- Hermes wheel: `f8b3c779c58435dd33f8f9bbc89e9823bd09f81367a27366c6d678270c1860b1`
- Profile wheel: `a56da2417df0912f3fe407c0b78befd7362207d1c8a35271000af46701ba79d2`
- Corrected Ty wheel: `932d4552233cfbaa325ddc3db5982150a37f437cf94a332eb3869052148bfe4c`
- Materializer: `6d2ae683562ce61e3cb2a22d4e97f776d9d1cd43b68b713fbfb3be02e9fcf986`
- All 18 qualification-tool hashes matched their sealed package/script bytes.
- All 109 wheel RECORD inventories, sizes, and member hashes passed.

## Roots, inventories, and seals

- Prefreeze: 395 files; 392 inventory entries plus the three intentionally self-excluded generated documents.
- Prefreeze inventory, candidate, product binding, expected state, and `SEAL.json` self-digests passed.
- Postfreeze inventory: 481 entries, exact match to prefreeze root.
- Receipt inventory: all 27 files matched.
- Delivered inventory: 482 entries, exact match.
- No symlinks or writable paths; roots are `0500`, files `0400`.

Exact seal bytes:

- Prefreeze `SEAL.json`: `257498e6aa2db7107ee24223a29b09f2e26c3d493869dc21206688be24b037b9`
- Postfreeze seal in receipts: `3002d815d7523c2971c990544d92c1f0d16fd51781f83d9d636ef6336b5878f6`
- Postfreeze seal in delivered root: same digest and **byte-for-byte identical**
- Delivered-bundle seal: `54be54cf89720057486596a21941ec5d456a1c54148f66dbde0475503a752f67`
- Receipt seal: `52b7de2d30d99f38db6f73ad70ebe9a21c99449348f069cf3d1f29f5cab745c8`

## Authority, profile, socket, direct URL, and Ty

- All three registry/ledger chains recomputed row-by-row, including previous-hash links, document hashes, and registry cross-links.
- Final authority:
  - registry head: `b24fd4e1b0b25655f18c6445a1920c30f274bc979556ef0a21494461dd78161d`
  - ledger head: `55e9d74c02c51220410780e56bd1e1a7eeaf89ee55afd2f598d97b67a3a58fb4`
- Profile receipt and 749-test manifest/artifact bindings passed.
- Source and installed socket transcripts independently matched canonical hashes and revoke/cleanup invariants.
- Direct-URL portable provenance matched both sealed wheel archives.
- Fresh Ty execution through bootstrap:
  - Python target `3.12`
  - 809 diagnostics
  - raw: `d01195a6c0de359b77948625d1e97c35cffbc7dcd145daaa4eed1a5c252ce063`
  - semantic: `ba03fe2e484683a8bdba0121f014caf614891c84da06a674a25314da1fce658a`
  - capability diagnostics: `0`

## Fresh delivered-root execution

Under an empty hostile environment:

- Standalone independent verifier: `TASK26_INDEPENDENT_CANDIDATE_PASS`
- Frozen bootstrap: `TASK26_FROZEN_BOOTSTRAP_PASS`
- Fresh sealed-wheel installation and rehydration: `ACTUAL_INSTALLED_GOLDEN_PATH_PASS`
- Rehydrated origin isolation passed.
- Profile package/receipt validation passed with 749 tests bound.
- Fresh Ty execution passed with exact sealed diagnostics.
- No temporary verifier/runtime residue remained.

## Ledger line 169

Every SHA-256 claim on `.omo/start-work/ledger.jsonl:169` resolved to the named artifact bytes: **25/25 resolved, 0 unresolved**. Test logs also contain the claimed 306 focused, 76 expanded, 8,552 gateway, 204+204 parser, 131 lifecycle, 32 direct-URL, 14 Ty-target, and 749 profile passes.

No files were edited.