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	14315
title	docs(benefits): ArchitectureOverview.md — name the main areas (cloud vs local) + local↔cloud spine + unified-Chroma + inventory freshness
state	Closed
labels	documentationaiarchitecture
assignees	neo-gpt
createdAt	Jun 29, 2026, 11:24 AM
updatedAt	Jul 2, 2026, 9:41 AM
githubUrl	https://github.com/neomjs/neo/issues/14315
author	neo-opus-grace
commentsCount	2
parentIssue	14310
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jul 2, 2026, 9:41 AM
milestone	v13.1

docs(benefits): ArchitectureOverview.md — name the main areas (cloud vs local) + local↔cloud spine + unified-Chroma + inventory freshness

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

neo-opus-grace commented on Jun 29, 2026, 11:24 AM

Part of #14310 · follow the content rubric pinned on #14310. Refs #14310.

Problem: ArchitectureOverview.md has no LOCAL-vs-CLOUD distinction, draws two ChromaDBs (we run one unified), lists "Five MCP Servers" + Gemini-only embeddings (stale), and never maps the main areas a reader should explore.

Acceptance Criteria

Opens by naming the main areas (Body · Brain · Neural Link · cloud-vs-local Agent OS) as a map readers navigate from.
Adds the LOCAL-vs-CLOUD Brain section (two topologies of one organism) + the local-vs-remote model note.
Persistence diagram = ONE unified Chroma (logical KB+MC collections); MCP-server table + structural inventory current (5+ servers incl. self-healing daemons; local/remote providers).

Files: learn/benefits/ArchitectureOverview.md.

tobiu referenced in commit b09e154 - "docs(benefits): refresh architecture overview map (#14315) (#14395)" on Jul 2, 2026, 9:41 AM

tobiu closed this issue on Jul 2, 2026, 9:41 AM