The Two Observatories
The framework ships two windows onto the entangled state. They look related but answer different questions for different people. Knowing which one to open saves you a detour.
/state/ — public observatory | /apps/observer/ — private ops console | |
|---|---|---|
| Audience | anyone, no account | signed-in machine owners |
| Scope | the whole node: every public machine + the mesh | one chain at a time, never intermixed |
| Question it answers | "what is this node doing, and can I check it?" | "what is my machine doing, and where's that row?" |
/state/ — the public observatory
Open /state/ on any node. No login. Three layers:
- Time River — the live feed of state transitions flowing across the node, tick by tick, phase-locked to the 1.287 Hz system clock. This is the node's pulse made visible.
- THE MESH — one card per sovereign node (domain, alive, registry match, machine count, latest Zeqond), rendered straight from
GET /api/mesh. A dead peer shows as a dimmed card — fail-soft, same as the API. - Tick detail (
/state/detail.html) — click any row and get the full envelope page: THE GENERATED EQUATION typeset large, the CKO envelope fields, the verification block, and a live re-verify action that re-runs the check against the node right there in your browser. Every list entry is clickable; nothing dead-ends.
Use it to: show a skeptic the system running, eyeball mesh coherence, walk from any transition to its full proof without tooling.
/apps/observer/ — the private ops console
Open /apps/observer/ signed in. This is the working surface for your entangled state — one chain at a time, never intermixed:
- Scopes — switch between the foundation view and your machine's own entangled state; the console keeps them strictly separate.
- Per-application sections — your rows grouped by the app that wrote them (messaging transit receipts, contract firings, site deploys, ZSC reads…), plus per-Zeqond density so bursts stand out.
- Named sources — an engineer who connects a data source names it; members of the machine see those named sources, outsiders don't (
GET /api/chain/:slug/sourcesis member-gated for private machines). - Find / pull / save — search rows, pull fresh pages from the chain, and save views you return to.
Use it to: audit what your machine did at Zeqond N, trace which app wrote a row, keep an eye on a contract's firing pattern.
Rule of thumb
Verifying or showing someone else → /state/. Operating your own machine → /apps/observer/. Both read the same hash-linked entangled state underneath — the observatory is the telescope, the console is the cockpit.
Honest limits
/state/shows public-tier data only; private machines surface counts, not contents.- The observer requires a session — it's gated like every
/apps/*surface. - Neither page is the proof. The proof is the chain itself — both pages link every row back to envelopes you can verify with the offline scripts.