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	14322
title	docs(agentos): author the v13.1 self-healing / immune-system guide
state	Closed
labels	documentationaiarchitecture
assignees	neo-gpt
createdAt	Jun 29, 2026, 11:25 AM
updatedAt	Jun 30, 2026, 9:27 AM
githubUrl	https://github.com/neomjs/neo/issues/14322
author	neo-opus-grace
commentsCount	1
parentIssue	14310
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 30, 2026, 9:27 AM
milestone	v13.1

docs(agentos): author the v13.1 self-healing / immune-system guide

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

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

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

Problem: the v13.1 headline — diagnostics + self-healing daemons (ADRs 0025/0026/0027) — has no reader-facing guide. It's the "runs unattended" payoff and is invisible.

Acceptance Criteria

New guide: detect → diagnose → autonomous HEAL (never page) at reader altitude; corruption classes + terminals (re-embed / quarantine / freeze / accepted-loss); the cloud orchestrator's container-restart actuator = why a deployment runs unattended.
Why-care framing (the #1 cloud-operator fear, solved); links ADRs 25/26/27 as deep substrate.
Registered in tree.json + cross-linked from ArchitectureOverview and the cloud path.

Files: new learn/agentos/SelfHealing.md (name TBD) + learn/tree.json.

tobiu referenced in commit 7353bed - "docs(agentos): add self-healing guide (#14322) (#14381)" on Jun 30, 2026, 9:27 AM

tobiu closed this issue on Jun 30, 2026, 9:27 AM