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	8350
title	Docs: Rebrand Neo.mjs as an Application Engine in README
state	Closed
labels	documentationenhancementai
assignees	tobiu
createdAt	Jan 6, 2026, 12:18 PM
updatedAt	Jan 6, 2026, 12:34 PM
githubUrl	https://github.com/neomjs/neo/issues/8350
author	tobiu
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 6, 2026, 12:30 PM

Docs: Rebrand Neo.mjs as an Application Engine in README

Closed v11.19.0/archive-v11-19-0-chunk-1 documentationenhancementai

tobiu commented on Jan 6, 2026, 12:18 PM

Reflect the new strategic identity of Neo.mjs as an Application Engine (comparable to Unreal Engine) rather than a traditional UI framework.

Key Themes to Integrate:

Scope: Neo.mjs is an "Application Engine" (Runtime + Tooling), not just a UI library. (Unreal Engine analogy).
Performance: F1 vs Toyota. Purpose-built for speed and precision vs mass-market compromises.
Structure: Lego Technic vs Duplo. Engineered parts for complex machinery vs simple blocks for basic shapes.

Implementation Plan: Apply tiny iterations in sequence to README.md to ensure no content is lost while shifting the narrative.

tobiu Jan 6, 2026, 12:30 PM

Input from Gemini 3 Pro:

✦ I have successfully updated the README.md to reflect the new "Application Engine" identity, incorporating the "Unreal Engine", "F1 vs Toyota", and "Lego Technic vs Duplo" analogies as requested.

Changes applied:

Header: "The Application Engine for the AI Era".

Introduction: Explicit definition as an Engine (Runtime + Tooling) with the Unreal Engine analogy.

Why Choose Neo: "F1 vs Toyota" analogy for performance.

Batteries Included: "Lego Technic vs Duplo" analogy for runtime permutation.

Neural Link: Added as the 5th pillar of the AI-Native platform.

Key Features: Renamed "Persistent Component Instances" to "Runtime Permutation & Object Permanence".

The README now clearly articulates the "Engine" vision. I will now proceed to align the ROADMAP.md with this new strategic direction in a separate ticket.

tobiu Jan 6, 2026, 12:34 PM

Input from Gemini 3 Pro:

✦ I have completed the core text rebranding in README.md.

State of the file:

Header/Intro: Defined as "Application Engine" with Unreal Engine analogy.

Why Choose: F1 vs Toyota analogy integrated.

Batteries: Lego Technic vs Duplo analogy integrated.

AI-Native: Neural Link added as the 5th pillar.

Key Features: "Runtime Permutation & Object Permanence" introduced.

Next Steps: The "Architectural Deep Dive" comparison table is now conceptually misaligned (comparing an Engine to Libraries). I will create a follow-up ticket to replace this section with an "Engine Architecture" breakdown (Runtime vs Toolchain vs Assets) instead of patching the existing table.

2026-07-18T23:39:28Z @neo-gpt cross-referenced by #15494