v1.1 — AI Platform Maturity & Production Readiness — Index
Document ID: RM-AIM-INDEX
File Path: docs/18-roadmap/v1.1/index.md
Version: 1.3.0
Status: Complete (2026-07-19) — all three phases done: Phase 1
(WFL-104 lease fencing deferred within its ticket), Phase 2, and Phase 3
(every ticket across WS-C/E/F/G/H/J/K/L; exit criteria met — see the
Phase 3 doc’s closing notes for the
deliberate leftovers)
Owner: Product / AI Engineering
Last Updated: 2026-07-19
1. Purpose
Section titled “1. Purpose”This folder holds the implementation tickets for PRD-004 (AI Platform Maturity), the milestone after the v1.0 GA hardening (PRD-003, shipped). Where v1.0 made the appliance safe and honest, v1.1 makes it a capable, operable, extensible AI product.
The tickets derive from a 2026-07-09 five-front engineering audit (AI core, workflow+server, dashboard UI, tools/plugins/sandbox, DX/CI/deployment/docs) — ~90 findings, mapped in PRD-004 §12.
Ticket format matches the v1.0 phase docs (RM-GA-P2 is the reference): problem with file:line evidence, the change, acceptance criteria, files, dependencies, size (S ≈ ≤2 days, M ≈ 3–5 days, L ≈ 1–2 weeks).
2. Phase Register
Section titled “2. Phase Register”| Phase | Doc | Theme | Tickets |
|---|---|---|---|
| 1 | RM-AIM-P1 | Make production claims true (P0/P1) | AIC-101..103, PRV-101, SBX-101/102, SRV-101..104, WFL-101..104, SEC-101, DX-101..103, UI-101/102 |
| 2 | RM-AIM-P2 | Credible AI product (P1/P2) | AIC-201/202, PRV-201..205, RAG-201..205, EVL-201..203, SRV-201..203, SAF-201/202, RUN-201/202, OBS-201 |
| 3 | RM-AIM-P3 | Ecosystem & scale (P2/P3) | ECO-301..305, SBX-301..304, WFL-301..308, SRV-302..307, SEC-301/302, RAG-301, UI-301..306, DX-301..306, DEP-301/302, OBS-301/302 |
3. Sequencing
Section titled “3. Sequencing”- Phase 1 first, and within it
PRV-101(cost table) first of all — it silently disables quota enforcement across the whole platform, so every cost/quota number is fiction until it lands. - Phase 1 is dominated by “wire the good primitive onto the path” fixes (sandbox activation, execution driver hardening, release reconciliation) — low-risk, high-credibility.
- Phase 2 depends on Phase 1’s cost/context work (eval and quotas need real cost; RAG reranking benefits from the provider work). Phase 3 is the broad, parallel ecosystem/DX/UI tail.
4. Scale-Out fold-in
Section titled “4. Scale-Out fold-in”PRD-003 earmarked a “v1.1 Scale-Out” (distributed Path B). Its single-node- correctness subset (Postgres pooling/TLS/fencing, distributed rate limiting) is committed here as Phase 1/2 P0/P1 tickets; the full multi-replica shared-catalog promotion (PRD-003 R-5.1/R-5.2) remains gated on Product demand and is tracked, not committed, pending that decision. See PRD-004 §7.
5. Related
Section titled “5. Related”- PRD-004 — the requirements PRD
- v1.0 GA hardening — the milestone this builds on
18-roadmap/index.md— the roadmap top-level
6. Revision History
Section titled “6. Revision History”| Version | Date | Description |
|---|---|---|
| 1.3.0 | 2026-07-19 | v1.1 milestone complete: Phase 3 finished (ECO-305, SEC-302, RAG-301 were the last three tickets; all seven Phase-3 exit criteria met) — status header → Complete |
| 1.0.0 | 2026-07-09 | Initial v1.1 milestone index: three phase ticket docs derived from PRD-004 / the 2026-07-09 engineering audit |
| 1.2.0 | 2026-07-15 | Status refresh to match the Phase 3 ticket doc: 22 of 39 P3 tickets done (ecosystem, workflow-scale, sandbox, server tracks + DEP-301); UI/DX/OBS tracks, ECO-303/305, DEP-302 remain |
| 1.1.0 | 2026-07-14 | Status refresh: Phase 1 complete (WFL-104 lease fencing deferred within its ticket), Phase 2 complete (SAF-202 was the last ticket); Phase 3 remains planned |