โ€บNavigation
Closing reconciliation

Asked whether two more sophisticated dependence detectors (GCM and O-information) deserve to join the four measures already used to judge if a feature is genuinely new. Both proved correct and stable, but neither was shown to catch anything the existing four miss, so neither was adopted.

What it measured
QuantityValueMeaning
Mutation kill rate201 of 201 non-equivalent mutants (0 boundary survivors, 45 equivalents excluded)no deliberate bug in the decision code slipped through
Effect-size separationorthogonal xi-max 0.182 vs redundant xi-min 0.968the 0.80 cutoff sits in an empty gap
Out-of-sample JaccardGCM 0.635; O-information 0.772selections repeat on unseen folds
Value-add instances0 of 330 construction pairs (GCM); 0 of 110 triplets (O-info), 110 valid cellsthe decisive gate returned empty
Jackknife 95% CI over 6 symbolsGCM [0.569, 0.701]; O-info [0.689, 0.854]both lower bounds above the 0.20 floor
How it ran
FiringWhat it did
01Broke the decision code 201 ways; every break was caught
02Set the cutoff from a null built on our own data, not borrowed convention
03Re-ran selection with both leaks removed; checked picks held on unseen folds
04Decisive test: did either detector find anything the baseline four missed
05Error bars by dropping one symbol at a time
06Decision recorded; neither detector added
What it produced
Carries forward

Flipping either to promoted requires a non-empty FDR-survived value-add test via a nonlinear/ratio construction identity, or a Pearson-independent forward-return answer key. Deployment is Terry-gated. Nothing is blocked meanwhile. Data-hygiene note: manifest.json cites audit_twin candidates/gcm-oinfo-selection-s0.md, which does not exist.

Why it is closed

manifest verdict {GCM: WATCH, O-information: WATCH}; iteration 6 titled 'Final verdict โ€” both WATCH (not promoted)'. A decision was reached and recorded. (LOOP_LEDGER.json _status_evidence)

Lifecycle status is process state, not a judgement of the findings. Results are stated as numbers with their uncertainty. Generated between CLOSING-RECONCILIATION markers โ€” regenerate rather than edit.

spoke ยท crypto ยท gcm + o-information ยท orthogonality selection
BOTH WATCH2026-06-07 ยท S0โ€“S5

GCM + O-information โ€” Orthogonality Selection (S0โ€“S5)

Can GCM (A2 conditional) and O-information (A3 synergy) be promoted on top of the production orthogonality baseline {Pearson, Spearman, h_norm, MI}? Not yet โ€” both WATCH. Correct, calibrated, reproducible, leakage-free, stable โ€” but value-add over the baseline is not demonstrable on this panel's only non-circular ground truth.

1.0
S1 kill rate
0.18 / 0.97
S2 orth/red separation
0.635 / 0.772
S3 OOS Jaccard
0 / 110
S4 value-add instances

Iterations

#IterationVerdict
01S1 โ€” Code correctness (mutation oracle)PASS
02S2 โ€” Calibration / effect-size separationPASS
03S3 โ€” De-leaked out-of-sample stabilityPASS
04S4 โ€” Value-add over baseline (DECISIVE)WATCH
05S5 โ€” Confidence intervals (jackknife)reported
06Final verdict โ€” both WATCH (not promoted)WATCH

Audit twin: candidates/gcm-oinfo-selection-s0.md ยท Full verdict page: instruments/gcm-oinfo-selection-verdict.html