Measurement methodology
How the Terminal suite measures
The per-instrument battery for The Terminal, the receipts each measurement will carry, and the honest state of what is published today. Looking for what you can buy in this family instead? That is the The Terminal suite hub.
What this suite measures, and why
The Terminal suite is the display layer under the same discipline as everything beneath it: a working quant cockpit of roughly ninety panels in which every displayed number carries its provenance — the git SHA and the sha256 of the source artifact it was computed from — or the panel enters an explicit LOCKED state and refuses to render. It does not measure a new quantity; it enforces that no quantity reaches a screen without proof of where it came from.
The July 2026 incident on our core engine included fake telemetry painted into a live cockpit — random numbers presented as a working system. The terminal is the structural answer, built as the anti-cockpit: it cannot display a number it cannot prove. A LOCKED panel is the design succeeding, not failing — an honest refusal where a dishonest system would have painted something plausible.
The measurement battery, per instrument
Each instrument’s battery is summarized from its own published specification. Every dimension follows the six-stage lifecycle defined on the methodology page — pre-registered, content-hashed, deterministic, and shipped with its can-fail proof. Written in the future tense because nothing has been measured yet.
A working quant cockpit — roughly ninety panels — in which a number renders only with its provenance attached: the git SHA of the code that produced it and the sha256 of the artifact it was read from. A panel that cannot prove its number enters a LOCKED state and refuses to render, visibly.
- Per-number provenance — every displayed value carries a git SHA plus the sha256 of its source artifact
- LOCKED state — a panel that cannot prove its number honestly refuses to render
- Fail-visible display doctrine — no silent placeholders, no painted telemetry, ever
Honest limit: The terminal displays what has been computed and proven — nothing else. A LOCKED panel is not an error to suppress; it is the honest state of an unproven number.
Full instrument page →
The receipts this suite will publish
Every measurement from the The Terminal suite carries the same receipt chain, as defined in the full receipt taxonomy. Four of the six receipt types apply from the first measurement onward:
📋
Pre-registration
Each instrument’s battery is written and content-hashed before its first data collection. Any post-hoc change to the methodology would change the hash, and would be visible.
🔗
Content hash
Data, code, and results are SHA-256 hashed, so a published result from this suite is recomputable: declared outputs from declared computation on declared inputs.
🧪
Can-fail proof
Every test in the battery ships with a demonstration that it could have failed — a known defect injected and detected. A test that cannot fail proves nothing.
💀
Kill entries
Hypotheses registered for this suite and killed by the data are published with the same visibility as registrations. No silent disappearances.
What is published today
MEASUREMENTS PUBLISHED: NOT YET PUBLISHED
Nothing. No measurement from the The Terminal suite has been published, and this page will say so until one has. That order of operations is deliberate: pre-registration means the methodology is public before the data exists, so no result from this suite can ever have shaped the method that produced it.
When the measurement pipeline goes live, this page links, per instrument: the registered methodology document and its hash, point-in-time data manifests, battery results with confidence intervals and honest nulls, the can-fail proof beside every test, and kill entries for whatever does not survive.