Every ledger, every publication

This index measures nothing itself · it cannot make a refusal disappear · a ledger that is wrong is wrong here too, twice, with both digests shown

Reading a delta

A change in a headline counter between two runs is a change in what the world served, in what the probe asked, or in the probe itself. The probe version sits on every row so the third case can be ruled out before the first two are argued.

A counter can move while the published 95 percent intervals of the two runs still overlap. That is a move this measurement cannot distinguish from sampling noise, and it is counted separately here so a re-run is not mistaken for a finding.

A row is appended when a ledger publishes a digest this file has not recorded before. Prior rows are never edited or removed, including when a later run makes an earlier one look bad.

Not a measurement of its own. This index does not fetch any subject, does not score any ledger and cannot make a refusal disappear. If a ledger is wrong, it is wrong here too, twice, with both digests shown.

Real world asset disclosure interface survey

/rwa/ · 4 publication s · The population is frozen in the expectations file and identical across runs, so a count that moves is an issuer that changed what it serves. Still not a sector rate: the population is what this node already tracks.

the headline counters did not move between the last two runs. The digests still differ because timestamps and per row detail differ.

PYTHONPATH=engine python3 engine/tools/rwa_disclosure_run.py run

EDGAR and Federal Reserve grounded claim corpus

/grounded-claims/ · 6 publication s · The corpus is frozen in the expectations file and identical across runs, so a count that moves is a regulator page that changed under a citation this node already made.

the headline counters did not move between the last two runs. The digests still differ because timestamps and per row detail differ.

PYTHONPATH=engine python3 engine/tools/grounded_claim_run.py run

ERC-8004 Base refusal ledger

/erc8004/ · 3 publication s · Two runs of this ledger are two samples, not two looks at the same set. Each run pins a fresh Base block and draws 500 agent ids seeded by that block hash, from a registry that keeps growing, so the rows compared here overlap only by chance. A count that moves by single digits is sampling noise before it is news. The published rate and its 95 percent interval are the comparison that means something, and they are shown below the counts.

PYTHONPATH=engine python3 engine/tools/erc8004_probe_run.py --sample 500

Transparency log batch monitor

/tlog/ · 5 publication s · The same 23 logs every batch, so counts are directly comparable. What is not comparable is the cold start: the first batch held no prior checkpoint for any log and every batch after it does, which changes what some limbs can even reach.

the headline counters did not move between the last two runs. The digests still differ because timestamps and per row detail differ.

PYTHONPATH=engine python3 engine/tools/tlog_monitor_run.py run

SLSA and PEP 740 census of this node's own dependencies

/slsa/ · 2 publication s · A census, not a sample: both runs cover every distribution pip resolves for this node's requirements file. A count that moves is a real change in what PyPI served or in what the requirements resolve to, and neither is noise.

the headline counters did not move between the last two runs. The digests still differ because timestamps and per row detail differ.

/tmp/slsa_venv/bin/python engine/tools/slsa_provenance_run.py run

Machine readable