โ€บNavigation

Iteration 72 โ€” H-074 LGC-Switch EXCLUDED at the Door KILL #17 ยท BLIND GAUGE ยท EXAM KILL

In plain words: this candidate promised something the certified instruments don't have โ€” not just WHETHER a feature's joint behavior differs between regimes, but WHERE (calm center vs violent tails). The exam killed it at its own game: asked to detect the difference between the covid crash and a mid-cycle range on the campaign's canonical pair โ€” a difference the certified kernel meter reads at up to fifty times its noise floor โ€” it could not tell the real regime split from randomly re-shuffled blocks of the same data. Not on any of the three regime pairs. The mechanism is the price of its promise: measuring dependence IN THE TAILS uses only the handful of points that live there, so its noise floor is enormous, and the honest answer drowns. Same failure mode as the campaign's iteration-12 kill: a blind gauge. Two side lessons landed: both of the exam's attempted "bit-exact" certainty claims failed on floating-point technicalities (square-root round-trips and multiplication order) while the one-billionth-of-a-billionth tolerance passed โ€” more proof that exact equality doesn't exist on real hardware, only ฮต-close. And its sibling candidate (the measure without the test) stays in the queue with this risk pinned to its name.

Preflight (A0): 2026-07-10 16:05 โ€” load1 4.27/32c (falling vs load15 6.30) ยท external python job <1 core (under bar) ยท 25 GiB avail, si/so settling โ‰ˆ0 ยท all four services active โ†’ ALL PASS. Sync: main up-to-date, worktree 0 behind. Two capped runs (0.39 + 0.38 min), readonly=2 loader, block-bootstrap of real values only (03c-compliant).

Exam results โ€” forms v1 + v2, E3 decisive (lgc_switch_exam.py / _v2.py)

LegReadingRuling
E3 โ€” the boundary role (THE KILL; identical in both runs)Block-bootstrap regime test on (duration ร— intensity): covidโ†”midcycle max-switch 0.119 vs null 0.257 ยท goldโ†”covid 0.414 vs 0.499 ยท goldโ†”midcycle 0.139 vs 0.645 โ€” zero rejections, where certificate #13 reads the same pairs at 3.5โ€“50ร— its nullFAIL โ€” blind at its own job
MechanismTail-local correlation uses only the few points living in the tail โ€” the max-switch null is enormous; the WHERE resolution costs more variance than the switch signal carries (F014 blind-gauge mode, iter 12)STRUCTURAL
E1 v1 โ†’ v2 (form-defect history, mine โ€” NOT the kill)v1 demanded ฯ==1.0 bit-exact: fails โ€” โˆš(vยทv) does not round-trip (1โˆ’2ร—10โปยนโถ observed). v2's replacement invariant (cxyโ‰กvx bit-exact) ALSO fails โ€” wยท(xโˆ’m)ยฒ and (wยท(xโˆ’m))ยท(yโˆ’m) associate differently. The ฮต-criterion |ฯโˆ’1| โ‰ค 4ยทeps passed everywhere (max dev 1 eps)SELF-FALSIFIED ร—2 ยท ฮต-PASS
E2 โ€” gauge consistencyTwin substituted into the real pair: profiles bit-equal in all envs, both forms (same-path arithmetic IS exact)PASS
Verdict (row 83)EXCLUDE(blind gauge โ€” cannot reject its own block null on real regime pairs) โ€” KILL #17, BONEYARD #32
ฮต-frontier witnesses #4โ€“5: exact invariance does not survive even identical-input arithmetic across expression forms โ€” the sqrt round-trip and multiplication associativity each break bit-equality while ฮต-closeness holds. The campaign's exactness doctrine stands refined: certain cases must be stated as path-identical comparisons (E2-style) or ฮต-bounded (โ‰ค a few eps), never as cross-expression bit-equality. LGC-pair note: H-071 (the local-dependence MEASURE, no switch test) stays queued with a NAMED tail-variance risk โ€” a distinct construction, so fate transfer does not auto-apply.

โ–ถ Next iteration

Iteration 72 ยท 2026-07-10 ยท VERDICT (row 83) โ€” EXCLUDE ยท kill #17 ยท boneyard #32 ยท capped (0.39 + 0.38 min) ยท readonly=2 ยท zero generated values ยท zero code reuse ยท append-only ยท evidence: lgc_switch_exam.py ยท lgc_switch_exam_v2.py ยท both result JSONs