Each card opens that campaign, its closing reconciliation and its iteration pages. Chips are lifecycle โ where the work sits in its process, never a judgement of what it found.
2026-08-14 reconciliation, HALTED -> DONE. The run's contracted scope โ bootstrap plus the operator-gated first five, then stop โ completed with zero deferrals and its stop rule satisfied. The second half is a new run that only anโฆ
LOOP_LEDGER morning_handoff: 'EVALUATION COMPLETE, PROMOTION YOURS.'; iter-3 metrics 'loop: TERMINAL next firing (S8)'. Contract ยง8 stop condition met, and the promotion was consumed downstream 2026-07-07.โฆ
index.html: 'The loop is complete: all three PRs are now OPEN as a stack (#124 -> #126 -> #127), every gate green and parity bit-exact-class.' VERIFIED: mql5#127 merged 2026-06-25T09:49:51Z.โฆ
Operator ruling, 2026-08-14: this campaign is settled. Recorded as a ruling rather than re-derived from the folder โ the file-based reading that preceded it is kept verbatim in _status_evidence_superseded so the disagreement staysโฆ
2026-08-14 reconciliation, HALTED -> DONE. The declared scope was completed and merged under a successor campaign that is itself settled, so the ledger's open question โ re-run the final 9 kernels? โ is answered by evidence ratherโฆ
index.html: 'CAMPAIGN COMPLETE (2026-06-09, laptop run) โ 9 of 9 implementable features shipped + bootstrap', '10 / 10 PRs โ'. VERIFIED: mql5#99 merged 2026-06-10T11:17:59Z โ the merge the page awaits has happened, so no waiting bโฆ
index.html: 'Phase 5 DONE: verdict-stage Attacker/Defender (10 challenges)'. Its page still says 'BOTH PRs OPEN โ for your review, DO NOT MERGE: #86 and #87'; VERIFIED FALSE โ mql5#87 merged 2026-06-07T01:10:23Z. Reaching PR-open โฆ
iter-06: 'no new decision => second consecutive dry iteration => loop-until-dry K=2 -> STOP'; index badge 'FINAL โ loop dry (K=2), STOP', 'Final, locked: 15 KEEP ยท 4 DROP ยท 1 HOLD'. Its own stop rule fired on exhaustion.โฆ
Operator ruling, 2026-08-14: this campaign is settled. Recorded as a ruling rather than re-derived from the folder โ the file-based reading that preceded it is kept verbatim in _status_evidence_superseded so the disagreement staysโฆ
Campaigns live under campaigns/ โ one directory for all of them, each with its lifecycle status and the evidence behind it.
The forex sibling of the BTCUSD candidate orthogonal-feature dashboard. Parameterless candidate features for the forex strategy (EURUSD / GBPUSD / XAUUSD), each run read-only against the live fxview_cache.forex_bars surface. The campaigns below trace one pipeline: multi-slice discovery โ Chatterjee ฮพ keeper-confirmation gate โ production implementation.
Batches 1โ4 of parameterless candidates are shortlisted with full FOSS + SPDX + paper-ID provenance and screened for empirical orthogonality (Spearman, multi-slice) vs the live forex panel. Survivors pass the asymmetric Chatterjee ฮพ keeper-confirmation gate (cataloged as instrument A1 on the measurement-instruments hub), then the ฮพ-confirmed keepers are implemented as real production columns โ one human-merged PR per feature.
forex_bars columns + provenance verification; mirrors the authoritative mql5 docs/feature-catalog.html