# Record of Trust

This snapshot contains 32 entries: 31 native rows and one historical summary.
The native rows comprise 14 published rows and 17 withheld rows across four chains.
The commissioning chain contains rows 1–19; the final entry is live-run row 2.
Commissioning row 18 names and signs the purpose amendment; row 19 binds the current run's receipt digest.
Row 15 is the Root-signed enrollment of the Witness key used for these commissioning-chain records; it does not retroactively certify earlier rows.
A public reader verifies chain links and Root/Witness signatures over this_hash.
Some fields are shown as salted commitments. Content recomputation for committed rows needs the private TELOS package.
Keys bearing commitments have declared aliases outside the signed bytes; the private TELOS package opens each alias.
Commissioning bodies 17–19 are withheld; their body signatures are verified in the private TELOS package only.
The private TELOS package is the full check of those fields, the signed purpose and both receipts.
Legacy envelopes in commissioning rows 4 and 5 and code row 1 have no recorded signed message and are not verified.
Fields ending in signature_sha256 or envelope_sha256 are recorded digests.
The readings PA and canon pins are byte-identical across the two receipts.
We publish the root key ourselves. No third party vouches for it.
The prose date is 2026-10-27 ET; frozen.at is UTC.

The purpose named by commissioning row 18 includes the source-fidelity manifest digest 143cf282c9ca78d6900cffb154a5297a9b5638c2b9100575cdd343806756f4ff. The filmed execution path does not include the source-fidelity gate, and the run's journal records no source-fidelity result. Naming the manifest in the purpose is not evidence that the filmed run used it.

First run `shasum -a 256 -c SHA256SUMS`.
Then create a virtual environment outside this folder. check_public.py fails its SHA256SUMS check if any unlisted file sits inside it.
`python3 -m venv ../telos-record-venv`
`../telos-record-venv/bin/python -m pip install --require-hashes -r requirements.txt`
`../telos-record-venv/bin/python check_public.py .`
The checker supports Python 3.11 and newer.
If the dependency is missing, it prints `public_dependency_unavailable: install requirements.txt (see README)`, exits with code 3 and runs no checks.
The checker prints PASS for checks it performs and DECLARED for committed rows and withheld content bindings.
It prints NOT VERIFIED for the legacy envelopes.
The public checker compares the published entry files with the export, but it cannot recompute a redacted row's original content hash. A consistent change to a salted commitment in both places can therefore pass check_public.py. Detecting that substitution requires the private TELOS package's openings and cross-tier comparison. A valid signature over a declared row hash does not, by itself, authenticate the replacement commitment.
DECLARED results refer to the private TELOS package for the full check.
