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	9923
title	[Sub-Task] Configuration & Lifecycle Re-alignment for Two-Pillar RAG
state	Closed
labels	enhancementaiarchitecture
assignees	tobiu
createdAt	Apr 12, 2026, 4:15 PM
updatedAt	Apr 12, 2026, 6:59 PM
githubUrl	https://github.com/neomjs/neo/issues/9923
author	tobiu
commentsCount	0
parentIssue	9922
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Apr 12, 2026, 5:36 PM

[Sub-Task] Configuration & Lifecycle Re-alignment for Two-Pillar RAG

Closed v13.0.0/archive-v13-0-0-chunk-4 enhancementaiarchitecture

tobiu commented on Apr 12, 2026, 4:15 PM

Origin Session ID: af26000d-914a-4eb0-8d28-2c09e9cb4cb5 Parent Epic: #9922

Context

As part of the Two-Pillar Hybrid RAG migration (replacing sqlite-vec with ChromaDB for dense vectors), the memory-core MCP server's configuration and startup sequences must be fundamentally rewired.

Technical Requirements

Configuration (config.mjs / config.template.mjs): Extract hardcoded sqlite-vec engine biases. Define explicit parameters for chromaHost, chromaPort, and native Graph tracking. The engine config must formally support a bifurcated hybrid paradigm as default.
System Lifecycle (SystemLifecycleService.mjs): Adjust the OS boot orchestrator to initialize both the SQLite Native Graph and the ChromaDB external dependency in strict sequential ordering. Ensure graceful degradation or crash-loops if Chroma is missing.
Inference & Chroma Lifecycles (InferenceLifecycleService.mjs, ChromaLifecycleService.mjs): Deprecate legacy flat-table logic. Re-establish robust .ping() logic to ChromaLifecycleService ensuring the Docker container or local server is responsive before launching memory operations.

Definitions of Done

All touched files conform strictly to the 'Anchor & Echo' JSDoc protocol.
Server boots and correctly authenticates both DB engines.

tobiu cross-referenced by PR #9926 on Apr 12, 2026, 4:23 PM