Chancellor · The Judging-Week Soak · Live
The Long Watch
Eleven thousand five hundred twenty segments of governed work, run in the open
through judging week — every decision receipted, every halt published, and the watch
that keeps the run alive standing in frame.
3,557 / 11,520
segments done · the run advances one segment a minute
355 / 1,152
faults injected so far
3,428
chain entries under checkpoint
3,272 segments complete
285 halted — fail-closed, by design
30.9% of the judging-week run
launched 2026-11-01 · runs through finals, 2026-11-09
I
Graded Work
No agent marks its own homework.
42,684
steps of governed work executed, twelve to a segment — each graded at the gate before it was allowed to count, and each grade receipted in the chain
II
Gated Authority
Consequential acts wait at the gate.
285
segments halted fail-closed, in gold because a halt is the product working: the gate refused work a fault had corrupted, counted the refusal in the open, and the run went on
III
Kept Receipts
Every decision leaves a receipt you can verify offline.
3,428
audit entries under signed checkpoint in the published snapshot · 426 signed checkpoints · corrupted state files: 0 · verified cold at this refresh with the product's own verifier — the live log holds 3,435 entries; the tail past the newest checkpoint is not yet checkpointed, and the verifier says so rather than guessing
IV
KEEP — The Watch
The supervisor that notices, verifies, and resumes.
13 interruptions · 13 resumes
1 deliberate proof kill · 12 supervision losses — every one resumed from the last signed checkpoint, the chain verified across the break · the run's own chain verifications stand 426/426 ok · the newest checkpoint was written 7 seconds before this refresh
Drift is the one true failure this page exists to make visible — a run claiming
success for work whose final state failed its check. The drift counter above is expected to
read zero for the entire run; if it ever reads nonzero, that is the headline, and it will not
be edited away. The counters on this page are refreshed mechanically from the soak's own state
files, and the snapshot published beside the record lets any reader check every count.
Verify the chain yourself
Download the snapshot pair — they must sit side by side — install the package from the
repository, and run the verifier the product ships. Offline, no credentials, no network.
Exit 0 means the chain is intact and the newest signed checkpoint checks out.
python -m chancellor.verify_log audit-snapshot.jsonl