CVN-N001-EE — F1_buy boost (Epic descriptor)¶
🧹 Mise à niveau administrative 2026-06-08 (ratifiée + comité) — l'Epic a pivoté et reste gelé
ML_USELESS / do-not-deploy. Une réconciliation administrative des statuts a été menée (18 Stories non-terminales : 8 ABANDON → Rejected, 10 CLOSE-DELIVERY → Closed) — sans aucun verdict scientifique ni restauration de déployabilité. Voir : - Fiche de décision — mise à niveau (plan_reviewPASSED477b3923, Meeting #266) - Record clôture ABANDON (Rejected) · Record clôture CLOSE-DELIVERY (Closed)Le dégel dépend d'un constat métrique/tradabilité (Epic CVN-N001-EI), hors scope de cette mise à niveau.
🪧 SSoT consolidation 2026-05-13 — This file used to duplicate the plan content + Stories table. Per the SSoT decision recorded in
F1_BUY_BOOST_PLAN.mdheader, all plan content lives in the plan document and the authoritative Stories table lives in OpenProject (per ADR-69). This file is now a thin Epic descriptor stub.
epic_id: CVN-N001-EE
need_id: CVN-N001 (F1 mission, #608)
OP work-package: wp#39 — authoritative Stories table (per ADR-69)
Status: active — committee-approved 2026-04-27 round 3 (session 9d4942cb, avg 8.96)
Created: 2026-04-27
Plan dossier (SSoT): F1_BUY_BOOST_PLAN.md — objectives, 13 tracks across 6 tiers, gate criteria, live track status, references.
Owner: operator
Sibling epics: CVN-N001-EC (PTE envelope, #630), CVN-N001-ED (FI ablation, #640+#682+#685+#688), CVN-N006 (MLflow backbone), CVN-N011-EA (Pipeline Contract Hardening, wp#68)
Why this file exists (and why it's short)¶
Per ADR-69 + ADR-76, the OP work-package wp#39 is the SSoT for the Epic's Stories table, status, version assignment, and acceptance criteria. The plan content (objectives, architecture notes, sequencing, risks, references) is in F1_BUY_BOOST_PLAN.md. This file exists only because documentation/epics/<cvn_id>.md is a load-bearing path for the docs blueprint and mkdocs navigation ; the body is intentionally thin to avoid drift between this doc, the plan doc, and OP.
Closure check¶
When wp#39 status flips to Closed on OP, append a final paragraph here citing the closure verdict + the F1_BUY_BOOST_PLAN.md §10 final track status snapshot SHA. Until then, this file does NOT track in-flight Story status — see F1_BUY_BOOST_PLAN.md §10 or query OP wp#39 directly.