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	12154
title	Author amending ADR: one flat unified Chroma store + parity
state	Closed
labels	documentationaiarchitecture
assignees	neo-opus-ada
createdAt	May 29, 2026, 1:43 AM
updatedAt	May 29, 2026, 3:18 AM
githubUrl	https://github.com/neomjs/neo/issues/12154
author	neo-opus-ada
commentsCount	0
parentIssue	12153
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	May 29, 2026, 3:18 AM

Author amending ADR: one flat unified Chroma store + parity

Closed v13.0.0/archive-v13-0-0-chunk-14 documentationaiarchitecture

neo-opus-ada commented on May 29, 2026, 1:43 AM

Context

Sub of #12153 — the lock-in decision record for the one-flat-unified-store topology. This is the formal authority artifact; the code subs (#12153 subs 2–5) implement against it.

The Fix

Add a new ADR at learn/agentos/decisions/00NN-*.md (next free number), e.g. "Chroma — Single Flat Unified Store + Dev/Prod Parity", Status: Accepted.
Decision content: one daemon/container; one flat store named unified (local .neo-ai-data/chroma/unified, cloud volume /chroma/unified — retiring /chroma/chroma); no per-realm folders; realm/tenant isolation by collection names + metadata; KB shipping by collection-scoped export; recovery by the KB-as-cache / MC-as-store backup model. Local conforms to the cloud reference; the federated-era two-folder layout + stale memory-core folder are retired.
Cross-reference: amends ADR 0003 (preserve its one-daemon core), touches ADR 0014 (cloud topology). Add a forward "amended by #NN" note to ADR 0003.

Decision Record impact

amends ADR 0003; touches ADR 0014. ADR successor-risk: adr-amendment-required (see parent #12153).

Acceptance Criteria

New ADR added, Accepted, amends 0003 + cross-refs 0014.
ADR 0003 carries a forward "amended by" pointer.
Durable-doc archaeology discipline honored (no decay-prone lane/cycle/AC anchors in the prose; canonical amends/supersedes # decision-record refs are fine).

Out of Scope

All code changes (parent subs 2–5).

#12153 (parent), ADR 0003, ADR 0014.

Origin Session ID: efd8dc2e-2052-4089-814a-ab22cd8c6a62

tobiu referenced in commit 7cedc3b - "docs(ai): ADR 0017 — single flat unified Chroma store + dev/prod parity (#12154) (#12159) on May 29, 2026, 3:18 AM

tobiu closed this issue on May 29, 2026, 3:18 AM