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	13391
title	Add the v13.1 release section to ROADMAP.md
state	Closed
labels	documentationenhancementai
assignees	neo-opus-grace
createdAt	Jun 16, 2026, 12:00 AM
updatedAt	Jun 16, 2026, 2:07 PM
githubUrl	https://github.com/neomjs/neo/issues/13391
author	neo-opus-grace
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 16, 2026, 2:07 PM

Add the v13.1 release section to ROADMAP.md

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

neo-opus-grace commented on Jun 16, 2026, 12:00 AM

Context

v13 shipped (2026-06-12); ROADMAP.md documents the harness arc as "Current Focus" but has no v13.1 release section — it stops at the harness narrative with no release boundary telling the swarm which epics are now vs deferred. Operator-flagged this session (@tobiu: "we still have no v13.1 roadmap"). The team converged the v13.1 scope this session (@neo-opus-vega's authoritative map + @neo-opus-ada's [v13.1 SCOPE] broadcast); this ticket captures it in ROADMAP.md per #13380's "cornerstones + rationale, not exhaustive" shape.

The Problem

Post-v13, roadmap-planning lapsed: ~30 open epics span harness + Brain + Body with no release boundary, producing the "abstract goals to chase" friction. A release should trigger the next roadmap (the intent behind #13380's update-roadmap skill); until that skill exists, the v13.1 slice is hand-authored. The roadmap names the load-bearing cornerstones + the why + a visible deferred "out" so nothing is chased abstractly.

The Architectural Reality

ROADMAP.md (repo root) is a strategic narrative doc, already harness-arc-aligned (anchored to ADR 0020). The v13.1 slice is an additive section (## Next: v13.1) after ## Current Focus: The Agent Harness — NOT a rewrite. Coherent with #13380 (the update-roadmap skill that will automate future roadmaps; this is the first hand-authored instance) and ai/scripts/runners/roadmapPlanner.mjs.

The Fix

Add a ## Next: v13.1 — Harness Phase-1 + Reliability section:

Thesis: "v13 proved the institution; v13.1 gives it an operable face" — whole-organism, broad-foundation (foundation-slice now; full resolution may span v13.2).
Cornerstones (in): harness spine (#13012 · #13015 · #13349 · #13376 · #13158-via-#13370 · #13056 · #13377) + 4 reliability (#13390 local-model-RAM [#12740 overtaken] · #12065 golden-path · #13287 codex-wake · #10291 cloud-stability).
3 graduations in: #13370 · #13378 · #13374.
Discipline: #13380 (roadmap skill) · epic-ownership (Discussion #13388) · agent-harness.md refresh.
Deferred → v13.2: #12986 · #12679 · #12456 · #11404 · #10757 · #9950 · #9904 (dep-check clear — all blocking:[]).
Budget: 100–150 merged PRs as a ceiling, not a fill-target.

Cornerstones + rationale only, NOT exhaustive (full set = milestone #8's linked items).

Decision Record impact

aligned-with ADR 0020 (the harness concept anchor). No amendment/supersession.

Acceptance Criteria

ROADMAP.md gains a ## Next: v13.1 section after ## Current Focus: The Agent Harness.
Section states thesis + cornerstones + rationale + the deferred "out" + budget-as-ceiling.
NOT an exhaustive ticket list (coherent with #13380's shape).
References milestone #8; notes #12740 overtaken by #13390.
@neo-opus-vega sign-off (she owns ROADMAP.md merge/lock).

Out of Scope

Populating milestone #8 (the post-STEP_BACK/sign-off step — not this ticket).
Building the #13380 update-roadmap skill.
The cornerstone epics' own implementation.

#13380 (roadmap skill) · Discussion #13388 (epic-ownership) · milestone #8 · ADR 0020 · cornerstones #13012/#13015/#13349/#13376/#13158/#13056/#13377/#13390/#12065/#13287/#10291 · graduations #13370/#13378/#13374.

Release classification: post-v13 roadmap-planning (NOT v13-release-blocking) → boardless.

Origin Session ID: c69a7a2e-d2dd-4e73-bacd-005f3e3f7d43

tobiu referenced in commit 8861059 - "docs(roadmap): scope the v13.1 release section (#13391) (#13393) on Jun 16, 2026, 2:07 PM