AINumbers / Verification desk / Evidence register

Evidence Register

A claim-level register for the public numbers on this site. Each registered claim is bound to the page it appears on, the date it was measured (as_of), the date its review is due (review_by), and a point-in-time snapshot of the exact source line it was registered against. When a page moves and its snapshot no longer matches, the register gate goes red until the claim is reviewed again.

What is registered here

ClaimCount keySource surfaceAs ofReview dueSnapshot
About page hero badge: '32 Categories'.categoriesabout.html2026-09-212026-12-20source/about-categories-badge.txt
About page 'Tool categories' stat row.categoriesabout.html2026-09-212026-12-20source/about-categories-stat.txt
About page floor-coverage stat: '661 / 661 live kernels carrying a digest-matched property-test floor, measured 2026-08-13'.fv.floorFlooredabout.html2026-09-212026-12-20source/about-fv-floor-coverage.txt
About page 'Integration hubs' stat row.guides.hubsabout.html2026-09-212026-12-20source/about-guides-hubs.txt
About page hero badge: '590 Tools'.tools.browserabout.html2026-09-212026-12-20source/about-tools-badge.txt
About page 'Browser-based tools' stat row.tools.browserabout.html2026-09-212026-12-20source/about-tools-stat.txt
About page proof-coverage stat: '661 / 661 eligible workflows carrying a real risc0 groth16 zero-knowledge proof'.zk.provenNodesabout.html2026-09-212026-12-20source/about-zk-proof-coverage.txt
DORA & Operational Resilience hub eyebrow: 'Cat-22 · DORA & Operational Resilience · 12 Tools'.hubTools.doraguides/dora-operational-resilience-hub.html2026-09-212026-12-20source/dora-hub-tools.txt
Fraud & Risk hub eyebrow: 'Cat-03 · Fraud & Risk · 10 Tools'.hubTools.fraudRiskguides/fraud-risk-hub.html2026-09-212026-12-20source/fraud-risk-hub-tools.txt
FV process explainer QC stat: '661 / 661' kernels with a digest-matched property-test floor.fv.floorTotalfv-explainer.html2026-09-212026-12-20source/fv-explainer-floor-coverage.txt
Homepage chains-table footer link: 'Browse all 368 chains'.chainsindex.html2026-09-212026-12-20source/index-chains-count.txt
Homepage 'Live MCP Tools' hero stat (count sentinel mcp.live: the servedNodes + pilot + EXPECTED_UTIL figure the counts engine derives).mcp.liveindex.html2026-09-222026-12-20source/index-mcp-live-tools.txt
Homepage proof-coverage sentence: '661 of 661 deterministic nodes carry a real risc0 groth16 zero-knowledge proof'.zk.provenNodesindex.html2026-09-212026-12-20source/index-zk-proven-of-total.txt
Homepage 'ZK-Proven Nodes' percentage stat.zk.provenPctindex.html2026-09-212026-12-20source/index-zk-proven-pct.txt
MCP page 'MCP tools, all read-only' stat row.mcp.livemcp.html2026-09-222026-12-20source/mcp-live-stat.txt
MCP page hero sentence: '16 flagship tools render as interactive widgets in chat'.mcp.widgetsmcp.html2026-09-212026-12-20source/mcp-widgets-hero.txt
MCP page body prose: build_workflow_links covers '148 named multi-tool workflows'.workflows.recipesmcp.html2026-09-212026-12-20source/mcp-workflow-recipes.txt
TradeTech & Trade Finance hub eyebrow: 'Cat-26 · TradeTech & Trade Finance · 11 Tools'.hubTools.tradetechguides/tradetech-hub.html2026-09-212026-12-20source/tradetech-hub-tools.txt

The machine-readable register is claims.json. Each row links its snapshot under /source/; the snapshot records the exact source line, the claim's scope, and its review commitment at the as_of date.

How the review discipline works

Registration is one direction of a two-sided control. The generator (gen-evidence-register.mjs) is the single writer for the register and the snapshots; the gate (check-evidence-register.mjs) re-derives every binding on every push and fails on field gaps, impossible dates, snapshot hash mismatches, or a page line that no longer matches its snapshot.

Snapshots are point-in-time evidence. The generator never rewrites one by itself: a moved page leaves the old snapshot in place and the gate red until a reviewer re-reads the new text and re-validates the claim. Reviews move forward only. A claim whose review date has passed stays red until it is reviewed, and the baseline of already-overdue claims can shrink at any review but only grow by a committed, deliberate re-pin.

Count freshness has its own live control: the number inside a registered sentinel is re-derived by the counts engine independently of this register, so a stale count is caught even between reviews. This register answers the other question: what did the page say when we last looked, and who owes the next look.