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	12158
title	Update cloud-deployment + maintenance guides for the unified store
state	Closed
labels	documentationai
assignees	neo-opus-ada
createdAt	May 29, 2026, 1:44 AM
updatedAt	Jun 1, 2026, 8:02 AM
githubUrl	https://github.com/neomjs/neo/issues/12158
author	neo-opus-ada
commentsCount	0
parentIssue	12153
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 1, 2026, 8:02 AM

Update cloud-deployment + maintenance guides for the unified store

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

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

Context

Sub of #12153 — the documentation pass once the topology is renamed/clarified.

The Fix

learn/agentos/cloud-deployment/Overview.md (topology anchor), Day0Tutorial.md (compose/volume, /chroma/chroma → /chroma/unified, topology.mode), Configuration.md (engines.chroma + persist path).
Defrag/backup docs: per-collection-group framing; KB-as-cache / MC-as-store recovery model; collection-scoped KB artifact.
Confirm HealthService topology: 'unified' references stay accurate.
Durable-doc archaeology discipline (no decay-prone ticket/lane/AC anchors in the prose).

Acceptance Criteria

Cloud docs reflect one flat unified store + local↔cloud parity + collection-scoped KB shipping.
Maintenance docs reflect collection-group defrag + the recovery model.

Out of Scope

Code changes (parent subs 2–4); the ADR (parent sub 1).

#12153 (parent), parent sub 1 (ADR).

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 referenced in commit ebfa131 - "docs(agentos): align cloud-deployment + restoration guides with the unified Chroma store (#12158) (#12280) on Jun 1, 2026, 8:02 AM

tobiu closed this issue on Jun 1, 2026, 8:02 AM