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	14166
title	Freeze → auto-unfreeze/re-heal cycle: a transient embedder fault must not permanently freeze a collection in cloud (the #1 weeks-bar risk)
state	Closed
labels	enhancementaiarchitecture
assignees	neo-opus-grace, neo-opus-vega
createdAt	Jun 27, 2026, 1:20 AM
updatedAt	Jun 28, 2026, 2:47 PM
githubUrl	https://github.com/neomjs/neo/issues/14166
author	neo-opus-vega
commentsCount	2
parentIssue	14039
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 28, 2026, 2:47 PM

Freeze → auto-unfreeze/re-heal cycle: a transient embedder fault must not permanently freeze a collection in cloud (the #1 weeks-bar risk)

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

neo-opus-vega commented on Jun 27, 2026, 1:20 AM

Problem

freeze is the autonomous safe action for a systemic / dimension-systemic fault (e.g. a misconfigured-embedder false-storm). But in cloud there is no operator to unfreeze. If freeze is terminal-until-human, a transient embedder glitch permanently kills a collection — directly defeating "runs for weeks." It is unclear the auto-reopen fingerprint (#14118 lineage) unfreezes a frozen collection (vs re-opening accepted-loss residue).

Fix shape

A re-probe → auto-unfreeze → re-heal cycle: a frozen collection is periodically re-probed; when the underlying fault clears (embedder healthy, dimensions consistent), it auto-unfreezes and re-enters the heal path.
Bounded — don't thrash freeze↔unfreeze; back-off.

Acceptance Criteria

A frozen collection is re-probed on cadence; fault clears → auto-unfreeze → re-heal.
Freeze↔unfreeze is bounded (no thrash).
A persistent fault stays frozen (contained) but recorded in the heal-ledger.

Scope

v13.1 — the highest-risk could-be-known for the weeks-bar. Parent neomjs/neo#14039; actuator-side, coordinate @neo-opus-grace (#14134).

Live latest-open sweep: scanned 25-latest + neomjs/neo#14134 / neomjs/neo#14133 / neomjs/neo#14118; freeze is defined (containment), but auto-unfreeze/re-heal is unfiled. No duplicate.

Authored by Vega (Claude Opus 4.8, Claude Code). Origin Session ID: 1bb8a27b-ae0d-4668-a9a2-acbbe2387512

tobiu referenced in commit 644643e - "feat(ai): autonomous freeze re-probe substrate — decider + store + cycle orchestrator (#14171) (#14172) on Jun 27, 2026, 2:25 AM

tobiu referenced in commit f0b9854 - "feat(ai): heal-event ledger substrate — durable store + status-summary + query (#14177) (#14178) on Jun 27, 2026, 3:13 AM