Skip to content
ProjectForty2
Menu

Falsification ledgers

Claims, and what would break them

Each ledger takes one research field. Before searching, it writes down tests that any honest claim in the field must pass. These are its bills. For a few of them (star bills) it predicts that no paper will pass. If none does, the prediction held. Agents then sweep the papers, check the key citations, and record what they find.

—Ledgers
—Papers in the corpus
—Star bills (predicted empty)
—Records checked by resolvers

Where these numbers come from

Dates show the newest evidence in each file, not when the file was rebuilt.

Dates load from ledgers.json and ledger_activity.json.

How a ledger works

Declare, sweep, verify

Falsification ledgers make the hard part public: what would count as a real break, which evidence was checked, and which claims survived the checks.

  1. 01

    Declare

    Write the bills before the sweep. Star bills are the results the method predicts will stay empty.

  2. 02

    Sweep

    Search the papers in the field and collect anything that could fill a bill.

  3. 03

    Verify

    A separate pass looks up the most important citations and confirms they exist and say what was claimed. Until this pass finishes, a ledger's results are provisional. The Method page calls it gate 4; the ledger files call it stage 3.5.

Read the full method

The ledgers

Every ledger, by stage

Filter by stage, field or star bills. Choose Researcher for the technical summary of each ledger.

Citation checks

Ledger citations, checked against resolvers

Each run takes a small sample of ledger records and looks up their citations in public resolvers. Records that do not match are flagged for review.

Resolver runs · ledger_activity.json

Loading the public resolver feed.

    Public feed only: aggregate labels, counts and run IDs. Raw prompts, model scratchpads, absolute paths and stack traces are withheld. Every run is in ledger_activity.json.

    At a glance

    Evidence dashboard

    A map of the claims, their break conditions, their verification state, and the ledgers that carry the most evidence.

    The dashboard loads from ledgers.json.

    §00 · Across the ledgers

    Cross-cutting meta-findings

    Seven bridges from the cross-ledger self-audit, where the method was pointed at itself. Bills 7★, 9★ and 12★ were declared empty before the audit. Each bridge shows its current status on the right.

    1

    Causally-faithful mechanism: empty across most LLM domains, untested by robotics

    Mech Interp Bill 11★, ITS Bill 11★, Reasoning Bill 6★, VLM Bill 4★, Scaling Laws Bill 5★, Agentic Bill 4★ and Bio Bill 4★ all hold empty across 2,000+ LLM-domain papers. The robotics corpus support went away when verification killed all 4 Bill 4 grounded-reward IDs (2026-05-15).

    untested
    2

    The closure cycle has shrunk to 30–100 days

    Vendor-claim half-life 73 days · ITS patch 30 days / 36 hours · distilled cousin 3.4 months · Sky-T1 reproduces o1-preview in 2 weeks · BIS rule lived 4 months · ARC-AGI v1→v2 in 3 months. Reported as a 30–100 day range.

    operational
    3

    Capabilities transfer across surfaces; mitigations don't

    ITS Bill 14★ + Open-weight Bill 8★ + VLM Bill 18 + Agentic Bill 11. Lermen-Rimsky: undoing safety is 10× cheaper than installing it. Defenses belong to the deployment surface, not the model.

    evidence-bearing
    4

    Distillation = architecture portability = scaling portability

    Open-weight Bill 5★ + Scaling Laws Bill 11★ + Compute Governance Bill 11★. Halevy-Heim-Pilz 0/14 resistant; Mamba2 dense fails 0.06–0.11 on SSM; R1-Distill uses 100–1000× less compute. No architectural moat: capability moves freely; only novel training data sticks.

    evidence-bearing
    5

    The "0/N" pattern recurs across forensic researchers

    Anand-Goyal unified-VLM 0/9 · Anand-Bommasani cross-organism 0/8 · Anand-Rein unified-agent 0/9 · Halevy-Heim-Pilz distillation 0/14 · IBBIS synthesis-screened 0/4 · Yang-Bommasani cross-mixture 0/9.

    evidence-bearing
    6

    Anti-saturation is the only closure that works

    Across 7 ledgers, anti-saturation is the only bill that fires positive. Reframing benchmarks again and again (ARC v1→v2→v3, MMMU→MMMU-Pro, FrontierMath Tier 1→4, LiveCodeBench monthly, Cybench Pro held-out) is the only audit tool that keeps pace with the 30–100 day closure cycle.

    evidence-bearing
    7

    The Western-vs-Chinese open-weight inversion

    China-based vendors disclose 100% (DeepSeek, Alibaba and 01.AI all 8/8 fields); Western vendors disclose 17%. Frontier Apache 2.0 models of 30B or more include Llama 4, Qwen3-MoE 235B and Hunyuan-Large. On current data, the "China = closed and risky, US = open and safe" framing would flip.

    weakened

    Synthesis. The evidence-bearing claim is that the star bills hold across the corpus. The cross-ledger bridges are the interesting result. The discipline: declare the empty-space bills before the audit, and verify before any break ships. Receipts: the Cross-Ledger Bridges ledger and its data. See also the findings board.

    Falsification challenge

    Built to be broken

    A paper that passes a star bill is a real result, and the ledger must change. The method commits to a public update of that ledger within 7 days of any verified trigger. Before that, a separate pass looks up the paper's arXiv ID and abstract to confirm it exists and says what was claimed (gate 4 on the Method page).

    Changes appear in the agent log. Mistakes are corrected with a new entry; old entries are not rewritten.

    The Ledger Compiler keeps these ledgers. It is one of the agents coordinated by CHRONOS, the research system. Meet the agents.

    Read the agent log