ML Boost — F1_buy 75 mission¶
🪧 SSoT consolidation 2026-05-13 — This index used to duplicate content with
documentation/F1_BUY_BOOST_PLAN.md. Per the SSoT decision recorded inF1_BUY_BOOST_PLAN.mdheader, all mission narrative + live track status + gate criteria now live in that single plan document. This index is a thin pointer kept to preserve themissions/ml-boost/directory as the location of per-Track results dossiers.
Canonical references¶
- Plan + live track status + gates :
documentation/F1_BUY_BOOST_PLAN.md - Mission summary → §0 Executive summary
- 13-track structure → §5 The 12 tracks (10 from v1 + 2 added in v2) + Track 14 in §10
- Gate criteria (6 official gates) → §6 Sequencing, gates & operational prerequisites
- Live track status table → §10 Implementation tracking
- Pipeline contract hardening (cross-cutting CVN-N011-EA) → §11.1
- Tests covering the mission → §11.2
- Epic descriptor :
documentation/epics/CVN-N001-EE-f1-buy-boost.md(also a thin stub) → OP wp#39 is the authoritative Stories table per ADR-69 - S18 freeze note : see the banner at the top of the plan +
documentation/architecture/TRAINING_PIPELINE.md§6 for the regression context
Per-Track results dossiers (this directory)¶
Each Track that completes a sweep produces a results dossier in this folder. The dossiers stay here as the canonical per-Track audit trail :
- Track 5 — Asymmetric label smoothing + cleanlab — verdict ABANDONED
- Track 6 — Focal loss — verdict ABANDONED
- Track 9 — Per-regime threshold — verdict ABANDONED
- Track 11 — Ensemble diversity — In testing
- Track 1 — BTC cross-asset features — verdict ABANDONED (leakage gate fail, GH #806 investigation)
- Track 14 — Timeframe sweep (5m / 15m / 30m / 1h) — verdict LOCK on 5m
The verdict + status fields in each dossier are the source of truth for the entries in F1_BUY_BOOST_PLAN.md §10. If they disagree, the per-Track dossier wins (operator updates the plan §10 from the dossier, not the other way).