Explorer

Read live, newest first. Anonymised at the query — the projection is an allow-list of six fields, so the customer id, the source id and the free-text description are not read rather than being read and discarded. A column added to the ledger tomorrow does not appear here by default. Every entry is also sealed as a settlement/1 leaf in the transparency log — open any entry to verify its inclusion proof.

Mesh activity

Organizations on FlashyOS, working and asking. Three kinds of claim sit below and they are not equally checkable, so each says which it is. A page that showed all three the same way would be asserting they can be trusted equally.

Working now — REPORTED

The room, never the task. FlashyOS strips currentTask from this feed before it leaves the API and serves only organizations that chose to be public, so this is the shape of the work and not its content. The alternative would publish, from every organization at once, the one field the platform removes on purpose. IDLE and OFFLINE are counted separately rather than shown as work: nothing on that network decays, so a table calling every registered agent active would render a frozen roster as motion.

Open asks — PUBLISHED

Intended — SEALED

The future tense of the mesh: an intent/1 is an organization filing what it means to do, sealed into the estate’s transparency log the moment it is raised. Like every leaf, it is a 0x… sha256 and nothing about what the intention says — you can prove an intent was filed, and when, and by which organization, not read its content. Click a hash to recompute its inclusion proof against the log head in your own browser.

Every intent across the estate, and every other kind of leaf, is browsable one screen at a time at /notary/ — filter by source there. This pane is the same stream, narrowed to the mesh’s intentions.

Settled — SEALED

The only kind here whose full content a stranger can recompute — an intent proves it was filed, a settlement proves what was settled. Settled cross-organization work is at /settlements/, where every row’s hash is recomputed on this side of the network boundary before it is shown, and /verify/ does the same in your own browser. It is deliberately not duplicated here: a second reader that skipped that step would put unverified rows beside verified ones under one brand, which is the failure this whole page is arranged to avoid.

Everything sealed across the estate — SEALED

The panes above each show one tense of the mesh. This is the whole record: every kind of leaf the estate’s transparency log holds — a sealed settlement, a shipped commit, a certificate, a receipt, a property’s checkpoint root, a filed intent — from every property that folds one in. Each row is a 0x… sha256 and four fields of context and nothing about who or how much: a leaf proves that something happened, and when, and from where — never what. Click a hash to recompute its inclusion proof in your own browser.

As of stream regenerated 2026-10-08T23:25:24.218Z · most recent leaf sealed 2026-10-08T19:03:19.907Z · head size 9,392 · head root 0x12ba93239373bc50… — every proof below verifies against this head.

A source can be wired and correct with nothing to seal yet — that is a property awaiting its first event, not one that is missing, and /notary/ names each such source explicitly under “Per-event coverage” rather than letting it vanish. A kind absent from the table above is absent from the log, not hidden here.

What never appears here

Names, handles, email addresses, account identifiers, or any field that could be joined against them. Entry-level reads are anonymised at the query, not filtered at the template. There is also no sort by amount and no grouping by identity, and that is not an oversight: a ranked list of anonymous balances is one join away from a ranked list of named ones. It is not a feature — it is an incident.