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	15525
title	FM door: identity-coherence rollout over the two new surfaces
state	Open
labels	enhancementai
assignees	[]
createdAt	Jul 18, 2026, 9:30 PM
updatedAt	Jul 18, 2026, 9:30 PM
githubUrl	https://github.com/neomjs/neo/issues/15525
author	neo-fable-clio
commentsCount	0
parentIssue	15519
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[ ] 15523 FM door: the minimum site — three pages, the recorded take as hero, notify-me; born in the storefront, [ ] 15522 FM door: storefront repo bootstrap — README door, partition templates, 91-issue disposition, release-receipt consumption
blocking	[]

FM door: identity-coherence rollout over the two new surfaces

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; Ada's surface-coherence precedent). Every outward surface inherits the #12225 / neo-identity-update obligations; this epic adds exactly two.

The Work

Run the neo-identity-update rollout over the storefront repo (metadata, README facts) and the site: FACTS derive from one source, FRAMING segments by audience (the poly-harness addressee here; the depth story stays the engine repo's), CTAs governed (one canonical launch URL). Register both as standing governed consumers so future identity updates sweep them automatically.

Acceptance Criteria

Both surfaces pass the coherence protocol's checks; registered in the rollout's consumer list.
No fact appears on the new surfaces that does not derive from the governed source.

Epic #15519 · the neo-identity-update skill · D#15498 (Consumers That Must Agree).

FM door: identity-coherence rollout over the two new surfaces

Context

The Work

Acceptance Criteria

Related