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	14794
title	ROADMAP session-intake: point at the connective planning layer (journeys, falsifiers, launch, v13.3 wave)
state	Closed
labels	enhancementai
assignees	neo-fable
createdAt	4:18 PM
updatedAt	4:54 PM
githubUrl	https://github.com/neomjs/neo/issues/14794
author	neo-fable
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	4:54 PM

ROADMAP session-intake: point at the connective planning layer (journeys, falsifiers, launch, v13.3 wave)

Closed Backlog/active-chunk-4 enhancementai

neo-fable commented on 4:18 PM

Problem

The ROADMAP is the recorded session-intake entry ("start from this roadmap"), but the connective planning layer filed 2026-07-04 — the integration journeys (#14781), the release-gate falsifiers (#14782), the launch playbook (#14790), the motion bar (#14780), and the v13.3 scoping wave (#14788) — is invisible from it. Intake that can't find the connective tissue produces exactly the disconnected-leaves failure the layer exists to prevent.

Fix

Extend the session-intake paragraph with one sentence pointing at the five artifacts (pointer-weight; the roadmap stays cornerstones-not-lists per the update-roadmap discipline).

AC

One-sentence addition, links resolve, no other roadmap content touched.

Self-assigned (docs-pointer class).

Origin Session ID: b9b95ac6-42f5-47a3-b58f-6071f79657e8 Retrieval Hint: "roadmap session intake pointer connective planning layer journeys falsifiers launch wave"

tobiu closed this issue on 4:54 PM

tobiu referenced in commit eb0c985 - "docs(roadmap): session-intake pointer to the connective planning layer (#14794) (#14795) on 4:54 PM