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.

Neo.mjs - Self-Evolving Software Organism

Frontmatter

title	>-
fix	Remove early abort in Sandman pipeline to permit ambient GC and
author	tobiu
state	Merged
createdAt	Apr 12, 2026, 7:09 PM
updatedAt	Apr 12, 2026, 7:11 PM
closedAt	Apr 12, 2026, 7:11 PM
mergedAt	Apr 12, 2026, 7:11 PM
branches	`dev` ← `agent/9933-sandman-early-abort-fix`
url	https://github.com/neomjs/neo/pull/9934

Merged

tobiu commented on Apr 12, 2026, 7:09 PM

Resolves #9933. Modified processUndigestedSessions() to no longer abort execution when zero undigested sessions are present, allowing the daemon to ambiently perform Garbage Collection and synthesize the Golden Path roadmap consistently.

tobiu commented on Apr 12, 2026, 7:10 PM

Input from Antigravity (Gemini 3.1 Pro):

✦ # PR Review Summary

Status: Approved

Thanks for stepping in so quickly! Excellent tactical fix to restore the ambient reliability of the background Sandman daemon. It is absolutely critical that global topological decay and garbage collection are decoupled from the frequency of new session ingestion.

📊 Evaluation Metrics

[ARCH_ALIGNMENT]: 100 - Resolves an architectural bottleneck where ambient system maintenance (Garbage Collection and Strategy Extraction) was improperly halted by a lack of new episodic memory.

[CONTENT_COMPLETENESS]: 90 - "Fat Ticket" protocol was observed, properly summarizing the two distinct workflows of the Sandman pipeline vs Memory ingestion.

[EXECUTION_QUALITY]: 100 - Clean, precise refactoring. Replaced the terminating short-circuit with a solid bifurcating if/else control flow structure. Native test suites verified stability seamlessly.

[PRODUCTIVITY]: 100 - Instantly restores the expected automated execution flow for the scheduled npm run ai:run-sandman process.

[IMPACT]: 60 - Essential bug fix to ensure consistent Native Graph telemetry and Golden Path vector realignment.

[COMPLEXITY]: 10 - Standard logic control-flow extraction.

[EFFORT_PROFILE]: Quick Win - High ROI execution to restore vital background agent logic.

🕸️ Context & Graph Linking

Target Epic / Issue ID: Resolves #9933

Related Graph Nodes: agent/9933-sandman-early-abort-fix, CLASS:Neo.ai.mcp.server.memory-core.services.DreamService

🧠 Graph Ingestion Notes

[RETROSPECTIVE]: Background autonomous daemons should structurally decouple "input-driven" processing (e.g. digesting new sessions) from "ambient-maintenance" processing (e.g. garbage collection, decay, roadmap synthesis). Short-circuits based on the absence of inputs should never cascade to halt ambient maintenance cycles.

📋 Required Actions

To proceed with merging, please address the following:

Merge PR. No further changes requested.

Clean and verified. Approved for Squash Merge.