Community roadmap
What’s available. What’s stabilising. What comes next.
This roadmap describes Community capabilities, not commercial edition packaging. Community Alpha targets October 2026. Dates are milestones, not promises per feature; community initiatives are tracked separately from runtime capabilities.
| Status | Area | What it covers |
|---|---|---|
| Available | CLI foundations | Doctor, inspection, declarative validation, model and application read paths, incremental planning. |
| Stabilising | Community packaging | One-step Community download, tutorial starters and versioned compatibility guidance. |
| Stabilising | VS Code parity | Bringing validated tooling capabilities into a consistent source-first editor experience. |
| Stabilising | Client-project guidance | Community licence, deployment targets and exit path, published with the Alpha. Current answers |
| Planned | Mission starters | Client portal, operations back-office, field interventions and bookings, in the order Founding Freelancers choose. |
| Exploring | Domain packages | Letting community members publish reusable domain packages, and later distribute them. |
| Available | Agent Runtime | cell agent, goals, persistent sessions, confirmation flows and runtime-backed action execution. |
| Available | Governed MCP | MCP discovery and calls through catalog, policy and confirmation boundaries. |
| Available | MCP as native AST operationalization | Semantic Actions can retain their business identity while MCP is used as an execution backend through native AST. |
| Available | Knowledge Runtime | KnowledgeQuery, ContextAssembly, BindingSet, EvidenceSet, provenance and governed context assembly for agents. |
| Available | Scoped shared knowledge | Personal, team, project and organization knowledge with explicit scope and governed promotion. |
Community initiatives are separate from capability status. Early access, Founding Freelancers and future persona programmes are participation tracks, not runtime maturity levels.
Early access