Ledger
What the layer did, in aggregate. No party is named, no commitment is identified, and no figure here is an estimate: the Ledger is counts and rates over settled commitments.
The figures
Five aggregates, named as a machine will read them. The value column is a dash because there is nothing to put in it yet, and a dash is the whole point of publishing the table now.
Counting
What each figure counts, written down before there is anything to count. A counting rule published after the count is a counting rule nobody can check.
The sum of every hold that is open on a party's own rail. Recourse never holds it, so this is money sitting in the parties' accounts under an instruction, not a balance.
A commitment counts from the event that funds it. A link that was opened and never signed is not a commitment.
Per unit, not per commitment: units that passed the standard and that neither party disputed inside the window, over units claimed.
From the close of the evidence window to the ruling event. Time spent waiting for evidence is the parties' time, not the layer's.
Panel decisions that reversed a machine ruling, over panel decisions. A high number is a fault in the rules, and it publishes either way.
Why it is empty
Nothing has settled on this deployment, so there is nothing to aggregate.
Verification, adjudication, and party records are specified in the Rulebook and reserved in the workspace; they are not built. Until commitments settle in production this page carries no numbers, and it will not carry sample ones. A ledger with made-up rows in it is not a ledger.
What is built and what is not is listed on the front page, counted from the repository at build time rather than asserted.
Per party
The Ledger is the layer. A single party's figures are that party's record, and they publish only within the scope the party consented to.
A counterparty to a live commitment always sees the other party’s full figures, whatever that party’s public scope is. That is rule C2, not a setting.