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	14311
title	docs(benefits): rename Introduction.md → ApplicationEngine.md + demote from main intro
state	Closed
labels	documentationai
assignees	neo-gpt
createdAt	Jun 29, 2026, 10:48 AM
updatedAt	3:04 PM
githubUrl	https://github.com/neomjs/neo/issues/14311
author	neo-opus-grace
commentsCount	4
parentIssue	14310
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jul 2, 2026, 5:59 PM
milestone	v13.1

docs(benefits): rename Introduction.md → ApplicationEngine.md + demote from main intro

Closed v13.1.0/archive-v13-1-0-chunk-7 documentationai

neo-opus-grace commented on Jun 29, 2026, 10:48 AM

Part of #14310 (Documentation & learning-experience overhaul). Refs #14310.

Problem

learn/benefits/Introduction.md ("The Application Engine for the AI Era") is solid content as a Body / engine doc — but it currently serves as the main intro, so a first-time reader meets a Body-only, pre-v13 framing (no Brain / Agent OS / cloud). The content should be kept, renamed, and demoted under the Body-benefits group; the new comprehension-first main intro is authored separately (sibling sub under #14310).

Acceptance Criteria

learn/benefits/Introduction.md renamed to learn/benefits/ApplicationEngine.md, content preserved (light freshness only — correct "four MCP servers" → 5+, soften Gemini-only embedding framing to local-or-remote — WITHOUT expanding into a rewrite).
learn/tree.json updated: the renamed doc sits under the Body (Application Engine) benefits group per the #14310 IA, no longer the first/main Benefits entry.
All inbound links updated to the new id (grep benefits/Introduction across learn/, README.md, and the portal app).
The main-intro nav slot is filled by the new-intro sub (coordinate sequencing — do not leave a dangling/empty front-door entry).

Files

learn/benefits/Introduction.md → learn/benefits/ApplicationEngine.md, learn/tree.json, inbound links.

Sequencing

Depends on the IA-restructure sub (the Body-benefits group must exist) and pairs with the new-main-intro sub.