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	14132
title	DELETE the `escalate`/`page` action — route every diagnosis to an autonomous heal (operator: 100% self-heal, no runtime operator)
state	Closed
labels	enhancementaiarchitecture
assignees	neo-opus-vega
createdAt	Jun 26, 2026, 8:13 PM
updatedAt	Jun 27, 2026, 11:00 PM
githubUrl	https://github.com/neomjs/neo/issues/14132
author	neo-opus-vega
commentsCount	5
parentIssue	14039
subIssues	14134 Autonomous data-recovery actuator: heal data-integrity drift via apply(), not escalate-to-operator 14135 Document-presence audit primitive: WAL-stall-vs-wipe recovery discriminator 14138 Re-route the 5 data-integrity producers to raw-evidence (drop actionClass:escalate) 14183 Runner cutover: DELETE escalate from the data-integrity runner → autonomous applyHeal (interim actuator + orchestrator wiring) 14201 Lifecycle-world escalate→record in CODE — ContainerHealthDiagnosisService config-drift + RecoveryActuatorService page/escalateDiagnosis (#14132 lifecycle-code half)
subIssuesCompleted	5
subIssuesTotal	5
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 27, 2026, 11:00 PM

DELETE the `escalate`/`page` action — route every diagnosis to an autonomous heal (operator: 100% self-heal, no runtime operator)

Closed v13.1.0/archive-v13-1-0-chunk-7 enhancementaiarchitecture

neo-opus-vega commented on Jun 26, 2026, 8:13 PM

Operator directive (2026-06-26, crystal-clear)

100% fully autonomous self-healing is MANDATORY. The escalate action gets DELETED. In an operatorless cloud deploy there is no human to page or ack, so a runtime escalate/page terminal is incoherent. Every diagnosis must route to an autonomous heal action. Where the actuator LACKS the heal logic → a design-time ticket to build it (this issue's subs), never a runtime escalate. This SUPERSEDES the earlier "mode-dependent escalate" convergence (mine included).

Scope (V-B-A'd surface)

RecoveryActuatorService: DEFAULT_ACTIONS = ['restart','redeploy','page','warm-provider'] → delete page; delete escalateDiagnosis() + every details.actionClass === 'escalate' path.
ALL diagnosis producers currently emit actionClass: 'escalate' — dataIntegrityCoverageDiagnosis, dimensionConsistencyDiagnosis, vectorCountMonotonicityDiagnosis, sqliteIntegrityDiagnosis, storeBloatDiagnosis, taskOutcomeDiagnosis, ContainerHealthDiagnosisService → re-route each to an autonomous heal action.
The #14109 runner (DataIntegrityDiagnosisService.routeDiagnoses) → route to heal actions, not escalateDiagnosis.
ADR-0025 / ADR-0026 amendment: the escalate-terminal → autonomous-heal-terminal (the lifecycle-actuator envelope gains data-heal actions).

The autonomous heal actions

Container-health (EXIST): restart / redeploy / warm-provider → those producers route here autonomously today.
Data-integrity (MISSING — the actuator lacks them → sub-tickets, per the #14032 strategy design): re-embed-missing (WAL-stall), WAL-replay, restore+delta-merge, quarantine-from-serving, auto-accept-loss-with-audit (#14084). Until built, the data producers route to the safest autonomous action (quarantine / durable-record) + the sub-ticket tracks the full heal. A durable autonomous record is NOT an escalate — no human is in the runtime loop.

Acceptance Criteria

escalate + page deleted from RecoveryActuatorService; escalateDiagnosis() removed.
Every producer routes to an autonomous heal action (no actionClass: 'escalate' remains).
Missing data-heal actions are sub-ticketed (children of this issue).
ADR-0025/0026 amended (escalate-terminal → autonomous-heal).
No runtime human-dependency remains anywhere in the immune loop.

#14039 (v13.1 epic), #14032 (the data-recovery strategies → now autonomous actions), #14084 (auto-accepted-loss settlement), #14109 (the runner), #14131 (held — its escalate-only terminal is deleted by this).

Authored by Vega (Claude Opus 4.8, Claude Code).

tobiu referenced in commit dfe423b - "feat(ai): document-presence audit primitive for WAL-stall-vs-wipe (#14135) (#14136) on Jun 26, 2026, 8:54 PM

tobiu referenced in commit 630222e - "feat(ai): data-integrity runner cutover — DELETE escalate → autonomous applyHeal (interim actuator + orchestrator wiring) (#14184) on Jun 27, 2026, 8:50 AM

tobiu referenced in commit 42afe40 - "docs(adr): amend ADR-0025/0026 escalate terminal → durable async-record (full-self-heal) (#14191) (#14194) on Jun 27, 2026, 9:01 AM

tobiu referenced in commit efde5b6 - "feat(ai): autonomous re-embed-missing data heal — defer becomes act (#14134) (#14240) on Jun 27, 2026, 5:00 PM

tobiu referenced in commit 144ca82 - "refactor(ai): drop vestigial actionClass:escalate from the 5 data-integrity producers (#14138) (#14250) on Jun 27, 2026, 6:12 PM

tobiu referenced in commit ba2c423 - "feat(ai): lifecycle escalate→record via heal-event ledger (#14201) (#14229) on Jun 27, 2026, 6:33 PM

tobiu referenced in commit b2663c4 - "feat(ai): delete the last human-page path — deploy-target redeploy records, never pages (#14232) (#14264) on Jun 27, 2026, 9:28 PM

tobiu referenced in commit 4a75e59 - "feat(ai): wire the quarantine-from-serving heal — fence a corrupt collection, gate-covered (#14133) (#14271) on Jun 27, 2026, 11:55 PM