The record · public, and public whatever it says

Completeness first, outcomes second.

A record is only worth reading if you can tell when something is missing from it. So the count of slots the committed schedule expected comes before any outcome on this page, and the two numbers sit next to each other.

01

Outcomes — all four, always.

The denominator includes the losses. It is the same denominator in every view of this page.

02

The best and worst thirty days.

One tile, on purpose. There is no view of this page that shows the good window without the bad one.

03

Every day in the record.

Newest first. The seal is filled only where the day's Merkle root is on chain.

Slots written against slots the committed schedule expected
Day	Anchored	Root	Written / expected	Outage	Missing

04

Recount it yourself.

Everything this page rendered came from one open endpoint.

The pack: /api/public/counts — the JSON behind this whole page. Open, CORS-open and cacheable, so you can mirror it.
A day's leaves: /api/public/leaves/:day — every leaf of a day, so you can rebuild its root without us.
One row's proof: /api/public/proof?day=&table=&id= — an inclusion proof against the anchored root.
The method: Methodology, including the expected base rate we pre-registered and the change-freeze rule that stops us editing any of this quietly.