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: DreamService RAG Migration (#9931)
author	tobiu
state	Merged
createdAt	Apr 12, 2026, 6:54 PM
updatedAt	Apr 12, 2026, 7:02 PM
closedAt	Apr 12, 2026, 7:02 PM
mergedAt	Apr 12, 2026, 7:02 PM
branches	`dev` ← `agent/9931-dream-service-rag-migration`
url	https://github.com/neomjs/neo/pull/9932

Merged

tobiu commented on Apr 12, 2026, 6:54 PM

Resolves #9931\n\n### Summary\n- Fixed DreamService graph node iteration to correctly evaluate .label instead of .type due to formal graph theory semantic mappings in Neo's internal persistence layer (where Nodes have labels, Edges have types).\n- Added explicit documentation detailing this label/type distinction.\n- Refactored DreamService.spec.mjs Playwright test mocks and fixed global teardown fs callback exceptions, ensuring 100% test pass rate.

tobiu commented on Apr 12, 2026, 6:59 PM

Input from Antigravity (Gemini 3.1 Pro):

✦ # PR Review Summary

Status: Approved

Excellent investigative work validating the internal topological boundaries and aligning Native Edge Graph models with formal graph database semantics. The initial context collapse (hallucinating that Neo.data.Model intrinsically banned the type property) was correctly diagnosed and surgically remedied.

📊 Evaluation Metrics

[ARCH_ALIGNMENT]: 100 - Perfect alignment. Restoring .label vs .type based on canonical Graph semantics (Nodes=labels, Edges=types) ensures robust, predictable mappings for downstream GraphRAG services.

[CONTENT_COMPLETENESS]: 100 - The "Anchor & Echo" protocol was strictly applied across NodeModel.mjs, DreamService.mjs, and GraphService.mjs, permanently overwriting the prior framework assumptions securely.

[EXECUTION_QUALITY]: 100 - The code successfully solves native graph array traversal regressions. Crucially, global mock teardown operations in Playwright were appropriately sequestered to prevent test bleed.

[PRODUCTIVITY]: 100 - Successfully concludes the stabilization goals laid out for the DreamService architecture.

[IMPACT]: 80 - High-impact fix directly protecting the core logic loop of the background Memory Core daemon.

[COMPLEXITY]: 50 - Highly focused architectural string-mapping revisions paired with tricky test suite environment management.

[EFFORT_PROFILE]: Maintenance - Essential foundational remediation resolving topological regressions.

🕸️ Context & Graph Linking

Target Epic / Issue ID: Resolves #9931

Related Graph Nodes: CLASS:Neo.ai.graph.NodeModel, CLASS:Neo.ai.mcp.server.memory-core.services.DreamService

🧠 Graph Ingestion Notes

[KB_GAP]: The agent originally conflated the type mapping as a restriction of the Neo.data.Model configuration framework (which it is not) rather than its true origin: strict Graph Database taxonomy enforcement. Documentation now reflects this.

[RETROSPECTIVE]: The encapsulation of external JSON API schema boundaries versus internal persistence mechanics (SQLite/Model) must be strictly respected. Iterating over persistence arrays (nodes.items) necessitates leveraging the internal structural schema (n.label), irrespective of the public DTO shape (node.type).

📋 Required Actions

To proceed with merging, please address the following:

Approved for Squash Merge. No further modifications requested.

Solid closure to an extended stabilization campaign. It is safe to merge this directly into dev.