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	7553
title	Refactor HealthService to Match Superior Memory Core Pattern
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Oct 19, 2025, 11:54 PM
updatedAt	Oct 20, 2025, 12:07 AM
githubUrl	https://github.com/neomjs/neo/issues/7553
author	tobiu
commentsCount	0
parentIssue	7536
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Oct 20, 2025, 12:07 AM

Refactor HealthService to Match Superior Memory Core Pattern

Closed v11.0.0/archive-v11-0-0-chunk-3 enhancementai

tobiu commented on Oct 19, 2025, 11:54 PM

This ticket covers refactoring ai/mcp/server/knowledge-base/services/healthService.mjs into a singleton HealthService class. The current implementation is a simple function; it should be upgraded to match the more robust and informative pattern established in the memory-core server's HealthService (ai/mcp/server/memory-core/services/HealthService.mjs).

Acceptance Criteria

The file ai/mcp/server/knowledge-base/services/healthService.mjs is renamed to HealthService.mjs.
The content is replaced with a HealthService class that extends Neo.core.Base and is configured as a singleton.
The healthcheck function is converted into a class method (e.g., buildHealthResponse).
The new class uses the DatabaseLifecycleService and ChromaManager to get the database status, instead of creating its own Chroma client.
The health check response is enhanced to include more details, such as uptime and version, mirroring the memory-core service.
The ai/mcp/server/knowledge-base/services/toolService.mjs is updated to use the new HealthService class and its method.
The healthcheck tool continues to function correctly with the improved response structure.