Every link is checked as it draws. The connector between two nodes is green when a block's prev_hash equals the seal of the block below it. If it ever doesn't, that joint turns red and the exact mismatch is printed in place — you don't have to go looking for the break, it shows itself.
The arming dance, in one tap. Every module 404s after a deploy until something hits its /x/ prefix.
green = armed. A 401 counts, because the router loads the module and matches the action before checking auth, so a key demand proves the route is live.
amber = loaded but its status action is throwing.
red = genuinely missing from modules/.
not run yet
Pages
not checked yet
Break glass
If the chain ever breaks
This does not repair anything. Repairing a broken chain is the operator rewriting the record — the one thing this platform exists to make impossible. It captures the break instead, so its exact shape stays provable.
1. freeze — read and pin the current tip 2. locate — walk the links, name the first block whose prev_hash stops matching 3. export — pull every record to this phone as JSON 4. externalise — hand the frozen tip to the witness network
standing by
not loaded
not loaded
Unique visitors is not counted anywhere yet. Nothing in server.py records a visit, so no route can report it. Everything above is decision and demo activity, not people.