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-08-11 06:50 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 of real usage in the production ledger
518,432
as of build 2026-08-11 06:50 UTC
Test, agent, and operator-era traffic is excluded at query time by the platform's own hygiene conventions — the ledger itself is never rewritten. How that works.
844
statements today
44,245
this week
63,526
distinct actors, all time
61
verbs in the vocabulary
Source: GET /analytics/summary — a sold endpoint, documented in
the API reference. Refreshed by the platform every 15
minutes. The headline reads live through the same-origin
/api/summary proxy; the aggregates below re-render 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.
Navigated 18,467 Arrived 15,922 earned 13,975 Opened 4,549 progressed 3,659 Viewed 3,536 Engaged 3,426 experienced 2,282 hesitated 2,023 started 906 Top 10 of 61 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.
The site remembers itself
This website runs on the product it describes. Every deploy of empress.eco emits a statement — agent-sites-lane deployed this site — into the same ledger you're looking at, and this section reads those receipts back. (A build shows the receipts of prior deploys; the newest one lands moments after the page does.)
| Deploy | When (UTC) | Pages |
|---|---|---|
165f68e | 2026-08-11 00:37 | 28 |
3f2f6ea | 2026-08-10 22:45 | 28 |
8479a4f | 2026-08-07 03:37 | 28 |
6a042bb | 2026-07-28 16:16 | 28 |
26c4c8c | 2026-07-17 19:37 | 28 |
d038872 | 2026-07-17 18:23 | 28 |
54cb080 | 2026-07-17 15:54 | 28 |
87b5939 | 2026-07-15 03:32 | 28 |
Emitted by CI (POST /statements, web tenant), read back at build via
GET /activity/recent — the same two calls any tenant makes.
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.