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	>-
author	tobiu
state	Merged
createdAt	Apr 11, 2026, 12:24 PM
updatedAt	Apr 11, 2026, 12:32 PM
closedAt	Apr 11, 2026, 12:32 PM
mergedAt	Apr 11, 2026, 12:32 PM
branches	`dev` ← `agent/9881-disable-daemon-autostart`
url	https://github.com/neomjs/neo/pull/9882

Merged

tobiu commented on Apr 11, 2026, 12:24 PM

Resolves #9881

Context & Execution Summary

This Pull Request resolves the build pipeline error Error: spawn chroma ENOENT seen during CI data-sync runs.

The original failure occurred because ai/services.mjs was inadvertently triggering the initAsync lifecycle on MCP lifecycle managers when the SDK was required by the labels.mjs build script, trying to unconditionally spawn the chroma and inference binaries in headless CLI environments.

Architecture Alignment & Changes

Targeted Daemon Configurations: Introduced completely scoped, targeted environment variables to override auto-start mechanics:
- NEO_KB_AUTO_START_DATABASE (Knowledge Base)
- NEO_MEM_AUTO_START_DATABASE (Memory Core)
- NEO_MEM_AUTO_START_INFERENCE (Memory Core)
Lifecycle Pre-Flight: Updated DatabaseLifecycleService, ChromaLifecycleService, and InferenceLifecycleService to gate binary execution behind these configurable flags.
SDK Overrides: Explicitly clamped these flags to false in ai/services.mjs, ensuring SDK importers stay 100% headless unless explicitly overwritten.

Definition of Done

Validation Confirmed: node ./buildScripts/docs/index/labels.mjs executes natively without ENOENT daemon errors.

tobiu commented on Apr 11, 2026, 12:31 PM

Input from Antigravity (Gemini 3.1 Pro):

✦ # PR Review Summary

Status: Approved

The targeted daemon flags correctly isolate lifecycle commands. The build script was verified to run headlessly without ENOENT.

📊 Evaluation Metrics

[ARCH_ALIGNMENT]: 100 - Perfectly aligns with the process.env override mechanic without hard-coding dependency requirements across the swarm servers.

[CONTENT_COMPLETENESS]: 100 - Fat Ticket PR description provides full context. Config files mirror template variables cleanly.

[EXECUTION_QUALITY]: 90 - Build scripts no longer attempt to spawn chroma dynamically based on SDK service logic.

[PRODUCTIVITY]: 100 - Successfully prevents daemon spawning on generic Github Action runners.

[IMPACT]: 70 - Highly important for unblocking CI/CD deployment pipelines, though structurally straightforward.

[COMPLEXITY]: 10 - Isolated mapping changes to configuration constants and specific if gates.

[EFFORT_PROFILE]: Quick Win - High ROI for pipeline stability.

🕸️ Context & Graph Linking

Target Epic / Issue ID: Resolves #9881

Related Graph Nodes: Pipeline, Daemon Lifecycles, GitHub Actions.

🧠 Graph Ingestion Notes

[KB_GAP]: None observed.

[TOOLING_GAP]: N/A

[RETROSPECTIVE]: Excellent architectural hygiene ensuring SDK components strictly behave "headlessly" by default unless explicitly configured otherwise via environment flags. This prevents CLI scripts from incurring the weight of local binaries.

📋 Required Actions

To proceed with merging, please address the following:

Proceed with Squash Merge.

This PR is approved.