The observatory
The ledger, made visible.
Every ledger that wants to be believed has an explorer. This is ours — real production aggregates, rendered from the substrate at build (2026-07-07 19:03 UTC). Unlike a chain explorer, there is no drill-down by design: this ledger holds behavioral data, so you get the aggregate truth and never an individual's trail.
The stream
Statements arriving at the substrate right now, newest first — every play, read, navigation, and ticket earned becomes a permanent row in the ledger. Actors are reduced to irreversible tokens at the edge before this page ever sees them; what you're watching is real, and it is nobody's trail.
- listening for the substrate…
Source: GET /activity/recent, sanitized by an edge function
(/api/pulse) that holds the tenant key server-side. Polls every
~10 seconds.
Statements in the production ledger
384,603
Test traffic is excluded at query time by the platform's own hygiene conventions — the ledger itself is never rewritten. How that works.
993
statements today
4,959
this week
46,517
distinct actors, all time
48
verbs in the vocabulary
Source: GET /analytics/summary — a sold endpoint, documented in
the API reference. Refreshed by the platform every 15
minutes; this page re-renders on every deploy.
The vocabulary that emerged
Empress never rejects a verb it hasn't seen — so the vocabulary below wasn't
designed, it emerged from production. ADL standards
(experienced, passed) live beside verbs tenants minted
for themselves (reading-started, increment). This is
the any-verb principle as data.
experienced 15,007 scored 1,968 Progressed 1,322 reading-started 1,293 reset 1,269 increment 1,114 passed 989 loaded 965 started 945 initialized 906 Top 10 of 48 distinct verbs, by all-time statement count.
Who feeds the ledger
1 production tenant today:
swapp — the card platform at
swapp.eco, where every play, read, and answer
becomes a statement. Multi-tenant by design: your platform integrates
the same way, and your slice of this page is
isolated to you.
What you will never see here
No actor identifiers, no individual histories, no drill-down. The substrate serves per-actor truths only to the tenant that owns them, scoped by key at the SQL level — machine-verified isolation. An explorer should prove the ledger is alive, not leak what's inside it.