entries
32
native
31
published
14
withheld
17
chains
4

Sealed public Record · 2026-10-27

This snapshot has 32 entries. That is 31 native rows plus one historical summary.

The native rows are 14 published rows and 17 withheld rows across four chains.

The commissioning chain is rows 1 to 19 and the final entry is live-run row 2.

In this snapshot, commissioning row 18 names the amended purpose file by its hash and the Witness key signs that row. Row 19 binds the receipt digest of the filmed run. Live-run row 2 ran on that named purpose. It says “draft” because of the reference its readings were taken against, and those readings were recorded.

Row 15 enrolls the Witness key used for these commissioning-chain records, and Root signed it.

As a public reader you can verify the chain links and the Root and Witness signatures over this_hash.

TELOS Record of Trust root key (Ed25519), fingerprint sha256:d7fa85af712439c614fb25cdac293b783c0c0240ac79efb57f659c0f60bea8bb. Published at github.com/TELOS-Labs-AI/record-of-trust.

You verify it offline with check_public.py and Python 3.11 or newer.

Download the public Record (ZIP):

Current download (includes a checker fix, 31 Oct)

SHA256SUMS fingerprint: d9bbaa7159024124dc2509d4f3f53f1466164fb3d10042de4e3f0c7bcdd60338

Version cited in the GTC evaluation form (27 Oct)

SHA256SUMS fingerprint: 808a4edeeac7ec90c5488a7fa2357c4fa2c3bda6aa6fea073744145e6982c4e1

The record entries in the two downloads are identical. They differ only in the checker, its notes and the file-checksum list.

Extract public-record/ from the ZIP into an empty folder, then run Step 1 from that folder.

Check it yourself

Step 1. Download the public Record zip (telos-public-record-20261031b.zip) from this page, unzip it in an empty folder and cd public-record. Create the Python environment outside that folder, because the checker treats any extra file in it as a failure (reason SUMS).

python3 -m venv ~/telos-venv
PY="$HOME/telos-venv/bin/python"
shasum -a 256 SHA256SUMS          # must match the public fingerprint above
shasum -a 256 -c SHA256SUMS       # every line OK
"$PY" -m pip install --require-hashes -r requirements.txt
"$PY" -I -B check_public.py .

Expected: RESULT PASS. The chain links and the Root and Witness signatures show PASS. Fields hidden behind salted commitments and the withheld bodies of rows 17 to 19 show DECLARED. Rows 4 and 5 and code row 1 show NOT VERIFIED because they have no recorded signed message.

Step 2. Make it fail. Copy the folder. In the copy's record-of-trust-export.json, change one character of row 19's this_hash and rerun. Expected: exit 1 with a FAIL line. The original still passes.

Row index · 32 rows

To check the Record, use the zip above. These links are for reading single files.

Individual files · 45 files