Measurement methodology
How the Integrity Services suite measures
The per-instrument battery for Integrity Services, 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 Integrity Services suite hub.
What this suite measures, and why
The Integrity Services suite measures other people’s trust surfaces. One service traces every number on a trading UI through its full chain — component, loader, artifact, publisher, computation — with FABRICATED as a first-class finding status. The other proves that a CI gate can actually fail, by planting violations the gate must catch in self-reverting drills, and grades the evidence with a receipt taxonomy: BEHAVIORAL, STRUCTURAL, DECLARED-GAP.
Both methods ran on us before they were offered to anyone. The lineage audit has been executed twice on our own cockpit and caught real fabrications — hardcoded statistics, random-number telemetry. The falsification drills found one of our own parity gates green over nothing. A dashboard nobody has traced and a gate that has only ever passed are the same object: an unexamined claim.
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 service that traces every number on a trading UI through its full chain of custody — component, loader, artifact, publisher, computation — and names what it finds, with FABRICATED as a first-class finding status.
- Component → loader → artifact → publisher → computation trace for every displayed number
- A finding taxonomy in which FABRICATED is a first-class status, not a euphemism
- Method proven on ourselves — executed twice on our own cockpit, where it caught real fabrications: hardcoded statistics and random-number telemetry
Honest limit: The audit establishes what a number’s lineage is, not whether the methodology behind it is good. A fully traced number can still come from a bad model — that is a different audit.
Full instrument page →
A service and toolkit that proves a CI gate can actually fail: violations the gate must catch are planted in self-reverting drills, and the evidence is graded with a receipt taxonomy — BEHAVIORAL, STRUCTURAL, DECLARED-GAP.
- Self-reverting drills — planted violations the gate must catch, then cleanly removed
- Receipt taxonomy — every gate’s evidence graded BEHAVIORAL, STRUCTURAL, or DECLARED-GAP
- Founding case — a drill found one of our own parity gates had been green over nothing
Honest limit: The kit proves a gate can fail; it does not prove the gate catches everything. A gate that has only ever passed proves nothing — and a drill that ran once, long ago, decays toward the same state, which is why drills are designed to be repeatable.
Full instrument page →
The receipts this suite will publish
Every measurement from the Integrity Services 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 Integrity Services 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.