Ledger Kernel · research-stack
MVP · records to 2026-09-23 · every number is from the project's records, listed at the end
seq 1Argumentclaim.asserted · anchors[0]

Research you can hold to account.

Every deep-research tool can search, read and write. None can be held to what it wrote. Here every claim, model call, dollar and judgment is an event you can open, replay and check. The report is prose; the reason is a ledger.

report.md · Findings Stripe caches status codes and response bodies for keyed requests once endpoint execution begins, replaying even 500 server errors on subsequent retries. high confidence · docs.stripe.com “Stripe’s idempotency works by saving the resulting status code and body of the first request made for any given idempotency key, regardless of whether it succeeds or fails. Subsequent requests with the same key return the same result, including 500 errors.” A1 fetch.done · status ok · docs.stripe.com bodies/<sha256_text>.zst · extracted text, bytes Stripe’s idempotency works by saving the resulting status code and body of the first request made for any given idempotency key, regardless of whether it succeeds or fails. Subsequent requests with the same key return the same result, including 500 errors. start end the model cites url + quote · the kernel resolves fetch_ref and [start, end) · rungs exact → nfc → folded GATE-4 · every resolved anchor decoded from the store and compared byte-for-byte 451 / 451 · 0 mismatches

A finding in a real report, and the page it came from. The model cited a URL and a quote; the kernel found the quote in the bytes it had fetched and stored the offsets. The POC gate re-read every resolved anchor from the store: 451 of 451 matched, 0 mismatches. The MVP kept the rule and ran it over twenty campaigns: 53 questions, 708 of 723 live claims linked into the Knowledge ledger, $8.27 in all.docs/GATE-POC.md check 4 · docs/SPEC-kernel.md §2 anchor resolution · the report: Gold-8 Verdicts, Q6

MVP gate · 53 of 53 questions · $8.27 16.42 over 672 expert-written items 30.8 points already on disk, unread 6 of 53 reports pass all four judged laws
seq 2Planfour doors

Four doors.

Questionpremise · load_bearing
The problem The output of deep research is prose you have to trust. Five questions a reader asks of a report, the dead end each one hits, and our own earlier tool's numbers. problem.html →
Evalbench.result · 16 Sep
The POC Twenty-eight packages, measured: 47 gated rows with no miss, eight checks with one miss drawn and fixed, eight questions against the old engine at 5 of 8. poc.html →
Runbuild log · 19–23 Sep
The MVP A dated build log, newest first: what was built or measured, the number it produced, and the record it came from — including the four numbers we had to take back. mvp.html →
Notethe instrument · 23 Sep
The measurement A model that cannot write at all — only score, choose or rate — found 30.8 benchmark points sitting unread on pages the runs had already paid for. Every judgment behind it cost $0.27. jev.html →

Not released. The MVP runs and the console is built; the repository is private. Ask for access and we send one message when a question of yours can be run and held to account.

Request access →

between them: how it works — the ledgers as rails, append-only, kill -9, replay at $0, budget — and the roadmap, 55 of the 56 MVP packages in, extraction and assembly next.

seq 3Evalbench.result

The headline numbers, each with its file.

EXTERNAL · 23 Sep
questions, rubrics and items written by other people; no run counted read the source its own rubric came from
GOLD-EXT · the clean ten
16.42
672 rubric items · recall 12.89 · analysis 27.16 · presentation 27.04
RECORDED
JEV · the funnel
207 / 500
recall items whose material was already on disk · 30.8 points, unread
RECORDED
JEV · spend
$0.27
every judgment of that measurement, four runs · output free
RECORDED
MVP · 19–21 Sep
rendered from the gate ledger by a program; a row it cannot give says not measured
GATE-MVP · runs
53 / 53 · $8.27
20 campaigns · 52 done · 1 gap · 531 paid calls · p50 93.6 s
MEASURED
E3 · six laws
106 / 106 · 120 / 212
L1, L3 by the ledger's rule · L2 L4 L5 L6 labelled: 6 of 53 pass all four
LABELLED
E1 · re-judge
4 of 8
better 3 · not-worse 1 · worse 4 · the bar is 6
MISSED BY TWO
POC · 16 Sep
the numbers the site opened with, unchanged
GATE · check 4
451 / 451
resolved anchors re-read byte-for-byte · 0 mismatches
PASS
GATE · 8 checks
7 of 8
check 8 fixed by FIX-590 the same day · in CI since
FIXED
E1 · side-by-side
5 of 8
not-worse 5 · worse 3 · the bar was 6
MISSED BY ONE

The POC values are bench.result events whose verdict is recomputed from value and target when the report renders. The MVP gate is rsk gate mvp report over the X2 ledger; a re-render of the same ledger is byte-identical. The external ten are one bench.result row per rubric item. Neither document is edited by hand.docs/GOLD-EXT-CLEAN.md · docs/GATE-MVP.md · docs/X2-REVIEW-2026-09-20.md · docs/BENCH-POC.md · docs/GATE-POC.md · docs/E1-2026-09-16.md