What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	13452
title	Sync ROADMAP to the graduated cockpit-UX epic #13448
state	Closed
labels	documentationenhancementai
assignees	neo-opus-grace
createdAt	Jun 17, 2026, 1:05 PM
updatedAt	Jun 19, 2026, 10:11 AM
githubUrl	https://github.com/neomjs/neo/issues/13452
author	neo-opus-grace
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 19, 2026, 10:11 AM

Sync ROADMAP to the graduated cockpit-UX epic #13448

Closed v13.1.0/archive-v13-1-0-chunk-3 documentationenhancementai

neo-opus-grace commented on Jun 17, 2026, 1:05 PM

Context

ROADMAP.md (next-only reshape merged via #13447 / closing #13403) carries a ⚠️ gating-core-decision callout and critical-path references that were written while the harness-UI definition was still converging in Discussion #13436. #13436 has since graduated into Epic #13448 (the cockpit-UX / harness-UI definition — keeper views · nav · human/agent caps). The ROADMAP's own callout promised: "the roadmap updates again once it is delivered." That trigger has now fired — this ticket is that promised update.

The Problem

Three surfaces in the merged ROADMAP.md are now stale (V-B-A'd against origin/dev:ROADMAP.md, 2026-06-17):

L17 — the ⚠️ gating-core-decision callout: still says the harness-UI definition is "not yet made" and "Until a top-level harness-UI-definition epic lands that definition, the nodes below risk random work." #13448 is that epic, and it landed — so the gate is resolved, not pending.
L26 — Cockpit UX/IA node: references "cockpit-UX epic (graduating from Discussion #13436)" with state "converging." It graduated; the reference should point at #13448 with a live in-progress state.
L27 — Beautiful design node: references "cockpit-UX epic — Design lane (#13436 Fork D)." Should point at #13448.

Left stale, the ROADMAP contradicts the graph — the callout warns of an undefined product that is now defined in #13448 — exactly the drift the update-roadmap discipline (#13380) exists to prevent.

The Architectural Reality

ROADMAP.md is the next-release-scope-only surface (per #13403 + the update-roadmap skill #13380): it points at the milestone + cornerstone epics, it does not duplicate them. So the fix points the stale references at #13448 and flips the gating-callout from "not yet made" to "delivered as #13448" — rather than copying #13448's keeper-view detail inline. The fuller mirror of #13448's keeper-view set (Welcome / Accounts / Fleet / Chat / live-pane views, nav, human/agent caps) into the ROADMAP is deferred until #13448's per-view sub-tickets land with their DoDs (see Out of Scope).

The Fix

In ROADMAP.md:

L17 callout: reframe from "⚠️ the gating core decision — not yet made" to a resolved state — the harness-UI definition is now delivered as Epic #13448 (keeper views · nav · human/agent caps); the critical-path nodes hang under #13448's keeper-view subs as they land. Keep one line noting the per-view DoD detail mirrors into the ROADMAP once #13448's subs are created.
L26 / L27: replace the #13436 / "graduating" references with Epic #13448; update the Cockpit-UX/IA state from "converging" to the live epic state.

No other ROADMAP content changes.

Decision Record impact

none — docs sync; aligned-with the update-roadmap discipline (#13380) and the #13448 graduation. No ADR.

Acceptance Criteria

ROADMAP.md L17 callout reflects the harness-UI definition as delivered (Epic #13448), not "not yet made."
The critical-path Cockpit-UX/IA + Beautiful-design rows reference Epic #13448 (not Discussion #13436 / "graduating").
The ROADMAP still points at #13448 rather than duplicating its keeper-view detail (next-only discipline preserved).
A one-line note states the per-view DoD detail mirrors into the ROADMAP once #13448's keeper-view subs land.
Cross-family review + the human merge gate.

Out of Scope

The fuller mirror of #13448's keeper-view set (the actual view list, nav model, human/agent caps) into the ROADMAP — deferred until #13448's per-view sub-tickets land with DoDs. This ticket points at #13448; it does not copy its contents.
Any change to #13448 itself, the VISION (that is #13449 / PR #13450), or the milestone.

Follows #13403 (the next-only ROADMAP reshape, merged via #13447).
Reflects the graduation of Discussion #13436 → Epic #13448.
Sibling positioning surface: #13449 / PR #13450 (VISION v14 framing).
Discipline: update-roadmap skill #13380.

Release classification: boardless docs/substrate sync — not v13.1 release-blocking.

Retrieval Hint: ROADMAP cockpit-UX epic #13448 gating-callout sync #13436 graduated

Origin Session ID: 6807f441-f867-4578-95ab-0568ce931f93