# Artefact manifest — the sealed record (SHA-256)

**What this is.** The paper's claims are written to be assessable on
its sealed record. Public release of the experiment harness is
deferred (announced future work); this manifest publishes the
SHA-256 identity of every artefact the paper's numbers derive from,
so any later disclosure — full or partial — is verifiable against
commitments made at publication time.

**Derivation discipline.** This manifest is derived from the internal
verification record. Repository, branch and checkout names, hosts,
and internal record identifiers are neutralised as bracketed labels,
and file display names are neutralised where they carry internal
names — the hash is the identity, and the private archive's own
checksum file carries the on-disk names. **Every hash, size, commit
identifier, gate and number is verbatim.**

## Part I — epistemic-channels programme (sealed arms and grids)

All files below are the complete sealed record Part I's tables derive
from; hashes are SHA-256 over file bytes, sizes in bytes.

    30edd857e60911e2076c966df68d24de99cafc81c6d20e7925c0cef705239ffd    40,012  arm-untreated-8726a64.jsonl
    da7aa020f8763a54e7a7f326e506d6132518afa5ef38baae35e67b1860957d0d    42,407  arm-treated-ba0b961.jsonl
    888d0213e5eabec9d9696c6c7d310b7c18cd370aa6b3f26f68a94e7e5ad68316    42,407  arm-current-main-21e1475.jsonl
    617c7da33ae16fbe4a615691cf9d89266c840d8120efa74616cd4e48c7f8ab4b     3,201  [arm-corroboration-scorer].py  (display name neutralised; the §4.1 corroboration scorer)
    937b3520b7b7f232ec75205d40b4c3f0b0b0e63e8fe8fdbea337068f52d05e11    69,194  degradation-provenance/results-55-runs.jsonl  (§4.2)
    0e946dc9f11f3fafc8773c0d9b02ca353830e5ce7a7c7ad9b507dae24bb4eab3     1,545  degradation-provenance/instrument-validation.jsonl
    73c67f5829f7c474724b8da81d3f3839d9e7679dde0d69cc4ca51b8e526d40f3    74,785  degradation-availability/results-55-runs.jsonl  (§4.3)
    b356361434322cc00f70433b09edc5e4ceb2c58801be8bbd8933537893bcd552       877  degradation-availability/instrument-validation.jsonl
    30bdf8d508367f104522b3752969224479c9796be1073e15a7bf0277cf1cc997   144,472  degradation-marks/results-110-runs.jsonl  (§4.4)
    5c2bda3c6e8e7ec29ea7c66be9837019ca225d02c9b70793186913b3871c452a     1,685  degradation-marks/instrument-validation.jsonl
    1a5e9d55932bf8ff66d6a9d0ca2298e9fb3563d884d9fc4fa4ee6021cd323836     4,737  degradation-marks/independent-verification-receipt.md

Pins. The three §4.1 arms are pinned by world-engine commits
`8726a64` (untreated) / `ba0b961` (treated) / `21e1475` (current
head). The §4.2 and §4.3 grid hashes above are the values pinned in
their registered design records before analysis; the §4.4 grid's
hash is the estate-side final recorded in its
independent-verification receipt (chain: execution estate →
transfer → committed store, hash-stable at each hop).

## Part I — §4.5 witnessed-strike collection (sealed)

