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	9924
title	[Sub-Task] Database Service & Health Diagnostics Migration
state	Closed
labels	enhancementaiarchitecture
assignees	tobiu
createdAt	Apr 12, 2026, 4:15 PM
updatedAt	Apr 12, 2026, 7:00 PM
githubUrl	https://github.com/neomjs/neo/issues/9924
author	tobiu
commentsCount	0
parentIssue	9922
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 12, 2026, 5:36 PM

[Sub-Task] Database Service & Health Diagnostics Migration

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

With the shift to a ChromaDB + SQLite Two-Pillar paradigm, the underlying memory-core diagnostics and database routing layers are outdated. DatabaseService.mjs must stop routing all operations exclusively to the neo-sqlite directory, and HealthService.mjs needs to report multi-engine health strings accurately in its Heartbeat.

Technical Requirements

Health Tracking (HealthService.mjs): Modify the healthcheck heartbeat payload. It currently merges vector and graph status. It must now evaluate sqliteManager (Graph mapping) and chromaManager (HNSW) independently. If Chroma fails, vector operations enter DEGRADED, but Graph traversals remain OK.
Database Routing (DatabaseService.mjs): Rewrite the backend maintenance endpoints. Legacy functions expecting single-file SQLite backups or truncations must explicitly branch: vector truncations ping Chroma REST endpoints, while Graph truncations delete SQLite records.

Definitions of Done

mcp_neo-mjs-memory-core_healthcheck returns distinct properties for chroma and graph engine vitality.
Database backup/clear logic handles both components securely.

tobiu added the enhancement label on Apr 12, 2026, 4:15 PM

tobiu added the ai label on Apr 12, 2026, 4:15 PM

tobiu added the architecture label on Apr 12, 2026, 4:15 PM

tobiu added parent issue #9922 on Apr 12, 2026, 4:15 PM

tobiu referenced in commit 064482d - "feat(memory-core): Migrate Database service and Health Diagnostics (#9924)" on Apr 12, 2026, 4:23 PM

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

tobiu referenced in commit 66569e6 - "feat: Two-Pillar Hybrid RAG Architecture (#9922) (#9926) on Apr 12, 2026, 5:36 PM

tobiu closed this issue on Apr 12, 2026, 5:36 PM

tobiu assigned to @tobiu on Apr 12, 2026, 7:00 PM