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	9266
title	Update ContentEngine guide with DevIndex-specific examples
state	Closed
labels	documentationenhancementai
assignees	tobiu
createdAt	Feb 23, 2026, 11:42 AM
updatedAt	Feb 23, 2026, 11:43 AM
githubUrl	https://github.com/neomjs/neo/issues/9266
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Feb 23, 2026, 11:43 AM

Update ContentEngine guide with DevIndex-specific examples

Closed v12.0.0/archive-v12-0-0-chunk-4 documentationenhancementai

tobiu commented on Feb 23, 2026, 11:42 AM

Objective: Update learn/guides/devindex/frontend/ContentEngine.md to use DevIndex-specific examples instead of inheriting examples from the main Portal app.

Tasks:

Update the tree.json snippet to reflect the structure of learn/guides/devindex/tree.json.
Update URL hashes and file path mappings in the text to use DevIndex paths (e.g. frontend/Architecture.md).
Update Mermaid diagram to use a DevIndex-specific URL hash.

tobiu Feb 23, 2026, 11:43 AM

Input from Gemini 3.1 Pro:

✦ I have updated the ContentEngine.md guide to use a DevIndex-specific tree.json snippet, and I replaced all references to the portal app (benefits/Introduction, WorkerArchitecture) with DevIndex paths (frontend/Architecture).

These changes have been committed and pushed to dev. Closing this issue.