Frontmatter
| id | 9748 |
| title | Update ROADMAP.md to reflect v12.2 target (#9999 + #10030 + multi-body grid) |
| state | Closed |
| labels | documentationaiagent-role:pm |
| assignees | tobiu |
| createdAt | Apr 6, 2026, 11:03 PM |
| updatedAt | Apr 20, 2026, 1:49 PM |
| githubUrl | https://github.com/neomjs/neo/issues/9748 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Apr 20, 2026, 1:49 PM |
Update ROADMAP.md to reflect v12.2 target (#9999 + #10030 + multi-body grid)
Input from Claude Opus 4.7 (Claude Code):
❋ ## Scope alignment for this session's pickup
Claiming this ticket with narrowed scope: ROADMAP.md only (VISION.md deferred — richer rewrite pending a separate session per @tobiu, since VISION is significantly more complex).
v12.2 target
The ROADMAP update will reframe current focus around three concrete release goals:
- #9999 — Cloud-Native Knowledge & Multi-Tenant Memory Core. Currently 2/5 sub-epics closed (#10013 DreamService Decomposition, #10057 KB PR source). Active: sub-epic #10015 (Dynamic Topology) — #10001 landed 2026-04-20 via PR #10121 introducing the
chromaUnifiedflag; #10007 (lifecycle bypass), #10000 (hardened identity ingestion), #10010 (team-vs-private read flag) queued next. Sub-epic #10016 (multi-tenant identity) also in scope but likely cross-session.- #10030 — Concept Ontology & Semantic Gap Inference. Currently 9/14 sub-issues closed. Open: #10037 (Chroma concept embedding + hybrid search), #10034 (concept graph viz app), #10050 (description enrichment — blocked on architect time), plus enhancement sub-tickets (#10080, #10081, #10106).
- Multi-body grid epic completion. Existing work stream; specific epic ID to be surfaced during the ROADMAP draft.
Enabler worth surfacing in the ROADMAP
Embedding transition: KB currently ships with
gemini-embedding-001in the release zip; local runs supportqwen3-8bviaNEO_GLOBAL_EMBEDDINGconfiguration. Shifting the release-zip default to qwen3-8b (4k vs 3k vector dims) aligns with the local-inference-first direction already established and tracks naturally with the multi-tenant cloud deployment story. Worth calling out as a v12.2 enabler even if not scoped as a release-blocker.What success looks like
ROADMAP.md reads as a concrete release planner rather than high-abstraction horizon phases. A future agent or human picking it up should be able to answer "what's v12.2 shipping?" in one scan. Phases 3/4/5 from the current doc can stay as horizon framing, but the top of the doc should lead with v12.2 goals and their sub-issue trees so A2A handoffs land context-complete.
Pipeline context
Sits between PR #10121 (merged 2026-04-20, landed #10001) and the next unified-topology PR for #10007. Updating the roadmap mid-sub-epic gives future sessions an anchor — without it, agents picking up #10007 would have to reconstruct the v12.2 framing from scattered ticket bodies.
Ticket adjustments in this claim
- Title narrowed: dropped "and VISION.md for Immediate Autonomous Development Epics"; specific v12.2 target surfaced
- Label
epicremoved: single-PR documentation update, not an umbrella for sub-issues- Labels kept:
documentation,ai,agent-role:pm- Assigned to @me (tobiu) for this session's execution
Origin Session ID: 1c001810-be28-4554-bb56-c98f9b91bbfb
The current versions of
ROADMAP.mdandVISION.mdreflect outdated generic goals or theoretical long-term phases instead of actionable release priorities. As we are wrapping up the baseline for autonomous development (self-healing/self-evolving systems), the roadmap must jump straight to the technical epics in scope for the upcoming releases.Objectives:
ROADMAP.mdstrictly to the next releases and in-scope autonomous development epics.Note: Document updates deferred to a clean session to avoid context window overload.