Roadmap & scope

Done — the core loop, end to end

The profile → hypothesize → patch → gated-verdict → ROI loop runs unattended, OS-isolated, across Rust and C, batch and service, from a pinned corpus to a dollar figure — with zero shipped false accepts across all phases, and the two pipeline over-accepts both caught by audit and turned into permanent gates.

Phase 5 — the research forks (SPEC §13)

Deliberately out of the core roadmap, these are the two hardest cases the spec named — both now built and exercised, both routed to human review. Full write-up: Research forks.

• Kernel lane — done as a CPU demonstration. A matmul optimization that reorders floating-point accumulation (transpose-B + eight-accumulator ILP) runs 3.23× faster and is impossible to gate byte-identically. It slots into the harness by swapping the equivalence policy for a declared FP-tolerance (abs + rel·|ref|) — which still catches a genuine wrong result — and routes to needs-human-review because using the tolerance tier at all is a §8 signal. This is the GPU lane in miniature: reference-kernel differential testing, interleaved timing, ledger row. Only the timer and the hardware change; the actual GPU run needs GPU hardware, absent here.
• Learned optimization policies — done. crates/policy reads the ledger and ranks optimization classes by the Wilson lower bound of their shippable-win rate, turning the fixed cheapest-first ordering into a learned prior (advisory only — the gates still decide). Prior art: MLGO, AlphaDev, Meta's LLM Compiler.

The real target

The end goal is not vendored OSS case studies — it is a real production system. The same gates that matter for a JSON parser matter far more for a live CMS: an equivalence failure there is a customer-facing bug, and the network-isolated verdict path and append-only audit trail are what would make it safe to point an optimization agent at code that a business depends on.

Known gaps (what would have to close first)

Honesty about the remaining edges, since the product is trust:

• Full-container isolation. The verdict pipeline is network-isolated on the agent path (scripts/no-net.sh); the seccomp-restricted bench container of SPEC §10 is not built, and a human running just verdict directly is unwrapped.
• Test-suite pins. The verify-or-refuse machinery exists, but no target ships a TESTSUITE.sha256 yet — so "the agent cannot edit the upstream tests" is currently a mechanism awaiting its pins.
• TSan. The lane runs on the accept path only when a target declares [build].tsan; none does today, so there is no TSan coverage. Class-7 (concurrency) work depends on that opt-in landing.
• Kernel lane wiring. matmul demonstrates FP-tolerance equivalence script-driven; it is not yet a target.toml pipeline target.