The complete sealed record §4.5's numbers derive from, stored in the
private evidence archive's witnessed-strike set; identities
re-verified against the archive's stored bytes at derivation time.

    895d4b038ba7f5aad8892c20b3d740495108ef76ba2af066200d43a339406c5a 1,256,961  witness_collect_results.jsonl  (§4.5; 88 cells)
    cd994994ecd3f350df9767043d7671779602160d4ddf77fd896379ed8edeae7e    11,529  witness_gates-2026-08-29.jsonl  (pre-collection freeze gate receipts)
    e8a3feca68985d09e3cc63caa77808efdb0bcc5f83f0e99a31cd6444d56bdb31     7,850  wb_score.py  (the frozen-rule scorer, committed beside the evidence)
    914a4a00938693a96fadf86a1fa1e707c16c8cbace89bc0566af1b488b486924     9,603  container-stdout.log  (per-cell run log, banked before the run container's removal)

Pins. The built instrument is pinned by its tree aggregate
`02445d7c81ded537e6d273b04db3581a69ed6dac1dcbf57b2d5e669a4e46b7ef`
(== the value frozen with the preregistration) and driver sha256
`85dcbdd9b23a4291472ca8e892e12ea93d62525c5c49d671d1b16bad432d5845`.
The two untreated anchor cells reproduce the frozen pre-collection
gate verdict arrays — sighted `168e5323…` byte-exact, blind matching
the recorded prefix `a1ee2230…`, both checkable in full against the
gate-receipts file above. The self-verifying preservation archive
(instrument tree, driver, version-control lineage and results in one
read-only object, `e9423279…`) is recorded as its documented value,
relied on as preserved, not re-hashed for this manifest.

## Part II — duty-economy programme (from the consolidation's inventory)

- **Archive:** `[private-evidence-archive]/SHA256SUMS` verified — all
  six tarballs OK (`e1-runs`, `e2-runs`, `e3-main-runs`,
  `[e3-subject-tree-runs]` [display name neutralised],
  `e5-runs`, `t0-runs`).
- **Frozen scorer identity:** [e3-subject-tree] `score_e3.py` is byte-identical to the
  E3-V3 freeze blob `c7855be8…` and `run_e3_batches.sh` to `d260a803…`;
  the freeze's `a6_driver.py` (`6d7be88c…`) and `run_e3.sh` (`27b09dad…`)
  blobs are present in history — the current [e3-subject-tree] carries two
  post-closure commits (maintenance)
  that moved those two files *after* ratification, which is expected and
  does not touch the frozen collection. [e5-subject-tree] `score_e5.py` is byte-identical
  to the E5 scorer blob `f40c5340…`. `m1_registry.py` declares
  `m1-registry-1` (E1/E2); the E5 set scored under `m1-registry-e5-1`.
- **Commit pins verified to exist:** [experiments-repo] `2e65c290` (E1 apparatus),
  [harness-repo] `7beb429` (E1 harness) and `bfe2149` (E2 subject pin), the E3 subject source — `21e45bdc…`, the E5 subject tree's freeze mint `900e2676` and ratified tip
  `ff44fd4d`.
- **Copies are copies:** the main-tree mirrors of `E5-REPORT.md`,
  `E5-SCORES.json`, `e5-ct-freeze.md` are blob-identical to
  the E5 subject branch tip (the source); `E3-SCORES-assembled.json`
  is byte-identical between the [experiments-repo] and [e5-subject-tree] trees.
- **Not re-verified for this manifest:** the Docker/OCI image digests and
  wheel digests in `E3-SUBJECT-PIN.md` / `E3-V3-FREEZE.md` / `e5-pins.env`
  (subject wheels `ab279b90…`, `4d90f77a…`; base/runtime images) — the
  images live on the execution estate. Recorded as pinned values, relied on
  as documented, not re-hashed. Likewise the proxy-reported cost figure is the
  proxy's number, not recomputed.

### sha256 inventory (every file this consolidation relied on)

`[experiments-repo]/experiments/` (main @ 7d0e98c6):

    8d30959d45b1f0269b4d9d52c84615fd28cd1f01b31c1a405d2d342cb607addd  E1-REPORT.md
    75fb2e00c597b88e49a5890d4192b24dca3748c6abb5acc38458b381158e573a  E2-REPORT.md
    65f10da27ec28e79289eaebec3d9ae911ffd55d96d5531c8bf9892f8ba36566c  E3-REPORT.md
    a53ceaa98308662ba0d787764dfcd1159ec79d5b89011e0e134f8e3a980f08c6  E5-REPORT.md
    1ad4cbf345fc1d90d55814b59fea6cf1fa1b3b49a98c1db8ac5412eb18e1812b  E3-ASSEMBLED-COLLECTION.md
    6045d732dc79b88379fada04dae8c6480a66ae2f421a394522882751d346a4c1  E3-V3-FREEZE.md
    a927e6fc427ce2bf93baba407ccdfbb7d40968a460e7e1208dca7db2dc813294  E3-SUBJECT-PIN.md
    8b7cd6973e5e19f15b6ed475c1231caac450abd61bf783e32b85b3bb8ee3773b  E3-WHERE-THE-SUBJECT-LIVES.md
    fcfcf1437f3ce61222c3d52c24abf646618896b5e45faf1aac0ba76c02c4672f  E5-WHERE-THE-SUBJECT-LIVES.md
    20cdc828467abd5e0b53de253338a11a3a0544dcc863efedf12d44053f9fbfa3  e5-ct-freeze.md
    347ffd16b1e2d493157df3e38f7a2c68771202f26317a9486f9d27fb3bfd1312  E3-SCORES-assembled.json
    a66f8aed16e3dfc03fb3d0714bf7fc933d649a628e3477127720edb9ec7a4ba9  E5-SCORES.json
    c16036bc4a7d13130e89159e71ffcb0cab373022f9d00f0c5dfbcdeabc156e02  runs/E1-scores.json
    132231825e02f4fae7f8661809d5aafcb241aaa3f123a04f4e49259b8c3c3bba  runs/E2-scores.json
    2c20eb8326ef4c127c4da99722485fd51151768c1651e122a4d4bc62438022b4  runs/E0-baseline.json
    184e0271657ac1e78f3556ee58ab90299db526212ae893a228539a1a9f3a3b85  E0-REPORT.md
    787021e9670429127349b3f57a6693f9132cc0706da5b7eb2826a1d186e12828  E2-SEEDS.md
    73da26438f687205333a50c5d6a56c15b401f561e8da5dc3632296fa1b5e2fa0  score_e1.py
    4f19ddd31d9f50fef4ba1122103cae5183a057771555eff6a6f85d6a4eb26d88  score_e2.py
    8316df87c8651bd7d49eb624401d9f17c908533d9a45c64359849d1b1a1a653a  m1_registry.py
    36e6f8612a75ef3f67eacbf43fb935cbf013cedcebe08a8a0cd8749d9424d342  runs/e1-incident-001.md
    8bf46cbb4c0506759d06a5e43e7ad1e473c94c56adc80233e44a9b52d626bd66  V1-E3-ANCHORS-REPORT.md
    44a00f2b1690d7f26a67f93bd5ac05ac2fdd3eeed719362c1709f4c631e38ae3  E3-V2-ANCHORS-REPORT.md
    09af3c4b8ccc7651a28f92464d2535ff7b6fe9505a1a5c564d08e213c67db36b  E3-V2-ANCHORS-PRECOMMIT.md
    beeb4880e44176dd64ea2f08d26b763971787b21a6881dc584320fe3614e9cc9  E3-V2-A6GATE-PRECOMMIT.md
    29f40fc395df27e236e079de6bbc07b9ad5f59e2b3b7091ed6d8e5008a8b9bc2  E3-V2-A6GATE-RESULT.md
    d1617ae5f39f1b28aebf53115001f8fb5868d30ee771e7ae9f3dbd5b8af4babd  E3-V2-C2Q-EARLY-READ.md
    b9e69f5f19a001879f70c703ccd14e663daaa7c4d5ae0282ce9d6f7321a6946d  E3-V2-PROXY-VOID-RULING-NEEDED.md
    63118d049690a8bc9b19fb91659997e1cc248d349f8111c93979528d2c26c5be  E3-V3-PILOT-RATE-COUPLING.md
    a75e929e614c658fd161e2f59f387096297b1e3dfe7cc9b721b02c4618c8fccd  E3-FINDING-proxy-provenance.md
    f777eb5abf006fb63dbc76f6141b7d25c85810ede9bc80e9dfc0aee38e30d2d7  E3-FINDING-competence-vs-dynamics.md
    e31c954d9152539c6b73c469672839d3bb493e6907a3077d4510d8fa2e3f8943  E3-REPAIRS-OWED.md

`[experiments-repo]/docs/`:

    f7029d949f46cac846fe0e12d6d097eca965eaa3534d561018f4b3e33af33019  e2-perturbation-matrix.md
    767f510ecd4d5254cd860c5ae5f67920b367dfe934b2fd0bf600ade9907188c9  e5-oracle-experiment.md
    00ec7879c3f6c9530b3d6103c457421464af598e16b0b087166f188c6530015d  e5-interpretation-freezes.md

`[e3-subject-tree]/experiments/` (E3 subject branch @ 48cce551):

    ed823f2eef3abcd08dba1712ea3e472e9fabad4e22083bc2e2d3b1f8d4e22d0a  score_e3.py  (git blob c7855be8… = the freeze pin)
    340babc790cb13e35eb6f35b36def4ca16d07015fff17c8bd43b55b8febb12e8  e3v3-models-snapshot.json  (= the freeze's body digest)
    aa93e1c00d1cc261e9cab58e5c1ae445403255f3ae8a1f021ba9cfff6b0099bc  e3-prompts/orientation.txt  (tree 86e96b08… = the freeze pin; pack sha d0b71365… reproduced)

`[e5-subject-tree]/experiments/` (E5 subject branch @ ff44fd4d):

    d143d66ff312b3307da32fcbd730515aecd343bab78ceca39a54d4810601d225  score_e5.py  (git blob f40c5340… = the report's scorer pin)
    4281ed34cc51e2809801492e2a07ccc002c2fce2c95badc5069873a51b324809  score_e5_set.py
    ec25fa268a5ba55854fc3907b5dabf97e0f7d5f68fe08372b1e317867a37f319  e5_adapters.py
    8edc245bf491efca0a015d6e8cd0b4bc914b65e7b58c650112669a216874adfe  m1_registry_e5.py
    e08af8d3bb89a4106efc26fd682cea0453942b3a383622a2c78780399d1d14a1  e5-pins.env
    b68218106025fd2870e985249426906d4e0a212ab0fb4e5bf11cb3f3c8e52d8c  e5-ct.env
    d1271ac464b6904c94caca4dd18a1dd8850fa6c9486202c6bbbc3423d59db713  freeze_checks_e5.py

`[private-evidence-archive]/`:

    60d2c163bd41e8a390a6a66c215ef78d698f077e30b8e433093e43c3ac2f4c9c  SHA256SUMS
    dbc0249a29c4f537faf53385dfb9ab4e642344bfd2abdee5c1db2997cf512e02  e1-runs.tar.gz
    cc7b6815999390ddb608fcfce09f518500e9e207c2d93713db2ae408d42250ab  e2-runs.tar.gz
    ba29a3e4439bb1817cf51a34b5c261cdc9074478439a5f5ba30cb01132f86e1d  e3-main-runs.tar.gz
    c09b3cbd4ee57891540e6ceeec654d82a2b20d777c1471748664991cd4145e25  [e3-subject-tree-runs].tar.gz  (display name neutralised)
    f47fb1ea81aecace12904cb6b98635ebfb77dc7efc06850540932611d0002cfc  e5-runs.tar.gz
    21f24e4eee44c6843c0c76597e207b1956be42acc400155f8f8363a8dc03eff6  t0-runs.tar.gz

Hashes are over file bytes as stored (CRLF line endings preserved);
where a file is git-tracked, the archived copy was verified equal to
its commit through git's blob
hashing, and the four regenerated score files above are byte-identical to
these on-disk artefacts.

The four score files above (`E1-scores.json`, `E2-scores.json`,
`E3-SCORES-assembled.json`, `E5-SCORES.json`) regenerate
byte-identically from the archived raw trajectories under the frozen
scorers; the regeneration is recorded in the accompanying
verification receipts.