Verify without Thalor code

Everything published here is a file with a checksum, chained to the entry before it. Two commands and a standard library are enough to check it.

1 · The snapshot

Snapshot NS-000002-20260902T102622Z · log seq 2 · as of 2026-09-01. Files: assets.json, checksums.sha256, entry.json, manifest.json, northstar.json, sessions.json.

mkdir -p NS-000002-20260902T102622Z && cd NS-000002-20260902T102622Z
for f in assets.json checksums.sha256 entry.json manifest.json northstar.json sessions.json; do curl -sSO https://watch.thalorworks.com/snapshots/NS-000002-20260902T102622Z/$f; done
sha256sum -c checksums.sha256        # shasum -a 256 -c checksums.sha256 on macOS

Expected: every file OK. Then open entry.json: its entry_hash must be

ffd1847151009f32f609916943be6911173faa068934241c8782a617f48760fb

2 · The chain

Ten lines of Python over the Log file, ledger.jsonl, check every link and every hash back to genesis.

curl -sSO https://watch.thalorworks.com/ledger.jsonl
python3 - <<'V'
import json, hashlib
prev = '0' * 64
for line in open('ledger.jsonl'):
    e = json.loads(line); h = e.pop('entry_hash')
    assert e['prev_hash'] == prev, f"chain break at seq {e['seq']}"
    assert hashlib.sha256(json.dumps(e, sort_keys=True, separators=(',', ':')).encode()).hexdigest() == h, f"content altered at seq {e['seq']}"
    prev = h
print('chain intact, head', prev)
V

Expected head: ffd1847151009f32f609916943be6911173faa068934241c8782a617f48760fb.

3 · The anchors

The head hash is published in places this server does not control. Compare the head above with each:

seq 2 · git:github.com/thalorworks/watch-anchors#1f638751d450a5ec15ff0d246129eab8f5c0fea5 · 2026-09-02T10:33:27Z · ffd184715100…
seq 2 · git:github.com/thalorworks/watch-anchors#8eac18d4a72f9fe9494c5140690104962edad6a0 · 2026-09-02T10:29:10Z · ffd184715100…

Anchor targets: the public thalorworks/watch-anchors git repository (one commit per snapshot; the commit timestamp is the anchor), maury.thalorworks.com/.well-known/thalor-watch-head on a different host and deploy, and the weekly HQ thread report, mailed and archived by people.

4 · The evidence

Each log entry names the SHA-256 digests of the OSea session bundles it consumed (session_digests). A digest is the hash of a bundle's own checksums.sha256, so it commits to every byte of every stream. The bundles themselves are held on the node that produced them and on this server; evidentiary access is by request on the internal tier.

What this does not prove

That a single node's telemetry is unforgeable by a determined insider with physical access to that node. That becomes true only with diverse custodians and cross-attestation between hulls in one harbor (Stage 3). See method.