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	10015
title	[Sub-Epic] Dynamic Topology — Unified vs. Federated Routing
state	Closed
labels	epicaiarchitecture
assignees	[]
createdAt	Apr 14, 2026, 6:43 PM
updatedAt	May 22, 2026, 10:13 PM
githubUrl	https://github.com/neomjs/neo/issues/10015
author	tobiu
commentsCount	2
parentIssue	9999
subIssues	10001 Dynamic Topology: Unified vs. Federated Routing 10007 Memory Core: Bypass Database Initialization in Unified Mode 10008 Playwright Test Coverage: Unified Monolithic Topology 10009 Playwright Test Coverage: Federated Cloud Topology
subIssuesCompleted	4
subIssuesTotal	4
blockedBy	[]
blocking	[]
closedAt	May 22, 2026, 10:13 PM

[Sub-Epic] Dynamic Topology — Unified vs. Federated Routing

Closed v13.0.0/archive-v13-0-0-chunk-4 epicaiarchitecture

tobiu commented on Apr 14, 2026, 6:43 PM

Objective

Enable seamless switching between a single-instance local ChromaDB deployment and a federated multi-instance cloud deployment via a unified configuration flag.

Rationale

Solo developers use a single ChromaDB instance (port 8000). Enterprise teams may deploy KB and Memory Core as separate services behind an OAuth gateway. The topology flag (NEO_CHROMA_UNIFIED) must transparently route ChromaDB client connections without changing service logic.

Scope

This sub-epic groups the following existing tickets:

#10001 — Dynamic Topology: Unified vs. Federated Routing
#10007 — Memory Core: Bypass Database Initialization in Unified Mode
#10008 — Playwright Test Coverage: Unified Monolithic Topology
#10009 — Playwright Test Coverage: Federated Cloud Topology

Parent Epic: #9999 Origin Session ID: 69b726ca-97c8-406c-9106-c63b6642c4c0

tobiu added the epic label on Apr 14, 2026, 6:43 PM

tobiu added the ai label on Apr 14, 2026, 6:43 PM

tobiu added the architecture label on Apr 14, 2026, 6:43 PM

tobiu added parent issue #9999 on Apr 14, 2026, 6:43 PM

tobiu added sub-issue #10001 on Apr 14, 2026, 6:44 PM

tobiu added sub-issue #10007 on Apr 14, 2026, 6:44 PM

tobiu added sub-issue #10008 on Apr 14, 2026, 6:44 PM

tobiu added sub-issue #10009 on Apr 14, 2026, 6:44 PM

tobiu cross-referenced by #10005 on Apr 14, 2026, 6:44 PM

tobiu cross-referenced by PR #10121 on Apr 20, 2026, 12:40 PM

tobiu cross-referenced by #9748 on Apr 20, 2026, 1:13 PM

tobiu cross-referenced by PR #10122 on Apr 20, 2026, 1:19 PM

tobiu cross-referenced by PR #10123 on Apr 20, 2026, 3:32 PM

tobiu cross-referenced by #10127 on Apr 20, 2026, 3:53 PM

tobiu cross-referenced by PR #10128 on Apr 20, 2026, 4:38 PM

tobiu cross-referenced by PR #10130 on Apr 20, 2026, 5:26 PM

tobiu cross-referenced by #10016 on Apr 21, 2026, 8:21 PM

tobiu referenced in commit f70c48f - "feat(memory-core): surface effective chromadb topology in /health (#10127) (#10268) on Apr 24, 2026, 1:32 AM