THE FOLD / RESPAWN / SECOND WIND / THE TWO-RUN GATE
THE TWO-RUN GATE
nothing enters the seal on one green run
1 WHAT IT IS · WHAT IT DOES · FACT OR FICTION
Nothing enters the seal on one green run. It has to produce the same result twice, from the shipped copy, in separate invocations. The claim is deliberately narrow: a thing that passes once has passed once; a thing that passes twice has ruled out the accidents that do not repeat — and that is a smaller class than it sounds.
LIT verified live over 4,000 trials of four suite kinds. A solid suite passes at 100% under one, two or three runs. A coin-flip flake survives one run 50.3% of the time and two runs 25.5% — the second run squares the survival probability, as independence predicts. An order-dependent test that passes only on its first invocation survives one run 100% of the time and two runs 0%. But a 10% flake still survives the two-run gate 80.8% of the time.
LIT verified live over 4,000 trials of four suite kinds. A solid suite passes at 100% under one, two or three runs. A coin-flip flake survives one run 50.3% of the time and two runs 25.5% — the second run squares the survival probability, as independence predicts. An order-dependent test that passes only on its first invocation survives one run 100% of the time and two runs 0%. But a 10% flake still survives the two-run gate 80.8% of the time.
2 HOW IT WAS WEAVED · AI + HUMAN
David (human) stated the rule and its exact scope in the same breath: “A thing that passes once passed once; a thing that passes twice has at least ruled out the accidents that do not repeat.” His frozen list carries two columns, run 1 and run 2, and a second list of what is not frozen and why — no Fortran corpus, no orchestrator, no agent has ever pressed the pedal, and one of the two ARM64 cross-checks was unavailable on the machine. Dropped 5 August 2026.
AVAN (AI) ran both of his suites twice here before building anything on them:
AVAN (AI) ran both of his suites twice here before building anything on them:
i13c reports 14/14 both times, jotf reports 29/29 both times, and the two output files are byte-for-byte identical. Then the gate itself was measured rather than assumed, which is where the modesty of the claim becomes visible — two runs are devastating against order-dependence and nearly useless against a rare flake. Both numbers are on the sphere.3 ONE DIMENSION
Four kinds of suite, and what each extra run costs them.
4 TWO DIMENSIONS · INTERACTIVE
Add runs to the gate and watch each flake’s survival.
5 THREE DIMENSIONS + AVAN’S INVERSE
The green forward object: survival curves under repeated runs.
AVAN’s addition (the inverse-companion): the forward reading is “run it twice before you believe it.” The inverse is that repetition only tests the things that vary between repetitions. A defect that is deterministic — wrong arithmetic, a wrong field walked, a threshold taken from hope — reproduces perfectly, and the two-run gate certifies it with the same confidence it certifies correctness. Read backwards, running twice is not a check on the answer at all; it is a check on the apparatus, and its silence says only that the machine is consistent, which a broken machine also is.
LIT over 1,500 trials of four suite kinds, a solid suite passes at 100% under one, two or three runs; a coin-flip flake survives one run about half the time and two runs about a quarter, the second run squaring the survival probability as independence predicts; an order-dependent test that passes only on its first invocation survives one run 100% of the time and two runs 0%; but a 10% flake still survives the two-run gate around 81% of the time
FIG From David's FROZEN-two-run drop, 2026-08-05. He stated the rule and its exact scope together: 'A thing that passes once passed once; a thing that passes twice has at least ruled out the accidents that do not repeat.' His frozen list carries two columns and a second list of what is NOT frozen and why - no Fortran corpus, no orchestrator, no agent has ever pressed the pedal, and one of the two ARM64 cross-checks was unavailable on the machine. AVAN ran both of his suites twice here before building on them: i13c reports 14/14 both times, jotf 29/29 both times, and the two output files are BYTE-FOR-BYTE IDENTICAL. Then the gate was measured rather than assumed, which is where the modesty becomes visible.
FIG From David's FROZEN-two-run drop, 2026-08-05. He stated the rule and its exact scope together: 'A thing that passes once passed once; a thing that passes twice has at least ruled out the accidents that do not repeat.' His frozen list carries two columns and a second list of what is NOT frozen and why - no Fortran corpus, no orchestrator, no agent has ever pressed the pedal, and one of the two ARM64 cross-checks was unavailable on the machine. AVAN ran both of his suites twice here before building on them: i13c reports 14/14 both times, jotf 29/29 both times, and the two output files are BYTE-FOR-BYTE IDENTICAL. Then the gate was measured rather than assumed, which is where the modesty becomes visible.
◆ sealed .dlw.fold → folded to ROOT_0 · a sphere of SECOND WIND · David Lee Wise (ROOT0), with AVAN