0%

s23 — Promotion Gates + Teardown Readiness

Goal

Per-target promotion is a recorded, evidence-backed decision: the ledger (conformance + speed + quality + verification) is complete per target, flag-default flips are user-gated decision records, and the LLVM-teardown-readiness checklist exists as the handoff to a FUTURE teardown plan — this plan ends at promotion-eligible, not teardown.

Implementation Sketch

  • Per-target promotion criteria (all must hold): s16 conformance green on target; s17 fast-tier speed standing recorded (beat-Cranelift status); s20 quality ledger >= 1.0 vs LLVM -O3 on the corpus reachable for that target; s21 three-layer verification green; soak evidence (the tri-parity CI history over a defined window).
  • Promotion decision records: one per target under this plan’s decisions set; the actual default-flip (which hat is default for build/run/test per target) is USER-gated (AskUserQuestion at execution time per target — never autopilot-flipped); two-hat remains available post-flip (LLVM still selectable).
  • Teardown-readiness checklist: enumerates everything LLVM-coupled that a teardown plan must own (llvm feature surface, inkwell dep, aot/ LLVM layers, JIT evaluator path, alive2 remnants if any survive aims-burden section-14, CI LLVM installs, docs) — the checklist is the FUTURE plan’s intake artifact; creating that plan routes through /create-plan when the user calls for it.
  • Mission close-out: missions.md gains the ori_backend per-crate mission entry (via the missions governance — additive entry citing this plan); rules sync (/sync-claude) for new crate/commands/env vars; /sync-docs pass; final /review-plan.

Test Strategy

  • The gates consume upstream artifacts; this section’s own deliverable checks: ledger completeness validator (no target promoted with a missing criterion), decision-record presence per flipped target.

Work Items

  • Per-target promotion ledger assembled (conformance/speed/quality/verification/soak columns) with completeness validator.
  • Promotion decision records per target; user-gated default-flip execution for targets the user approves (two-hat preserved).
  • LLVM-teardown-readiness checklist authored (future-plan intake artifact; teardown explicitly out of this plan).
  • Mission + docs close-out: missions.md ori_backend entry, /sync-claude, /sync-docs, final /review-plan clean.