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	13883
title	[recovery-daemon] Rung-2 via B0 — supervised-process restart (privilege-free)
state	Closed
labels	enhancementai
assignees	neo-gpt
createdAt	Jun 22, 2026, 11:58 PM
updatedAt	3:21 PM
githubUrl	https://github.com/neomjs/neo/issues/13883
author	neo-opus-grace
commentsCount	1
parentIssue	13874
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[x] 13882 [recovery-daemon] Detect + restart a stuck (resident-but-not-serving) Ollama runner — privilege-free
blocking	[]
closedAt	Jun 23, 2026, 10:34 AM

[recovery-daemon] Rung-2 via B0 — supervised-process restart (privilege-free)

Closed v13.1.0/archive-v13-1-0-chunk-5 enhancementai

neo-opus-grace commented on Jun 22, 2026, 11:58 PM

Parent: Epic #13874. Graduated from Discussion #13871 (Axis B → B0).

Problem / scope

A large share of "crash/hang" faults are orchestrator-supervised processes (the local model server, embeddings server, vector store) that ProcessSupervisorService already restarts past a cooldown — zero new privilege. B0 makes the recovery daemon ACT on the crash — supervised process class without the docker socket, shrinking the privileged surface to the external-container case only.

Acceptance Criteria

Rung-2 via B0: restart an orchestrator-supervised process via ProcessSupervisorService.superviseTask + RESTART_COOLDOWN_MS (the crash — supervised process cell).
Escalates to Rung-3 (redeploy/page) if it restart-loops past N (anti-thrash, persisted).
Covers the restart half of the exhaustion cell (Rung-0 shed + Rung-2 restart).
Selects B0 (vs external) deterministically from targetIdentity.kind === 'supervised-task' (the C4 contract) — no inference.
Observability + verify-loop inherited from the daemon-core sub.
Zero new privilege (AC-7 composition).

Contract Ledger

Adds: the B0 actuator binding + the crash — supervised process / exhaustion policy cells.
Reuses: ProcessSupervisorService.superviseTask, RESTART_COOLDOWN_MS.

Sequencing

Blocked-by the daemon-core sub (daemon + dispatch). Privilege-free. Fire-relief priority — covers a supervised local-model-server crash.