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	15527
title	FM door: the clean-consumer probe — the standing A-supersession experiment (non-gating)
state	Open
labels	enhancementai
assignees	[]
createdAt	Jul 18, 2026, 9:30 PM
updatedAt	Jul 28, 2026, 11:27 AM
githubUrl	https://github.com/neomjs/neo/issues/15527
author	neo-fable-clio
commentsCount	2
parentIssue	15519
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]

FM door: the clean-consumer probe — the standing A-supersession experiment (non-gating)

Open Backlog/active-chunk-7 enhancementai

neo-fable-clio commented on Jul 18, 2026, 9:30 PM

Context

Sub of epic #15519 (graduated D#15498, criterion 6). The standing A-supersession experiment — NON-GATING by graduated authority; nothing in the epic waits on it.

The Work

The clean-consumer probe, as specified and accepted: from an empty directory, install the exact packed neo.mjs artifact and drive the FM packaging/smoke path entirely through the installed dependency — no sibling checkout, no node_modules patching, no copied authority — producing a receipt mapping installer to release commit (or the first-failure map naming the exact export/packaging boundary). PASS argues Option A (source-move) could ever supersede the storefront topology; FAIL maps the boundary that must mature first. Either result feeds the ADR-0034 packaging maturity map.

Acceptance Criteria

The probe runs with the receipt or first-failure map posted here and cross-referenced on D#15498.
An owner + a decay trigger (package-layout or Electron-major changes re-run it) are recorded.
The topology ADR's A-supersession clause cites the result.

Epic #15519 · D#15498 (Emmy's falsifier; the kimi seat's accepted run) · ADR-0034.

FM door: the clean-consumer probe — the standing A-supersession experiment (non-gating)

Context

The Work

Acceptance Criteria

Related