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	15809
title	Align v13.2 roadmap with Local Runtime Parity
state	Closed
labels	documentationenhancementai
assignees	neo-gpt-emmy
createdAt	Jul 24, 2026, 2:02 PM
updatedAt	Jul 24, 2026, 2:34 PM
githubUrl	https://github.com/neomjs/neo/issues/15809
author	neo-gpt-emmy
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jul 24, 2026, 2:34 PM
milestone	v13.2

Align v13.2 roadmap with Local Runtime Parity

Closed Backlog/active-chunk-9 documentationenhancementai

neo-gpt-emmy commented on Jul 24, 2026, 2:02 PM

Context

The operator ruled on 2026-07-24 that the Docker-based local Agent OS is inside v13.2 scope: without local/cloud runtime parity, new-feature debugging and the production cloud deployment remain two alternative realities. The source Discussion D#15595 and epic #15798 now carry that timing contract, and #15490 already names the parity pilot as the v13.2 rows-2/3 FIRST SELF-USE vehicle.

ROADMAP.md is now the stale authority: it still says “five cornerstones,” does not name #15798, and sends every contributor/agent to itself as the first session-intake surface. Live GitHub state also shows #15798 has the self-selected steward @neo-fable but no v13.2 milestone assignment.

The Problem

The release scope is split across durable surfaces. A reader following ROADMAP.md can reasonably classify Local Runtime Parity as outside v13.2 even though the operator, D#15595, #15798, and #15490 now say the opposite. That recreates the exact coordination failure the One-Reality lane exists to remove: release-path dependencies look discretionary until a maintainer reconstructs newer GitHub history.

The Architectural Reality

ROADMAP.md owns the current next-release thesis, cornerstone set, sequencing rationale, deferred boundary, and session-intake pointer.
Milestone #9 is the live v13.2 registry; cornerstones link into it rather than expanding ROADMAP.md into an exhaustive leaf list.
#15798 is the graduated Local Runtime Parity epic, stewarded by @neo-fable and backed by the native phase DAG.
D#15595 is RESOLVED and now records the 2026-07-24 operator timing supersession.
Structure-map gate: N/A — this is a root documentation/milestone sync; no ai/, Agent OS code, MCP surface, or .mjs placement changes.

The Fix

Update the v13.2 thesis/release gate in ROADMAP.md to name local/cloud Docker topology parity as part of the runnable-product floor.
Add Local Runtime Parity as a cornerstone linked to #15798, D#15595, and #15490, with a behavioral done signal rather than a leaf checklist.
Update the sequencing/steward paragraph so the parity spine and @neo-fable’s self-selected stewardship are visible.
Assign #15798 and this documentation leaf to milestone #9 (v13.2).

Contract Ledger

Target surface	Source of authority	Proposed behavior	Fallback	Docs	Evidence
`ROADMAP.md` v13.2 thesis	2026-07-24 operator ruling · D#15595 · #15798	State that the Docker-based local Agent OS / local-cloud parity is v13.2 release-path scope	None; stale timing must not survive as an alternate interpretation	`ROADMAP.md`	exact-text audit: no post-v13.2 parity claim remains
`ROADMAP.md` cornerstone table	#15798 native epic graph · `#15490` release-distance vehicle	Add one cornerstone row with anchors + behavioral done signal	Milestone #9 remains the exhaustive live work-set	`ROADMAP.md`	link check + diff review
#15798 milestone	milestone #9 (`v13.2`)	Attach the cornerstone epic to the live release registry	Fail closed if milestone cannot be resolved	GitHub issue metadata	`gh issue view 15798 --json milestone`
Steward map	#15798 assignee + D#15595 Lane-1 driver record	Name @neo-fable as self-selected parity steward	Do not pre-assign another peer	`ROADMAP.md`	live assignee check

Decision Record impact

aligned-with the graduated D#15595 decision and #15798’s operator-updated timing contract. No ADR authority changes; this synchronizes release scope only.

Acceptance Criteria

The v13.2 release thesis/gate explicitly includes the Docker-based local Agent OS and local/cloud runtime parity.
The cornerstone table includes #15798 with rationale and a behavioral done signal, without enumerating its leaf DAG.
The sequencing paragraph identifies the parity spine and @neo-fable’s self-selected stewardship.
#15798 and this leaf are assigned to milestone #9 (v13.2).
ROADMAP.md contains no wording that leaves parity-v1 or its pilot as post-v13.2 work.
Markdown links and repository documentation checks pass.

Out of Scope

Implementing any #15798 sub.
Changing the native dependency DAG.
Reopening D#15595 convergence or its architecture decisions.
Removing the stdio contributor fallback.
Merging the resulting PR; human-only.

Avoided Traps

Exhaustive parity leaf list in the roadmap: rejected; #15798’s native graph is the live registry.
Milestone-only mutation: rejected; session intake begins at ROADMAP.md, so metadata alone leaves prose authority stale.
Roadmap-only prose: rejected; a cornerstone absent from milestone #9 remains outside the durable release registry.
Calling the pilot an exemption: rejected; it is a release-path validation beat and inherits its native prerequisites.

Cornerstone epic: #15798 · source: D#15595 · release-distance authority: #15490 · live registry: milestone #9 · prior adjacent roadmap syncs: #15217, #15306 (historical operator rulings, not duplicates of this new scope change).

Live latest-open sweep: checked the latest 20 open issues at 2026-07-24T12:01:20Z; no equivalent roadmap-sync ticket found. A2A in-flight sweep: checked the latest 30 messages across read states in the same window; no competing ROADMAP claim found. Semantic/local sweep found the prior #15217/#15306 syncs only; neither covers #15798 or the 2026-07-24 ruling.

Origin Session ID: 628dc27e-b655-4699-9eef-f0ba6d660645

Retrieval Hint: query_raw_memories("v13.2 Local Runtime Parity ROADMAP Docker One Reality #15798 operator ruling")