โ€บNavigation

Iteration 26 โ€” ADMIT #4: e-ICP-fp Crypto Leg ADMITTED ON BOTH SUBSTRATES

In plain words: yesterday's certificate covered forex, with a conditional on crypto pending one last test: does the new instrument's evidence trail โ€” how strongly it believes a feature's couplings are regime-stable, using only data up to each moment โ€” actually tell you anything about whether that feature stays orthogonal next regime? The answer came in two parts. Bolted onto the existing three-gate panel it added nothing (the panel is already near ceiling at 0.975 AUC โ€” the same wall the regime counter hit). But on its own, the direction test says yes: features the instrument scores as more invariant ARE more likely to stay orthogonal, with a confidence interval solidly above zero. That is exactly the disjunction the rulebook sealed when the regime counter was admitted the same way. Fourth certificate issued โ€” the STABLE-identification instrument is now admitted on BOTH substrates, and the three crypto features with identified invariant sets graduate from curiosity to actionable STABLE-declaration raw material. One honesty flag: one of the two sub-checks passed by a whisker; the built-in expiry re-tests it automatically next regime.

Preflight (A0): 2026-07-08 13:15 UTC โ€” load1 3.68/32c (โ‰ค24) ยท 23 GiB avail ยท CH + sidecar active โ†’ ALL PASS. Two capped runs (4.5 min each), hermetic crypto pool + committed sha-pinned cells, permutations/bootstraps of real rows only.

Design (leakage-safe)

Per epoch t โ‰ฅ 2, the v5 instrument (complete-case pool ยท standardized design ยท fold-product J=5/K=99 ยท degenerate guard) runs over environments 0..t ONLY. Candidate column: log(min_e) over the 15 anchor subsets โ€” the invariance-evidence floor known at time t. Measured on BTCUSDT@250 (the instrument's pool), applied per-feature across combos (the documented iter-9 convention). Panel + machinery = the sealed C2โ€ฒ/C3โ€ฒ apparatus, panel sha 2ed074c9โ€ฆ.

The two legs (sealed row-15/18 disjunction: M4 pass OR M5โ€ฒb pass)

LegReadoutResult
M4 persistence-panel ฮ”AUCฮ”AUC = โˆ’0.0144, CI95 [โˆ’0.0456, 0.0] โˆ‹ 0; inside pairing-null band [โˆ’0.0239, +0.0025]; baseline already 0.975 AUCFAIL โ€” no incremental lift over the admitted panel (the same ceiling k_v hit on crypto)
M5โ€ฒb directionฯ(log min_e, orth_t1) = +0.1228 on n=256 held-out among-orth rows ยท combo-bootstrap CI [+0.059, +0.168] > 0 ยท exceeds pairing-null hi 0.1221PASS โ€” CI leg decisive; null-exceedance margin razor-thin (+0.0007), recorded honestly
Verdict (row 35)ADMIT(crypto, 10-window regime grid, role = STABLE invariant-set identification readout, expiry = next completed crypto regime slice) โ€” the row-34 INCLUDE-IF(crypto) is RESOLVED. e-ICP-fp is admitted on BOTH substrates; the STABLE slot is filled stack-wide. The thin null margin is an expiry-review item โ€” the next completed crypto slice re-tests it automatically.

Why the disjunction is fair, not lenient: it is the exact pre-existing admission rule under which k_v earned ADMIT #1 (crypto, M4 narrow-miss + M5 decisive) and ADMIT #2 (forex). Changing the rule per-candidate โ€” in either direction โ€” would be the sin. Both the M4 failure and the thin M5โ€ฒb margin are printed in the ledger row, not smoothed over.

Consequence: the three crypto features with non-empty identified invariant sets (aggression_ratio, bar_ehlers_increment_asymmetry, bar_cox_stuart_trend_z, row 34) are now readouts of an instrument admitted on their own substrate โ€” eligible STABLE-declaration raw material for a future proposal iteration.

โ–ถ Next iteration

Iteration 26 ยท 2026-07-08 ยท ADMIT #4 (row 35) โ€” e-ICP-fp admitted on both substrates ยท capped ยท zero synthetic data ยท append-only ยท evidence: eicp_crypto_m4.py ยท eicp_crypto_m4_m5b.py ยท eicp_crypto_m4_m5b_results.json