Roadmap Index
Document ID: RM-INDEX-001
File Path: docs/18-roadmap/index.md
Version: 1.9.0
Status: Active
Owner: Product Team
Last Updated: 2026-07-27
1. Purpose
Section titled “1. Purpose”This section describes the planned evolution of the Wovyr AI Platform — milestone releases and their themes. It complements the high-level phases in the README roadmap with per-release detail.
Current position (2026-07-19): v0.3.0 is tagged; the v1.0 GA-hardening engineering scope (PRD-003, all four phases) is complete, with the Tier-A GA-completion validation workstreams still open — see v1.0.md; v1.1 is complete (all three phases, 2026-07-19); v1.2 (Generative UI Trust Runtime) and v1.3 (MCP Connection Management) are shipped. v1.4 (Audit Remediation & Truth Reconciliation) is planned — a truth-and-hardening milestone (not features) scoped by PRD-007 from a 2026-07-23 four-lens audit. v1.5 (Design System Unification & UI Truth) is complete — all three phases, 31 tickets, 2026-07-27, incl. the first browser e2e harness in this workspace. v1.6 (Pentest Remediation) is planned — four small, independent fixes (RES-601/SBX-305/GUI-501/VAL-401) from the 2026-07-27 internal red-team assessment; everything else in that report was a verified PASS with no action item.
2. Release Themes
Section titled “2. Release Themes”| Release | Theme | Doc |
|---|---|---|
| v0.1 | Foundations: core engines runnable | v0.1.md |
| v0.2 | Memory, tools, and the gateway hardened | v0.2.md |
| v0.3 | Plugins, dashboard, and multi-tenancy | v0.3.md |
| v1.0 | Production-ready, GA, enterprise | v1.0.md |
| v1.1 | AI Platform Maturity: capable, operable, extensible (post-GA) | v1.1/index.md |
| v1.2 | Generative UI Trust Runtime — the product milestone: frame protocol, trust/policy engine, durable interaction loop, renderer SDK, internal-tools beachhead | v1.2-generative-ui.md |
| v1.3 | MCP Connection Management — a persisted, UI-managed layer over the shipped MCP client: connection store, agent-manifest wiring, dashboard panel | v1.3-mcp-connections.md |
| v1.4 | Audit Remediation & Truth Reconciliation — a truth-and-hardening milestone: day-one security fixes (SSRF, cross-tenant authz, audit MAC, KMS fail-closed), AI-core correctness (Anthropic embeddings, bounded caches, default retrieval), CI/claim honesty, and a sustainability scope freeze | v1.4-audit-remediation.md |
| v1.5 | Design System Unification & UI Truth — a unification-and-truth milestone for the three user-facing surfaces: one token source across landing/docs/dashboard/renderer, WCAG AA remediation with a CI gate, dashboard identity truth, and the first browser e2e harness. Complete (all 3 phases) | v1.5-design-system-unification.md |
| v1.6 | Pentest Remediation — four small fixes from the 2026-07-27 internal red-team assessment: a for_each fan-out cost/token ceiling, an explicit opt-in for privileged --local tools, schema-constrained UI-frame generation, and documenting the agent manifest’s unknown-field tolerance | v1.6-pentest-remediation.md |
| Future | Beyond 1.0 — research bets | future.md |
v1.1 (AI Platform Maturity) is scoped by PRD-004 from a 2026-07-09 five-front engineering audit — real cost accounting, context/token management, activated sandboxing, native Anthropic, a real RAG middle, an evaluation gate, MCP/plugin-SDK ecosystem work, and UI/DX/operability maturity. Three phased ticket docs: P1 · P2 · P3.
v1.2 (Generative UI Trust Runtime) executes the strategic repositioning of ADR-0011, scoped by PRD-005: the platform becomes the engine; the product is the runtime that lets AI agents render interactive interfaces to humans safely, auditable, and with durable human-in-the-loop decisions. v1.1 Phase 3 is re-scoped through PRD-005 — ecosystem items that serve the trust runtime fold into v1.2 P3; purely horizontal items defer to future.md.
v1.3 (MCP Connection Management) executes
ADR-0012, scoped by
PRD-006: a persisted, dashboard-managed
layer over the already-shipped, programmatic-only MCP client (v1.1 P3’s
ECO-301) — a connection store, agent-manifest wiring, and a dashboard panel, with
Stdio-transport connections gated exactly like the shell tool and
Http-transport connections reusing the existing SSRF guard. Deliberately
narrower than future.md’s exploratory outbound MCP-gateway/
federation bet (FUT-005) — this milestone is inbound-only.
v1.4 (Audit Remediation & Truth Reconciliation) is scoped by
PRD-007 from a 2026-07-23 four-lens
audit (QA, AI engineering, security, codebase-health/strategy) that read the
code against the claims in README.md/CLAUDE.md/DISTRIBUTION.md. It is a
truth-and-hardening milestone, not features: fix the concrete
day-one findings (redirect-SSRF, cross-tenant org authz, unkeyed audit chain,
unsandboxed native tool path, KMS ephemeral-fallback data loss, Anthropic-only
memory breakage, unbounded caches), make “proven” mean “proven in CI,” reconcile
the version and the claims with reality, and draw a sustainability line around
the ~20-subsystem surface. Tickets: v1.4-audit-remediation.md
(RM-AR-P1..P3).
v1.5 (Design System Unification & UI Truth) is scoped by a 2026-07-26 UI/UX
audit of the three shipped user-facing surfaces — the marketing landing page, the
Starlight docs site, and the operator dashboard (plus the @wovyr/ui-react
renderer it embeds), all measured live rather than read from source. Like v1.4 it
is remediation, not features: the landing page’s own
DESIGN-system.md claims /, the docs,
and the dashboard “read as one product,” and they measurably do not — four
independent token systems, three theme-persistence keys, two brand marks, eight
colour pairs below WCAG AA, a dashboard that cannot build from a clean checkout,
and a console that displays an acting principal it is not acting as. The
milestone unifies the tokens, gates contrast in CI (the previous pass was
deferred to human review and missed eight pairs), and adds the browser e2e
harness whose absence is why several shipped UI claims are still qualified
“manually spot-checked, not CI-gated.” Tickets:
v1.5-design-system-unification.md
(RM-DSU-P1..P3). No PRD — the findings are the requirements; requirement IDs are
defined in that document’s §3.
v1.6 (Pentest Remediation) — complete (2026-07-28) — is scoped by an
internal red-team / abuse-resistance assessment (2026-07-27), an authorized
engagement against the platform’s own CLI/workflow execution, tool sandbox,
multi-agent orchestration, UI-frame protocol, secrets/KMS/audit, and server auth
floor. Verdict: STRONG (541 security-invariant tests passed, 0 Critical and
0 High findings). Only 4 of the 20 dynamic cases needed follow-up — everything
else was a verified PASS with no action item — and all four are now fixed,
each with regression tests in the ordinary cargo test --workspace. Like
v1.4/v1.5, no PRD: the findings are the requirements. Tickets:
v1.6-pentest-remediation.md (RES-601, SBX-305,
GUI-501, VAL-401). Reproduction detail is held internally rather than published
here; that document’s §4 carries the operator-facing guidance.
3. Principles
Section titled “3. Principles”- Vertical slices — each release runs end to end, not just lower layers.
- Docs-then-build — specs (this repo) precede implementation.
- Security & multi-tenancy early — not bolted on later.
- Dogfood — the platform builds/operates itself where possible.
4. How This Maps to the Docs
Section titled “4. How This Maps to the Docs”Each release advances the subsystems documented in sections 03–16. The SUMMARY tracks which docs exist; the roadmap tracks which implementations land when.
5. Status & Disclaimer
Section titled “5. Status & Disclaimer”The roadmap is directional, not a commitment; dates and scope adjust with learning. ADRs (section 17) record decisions that reshape it.
6. Revision History
Section titled “6. Revision History”| Version | Date | Description |
|---|---|---|
| 1.8.0 | 2026-07-27 | v1.5 Phase 2 (one product — token unification + CI-gated a11y + first browser e2e harness) marked done — all 11 tickets shipped and verified; Phase 3 remains planned |
| 1.7.0 | 2026-07-26 | v1.5 Phase 1 (ship blockers) marked done — all 9 tickets shipped and verified same-day; Phases 2/3 remain planned |
| 1.6.0 | 2026-07-26 | Added v1.5 (Design System Unification & UI Truth, RM-DSU-001) — 31 tickets across three phases remediating the 2026-07-26 UI/UX audit of the landing page, docs site, and dashboard; requirement IDs defined in-document (no PRD, since the findings are the requirements) |
| 1.5.0 | 2026-07-23 | Added v1.4 (Audit Remediation & Truth Reconciliation, PRD-007/RM-AR-001) — a truth-and-hardening milestone from the 2026-07-23 four-lens audit; not a feature release |
| 1.4.0 | 2026-07-19 | v1.1 marked complete (Phase 3 finished — ECO-305/SEC-302/RAG-301 were the last tickets) |
| 1.3.0 | 2026-07-15 | Status-truth pass: replaced the stale “Planning / Documentation phase (v0.1.0)” claim with the real current position — v0.3.0 tagged, PRD-003 engineering scope complete, v1.1 P3 partial, v1.2/v1.3 shipped |
| 1.2.0 | 2026-07-15 | Added v1.3 (MCP Connection Management, PRD-006/ADR-0012) — a scoped, committed milestone narrower than FUT-005’s exploratory outbound MCP-gateway bet |
| 1.1.0 | 2026-07-14 | Added v1.2 (Generative UI Trust Runtime, PRD-005/ADR-0011); noted the v1.1-P3 re-scope |
| 1.0.0 | 2026-06-27 | Initial Roadmap index |