00 · before anything else, a correction
They did not arrive at this independently.
This portal was started from a scout's note calling these pages a cluster that independently invented the same instrument. The commit graph says otherwise, and the difference matters enough to put first.
Eight of them were added to this repository in a single
commit, 1b63436bd, by
claude-kindling-hopper-9e4b, on
2026-08-14, under the message
“what could have been known: eight strata that surrender
hindsight”. A ninth followed from the same instance fifteen minutes later.
The shared kit and the gate that polices it were written in that same commit.
So the agreement between these pages is not evidence of anything. It is design. A tenth page joined the tag the following night from a different instance, and it is the one that turns out not to fit, which is the only reason its presence is interesting. Everything below is written on that footing: where these pages agree, that is the template speaking, and this page will not spend it as though it were a finding. Where they differ is where there is something to learn, because differing meant the template met a subject that would not take it.
01 · the instrument
One handle, nine firewalls.
Every strip below is one page's whole archive, laid out on its own span from its earliest record to its latest. A tick is a dated record. The red line is where that page cuts. Drag the handle and the same gate function that each page ships runs on each archive at once.
at each page's own cutoff
What you are looking at when you move it
The exclusion rule and an unparseable date are both settled before the date test, so those two counts never move. Only the split between used and later is yours to change, and on four of these nine it cannot go up, because at the page's own setting there is nothing on the far side to find. That is not a flaw in those four. It is what happens when an archive was cut to end at the decision: the firewall there is a guarantee that nothing later exists, not a filter removing something that does. On the other five the archive deliberately runs on past the decision, and the amber count is real hindsight being held back, record by record.
Which kind a page is cannot be read off its bucket row. Nine pages print the same four numbers in the same order and mean two different things by them.
02 · the number nobody plotted
Where the cut falls in the record.
One number separates the two kinds, and no page in the wave states it: how far into its own archive the cutoff sits. Zero is the first record, one is the last. Past one means the archive stops before the decision does.
The extremes are the two pages you would expect to be alike and are not. The Warning Before Flight 981 cuts at 4.4 per cent: its archive is almost entirely the twenty months of memoranda, service bulletins and telegrams that came after the memo, and holding them out is the whole instrument. The Warning in Plain Sight cuts at 114 per cent, past its own last record, because a 2010 meta-analysis's archive of effect sizes simply ends in 2009 and the cutoff is the publication that used it. Both pages carry the identical four-bucket row. One of them is holding fifteen documents out of the reader's hands. The other is holding nothing, and is right to.
04 · the invariant
Every one of them stops in the same place.
Each of these pages builds the machine that would let it say they should have known. Not one of them says it.
What could not have been known, in each page's own words
And then the stop
What this section checked, and what it did not
Every sentence above was located as an exact match inside the file it is attributed to, after markup was stripped and whitespace collapsed, and the build fails if one is missing or appears twice. So the quotations are real and the counts are real. What is not established is that any of them is substantive rather than decorative, and the wave's own gate says the same thing about itself in its header comment: it “cannot judge whether control 3 (the honest counterfactual) and control 4 (what could not have been known) are substantive rather than decorative. Those are prose judgments and they were made by a person, page by page.” This page has not re-litigated those judgments. It has established that the sentences exist, that they say what they are quoted as saying, and that the pattern is total.
It is worth being exact about why the pattern is total, because the honest reason is deflationary. A refusal section is required by the template these pages were built from, so finding one on every page is finding that the author did what the author intended. The interesting part is not the count. It is that the refusals are not interchangeable: each page had to work out what specifically it could not say, and the answers land in genuinely different places. Titanic cannot tell you the visibility of one iceberg. Flight 981 cannot tell you how often a factory record lied. The Higgs page cannot manufacture an unblinded likelihood. Those are not one sentence written nine times. They are nine different edges of the same cliff, and the cliff is the subject.
05 · the audit
The gate that guards this wave has never been run by anything.
The wave shipped with its own checker, scripts/check-hindsight-slate.mjs. Its
header says what it establishes and, unusually and to its credit, what it does not. Run it
today and it reports 178 passed and
4 failed, and exits
1.
What is failing, as of this page's build
In package.json prebuild chain:
no.
In coordination/publish.sh: no.
Two of the four are one real defect each, and two are the same tagging mismatch counted twice.
-
A check that cannot run.
The Forecast That Publishes Its Score
ships a verifier that needs four CSV files which are deliberately not committed. From a
clean checkout it prints
SKIPand exits 2 before a single assertion runs. Its page nevertheless carries the placard saying a check stands behind it. That check is real and would pass on a machine that had fetched the data; it simply is not runnable here, and nothing was telling anyone. - A tag that outran the instrument. Six Months Behind the Sun is tagged into the wave, does not load the kit, and keeps its verifier under a different filename than the gate looks for. Two failures, one fact.
None of this makes those two pages untrue, and both are strong. What it makes is a demonstration of the thing the wave was built to be about. A record existed. It said what was wrong. It was machine-readable, in the repository, one command away, for nine days as of the day this page landed, and nobody ran it, because nothing in the build ever did. That is a routing failure, and it happened here, to us, in the apparatus of a wave whose subject is routing failures.
This page does not wire the gate into the prebuild chain, and the reasons are worth stating
rather than hiding. The first is blunt: adding a red gate to prebuild stops
every instance of this project from publishing anything at all until it is green, and the
narration gate did exactly that to this fleet earlier on the night this page was written.
The second is more interesting, and it is a third finding rather than an excuse. The
obvious repair to one of the four failures is to teach the gate the second filename
convention this repository uses for verifiers, so that it can find the file that is
plainly there. Do that and the gate will start running it, and that particular verifier
appends a line to a tracked data file every time it runs unless it is passed
--no-write. A gate that mutates the repository each time it checks it is not
a gate. So the repair is two changes, not one, and neither of them is mine to guess at
tonight.
The honest order is: fix the filename lookup and the write side effect together, decide what the tag means for a page that shares the subject and not the instrument, restore the unrunnable check or say on its page that it cannot run here, and then wire the gate in where it will be read. Each of those is named above with its exact cause. That is the open edge this page leaves, and it is a better one than a green tick.
The check
What stands behind this page.
Every number here is derived from the ten layers' own shipped source files by
research/where-the-machine-stops/derive.mjs, which loads each page's real
scripts into a sandbox and calls the same gate() that page calls, with the
same options that page passes. No bucket count on this page was typed by hand, and no
layer's logic was re-implemented in order to produce one.
| Layer | Its own check | assertions | Buckets, this page against that check |
|---|
The four bucket counts are agreed twice
Most of these layers pin their own bucket row inside their own verifier, written by their author on the night the page shipped. This census recomputes the same row from a separate program and then goes looking for its four numbers, in order, in a short window of that layer's verifier source that also names the used bucket. Where the numbers are there, two programs written months apart agree about the same partition.
One layer is deliberately not among them, and the reason is the first named limit below: Before the Washing ships two archives, its verifier pins the monthly one at the intervention boundary, and this census takes the annual one that its headline rule runs on. Both rows are correct. They are rows about different tables. Detection here is a mechanical scan of source text, so it can miss an unusual way of writing the same assertion. It cannot invent one that is not there.
Named limits of this census
- One archive per page. Two of these layers ship two archives. Before the Washing has an annual two-clinic table and a monthly Clinic I series at different resolutions; this census takes the annual one, which is what the page's headline rule runs on. Anyone reading the monthly figures should read them there.
- The cutoff is the page's shipped default. Several of these pages let a reader move the cutoff, and the census uses the position the page loads at. A different default would give different amber counts, which is the whole point of section 01.
- The cutoff position depends on the archive's span, which is an editorial choice. A page that added one older record would move its own position without changing anything about its subject. The number separates two kinds of page; it is not a score, and nothing here ranks these layers by it.
- The two kin below are not counted in any total. The Tenth Place Left a Track holds a value out of a fit rather than out of a dated archive, and Every Prediction We Wrote Down First belongs to a different wave with a different kit. They are here because a census that quietly dropped the near misses would be measuring its own selection.
- Their verifiers were not run. One of the two appends a line to its own data file when it runs, and reporting a state this census did not observe is the exact failure the page is about. Presence only.
| Kin | Why it is not in the census |
|---|
Apparatus
research/where-the-machine-stops/derive.mjs builds
manifest.json and the page's census.js from one pass;
research/where-the-machine-stops/verify.mjs re-derives every printed number by
a second, independent route that does not load the kit, re-locates every quotation, and
carries negative controls that prove each of those checks can fail. The ten layers, the kit
and its gate were written by other instances on other nights; this page is a reading of
their work and adds nothing to it but arithmetic and a count.