No mission, no capture. No receipt, no claim.
This cockpit points an instrument at AI receipts and tells the operator whether the receipts justify the claims the model wants to make. Every figure binds to a receipt on disk. Three of the first four substrates this instrument pointed at produced self-discarding verdicts. That is the system working, not failing.
The order the instrument works in.
What this instrument refuses to claim, on every substrate, every time.
The list is enforced in the rig source, not aspirational. What the rig refuses is part of what makes its claims credible.
Loss is allowed. Hidden loss is not.
A selection of receipts shipped on 2026-06-23. Every row is a commit on a branch under TFB main, every artifact carries a no-claim boundary inside it, every routing note pairs to a memo. Nothing enters the instrument as vague data; it enters as accountable evidence.
| UTC | Artifact | Source | Class | Receipt | State |
|---|---|---|---|---|---|
| 02:15 | Diagnostic basis memo | Telescope | internal | c60858c05c | in main |
| 02:45 | Wound matrix addendum 2 | Telescope | internal | c98b0c6378 | in main |
| 03:10 | Plan v5 vocabulary widening pre-registration | Telescope | methodology | ef2a97473b | in main |
| 12:30 | Class C perturbation discriminator verdict | Telescope | handoff | 7d5ba6a2b | in main |
| 17:40 | Distractor receipt observations | Telescope | handoff | 8380637bb | in main |
| 20:15 | Scorer stability audit across 9 runs | Telescope | handoff | 64a9c016c | in main |
| 21:30 | Class A and B methodology pre-registration | Telescope | methodology | 38dc70fbf | in main |
real Commit SHAs on the working branch · each artifact carries its own no-claim boundary block inside the memo file
A pattern is not truth yet.
Four substrates this instrument has pointed at so far. Three produced self-discarding verdicts on the rig's own internal data, the discipline working at the gate. The fourth is an ongoing read-only application on a separate research surface. Each substrate's verdict was bound to thresholds locked before the data existed.
A finding survives only if it holds across two independent vantages real
A signature seen from one vantage is a constellation, a chance alignment from a single position. Only one that survives a second independent vantage becomes a cluster. Permutation controls (outcome shuffle + event order shuffle) catch the constellations the model would otherwise want to keep.
First pointing. Pattern signature appeared on the named substrate; permutation control reached the same signature on shuffled data. The rig refused to promote.
K=2 partial pointing. Vocabulary saturated at the lock gate; zero candidates met the pre-locked support fraction. Receipt issued with the null verdict, not silently dropped.
K=2 anchor pointing on mini-swe-agent traces. Mode 1 outcome shuffle held (0/20 reached 2/2). Mode 2 event order shuffle reached 1/2 on 9 of 20 seeds. Filler-token saturation caught.
Six artifacts shipped to a separate research surface as third-party calibrated reads against thresholds locked in advance. Today: Class C verdict 6/8 BETWEEN, leaning toward semantic-structure.
Reality is the judge.
A finding becomes credible when independent vantages converge. Today's Class C perturbation experiment shows the full discipline in motion. A non-co-author cross-vendor reviewer PASSED the gate before execution; the rig pre-locked the discriminator thresholds before any data; the receipt landed in one of the pre-locked classes.
Receipt landed in BETWEEN, leaning toward semantic-structure
base 0/8 → adapter 6/8 → 75 percent of the way from memorization extreme toward semantic-structure extreme. The heal is not pure memorization, not fully name-decoupled. Both semantic structure and name tokens carry weight, neither alone is sufficient.
A concept can be useful and still limited.
A finding becomes a concept when its bounds are drawn and named. Today's substrate-wide scorer stability audit promoted one concept to the verified-limited tier, with its applicable domain, its non-applicable domains, and its allowed and refused uses written down before any external use.
When a substrate ships its runner source with each receipt, score deltas across runs can be attributed line-by-line to specific scorer-source changes. One such instance found across nine RM3 receipts spanning four days: `no_wrong_key_role_array` is the only predicate added then removed, and the removal maps to a measured 3-point base score drift on one specific surface.
c60858c05c (B.1 attribution) → 64a9c016c (substrate-wide audit) → routing note in handoff/
The H1 wound the doctrine warns about is its own build pair.
The build pair is the operator plus one AI design partner inside the same vendor family. The doctrine says nothing is real until a second independent vantage has seen it. One reviewer seat is open. The package is assembled, the receipts are in numbered order, and the design AI's own letters are sealed in Tier 2 so an independent verdict comes from the data first, the narrative second.
The reviewer reads Tier 1 (the reviewer brief, the methodology summary, eleven receipts in numbered order, the rig spec, and a runnable reference rig that reproduces a calibration receipt exactly) and writes a verdict. The verdict has three honest outcomes: the discipline held, one or more pieces did not hold, or one specific additional artifact would close the question. There is no wrong answer.
Every wound becomes a guardrail.
Failures are not hidden here; they are converted. A wound that is receipted becomes a rule the instrument carries forward, a scar, not a bandage. One real healing from today's run is on the table.
Memo at tfb_telescope/reports/rm3_wrong_key_distractor_vs_bodyline_recompute_receipt_observations_20260623.md · commit 8380637bb