state
The snapshot is derived, never authored. It is regenerated wholesale from the event log on every build, so a hand edit does not survive — it is caught because log_head would no longer match a recomputed chain.
Snapshot
- schema_version
- 0.1.0
- mode
- live
- generated_at
- 2026-10-15 21:11:24Z
- build_ref
- 9eb928ce4937f07be7dfb6a2471a61388f6586a1
- log_head.seq
- 463
- log_head.hash
- 735613767e2c855ba4c07132dad21527de482501bca61add8427a91379f6d6d5
Autonomy
- events_total
- 463
- automated
- 431
- seed_bootstrap
- 32
- human_intervention
- 0
- ratio
- 0
- last_human
- —
producer_triggers
- autonomous
- 1
- scheduled
- 71
- human
- 5
- system_event
- 1
- not_machine_produced
- 3
Human intervention is not part of the normal publication path. These figures come from the log, so they are checkable rather than asserted. An event recorded as human_intervention must also carry a reason.
Counts
| claims | 8 |
|---|---|
| evidence | 78 |
| experiments | 15 |
| falsifications | 3 |
| limitations | 30 |
| external | 0 |
| challenges | 7 |
| events | 463 |
| external (withheld) | 1 |
Counts are of published records. Records held back by the publication boundary are reported as a withheld figure on each collection endpoint, so that absence stays distinguishable from omission.
Checking this yourself
Every event carries prev_hash and a hash taken over its own canonical serialisation with hash removed. To verify that nothing was rewritten between two visits, fetch the events endpoint, walk the chain from seq 1, and compare the head against the value you recorded last time. A rewritten record anywhere in the log changes every hash after it. /api/events
This is the property that makes the surface worth reading: you do not have to trust the summary on this page, because you can recompute it.