Protocols and papers
Calibration Ledger v9
The research ledger: a dated evidence map of what was tried, what the experiments rejected, and what replaced it.
Research ledger · pre-publication · not peer reviewed
- Printed title
- From model output to accepted state (Calibration Ledger, version 9)
- Format
- PDF, 23 pages
- Date
- 27 August 2026
- License
- Text CC BY 4.0, as stated in the document
What it means
The work began as an efficiency hypothesis: pass compact context cards between model phases instead of full history. The experiments rejected that story.
The ledger records how that failure redirected the work toward a control plane in which a model output is only a proposal, and accepted state advances only after current evidence, exact lineage, verification, and human acceptance.
An unverified attempt can add evidence. It cannot silently replace the last accepted result.
Page 1
A local pass remains valuable at L1-L2 and must not be narrated as L4-L5.
Page 18
How it functions
Each claim area carries a status label (IMPLEMENTED, TESTED, PROPOSED, or UNKNOWN) and cites its source artifacts. The ledger maps five layers: Delta Atlas, Calibration Ledger plus STP, Clutch, BespokeNode, and State Runner. It grades evidence on claim levels from L0, a declared design, to L5, production assurance.
Use the review order on page 23: reproduce the local gate, inspect the finite predicate and its counterexamples, read the Clutch studies in order, and treat any claim above its cited ceiling as unestablished. The document calls itself an orientation and evidence map, not a substitute for the source artifacts or an independent reproduction.
Status and claim boundary
Cover-marked RESEARCH LEDGER | PRE-PUBLICATION | NOT PEER REVIEWED. Evidence reaches L1 (local conformance) and L2 (reproduction on one Windows host); L3 to L5 are UNKNOWN. The control-plane results come from declared fixtures, one local State Runner run, and one Windows clean-room attestation. The Clutch studies used synthetic tasks with billed provider calls.
The full ten-stage STP lifecycle remains PROPOSED. The ledger does not establish product efficacy, production safety, useful delivery on real projects, independent-team replication, cross-platform behavior, or general cost savings.