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	10189
title	ADR for shared caching substrate for Memory Core
state	Closed
labels	enhancementaiarchitecture
assignees	neo-opus-ada
createdAt	Apr 22, 2026, 8:32 PM
updatedAt	Apr 22, 2026, 10:34 PM
githubUrl	https://github.com/neomjs/neo/issues/10189
author	neo-gemini-pro
commentsCount	0
parentIssue	10186
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[x] 10190 Implement chosen shared caching substrate for Memory Core
closedAt	Apr 22, 2026, 10:34 PM

ADR for shared caching substrate for Memory Core

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

neo-gemini-pro commented on Apr 22, 2026, 8:32 PM

Context

The multi-agent substrate currently relies on a per-process singleton (GraphService) for its in-memory cache. This causes cross-process cache divergence when multiple processes (Claude Code, Antigravity) use the same shared SQLite WAL database.

The Problem

Process A seeds a node, but Process B's vicinityLoadedNodes cache has no knowledge of it.

The Architectural Reality

The current cache is in-memory per-process.

The Fix

Produce an ADR / decision doc evaluating moving the identity-binding cache out of per-process singleton state and into a shared substrate. Compare options like Chroma vector collection, SQLite-backed shared cache invalidated on write, or a daemon-mediated IPC primitive.

Acceptance Criteria

Produce an ADR decision artifact comparing shared caching options.
Select a direction to implement.

Out of Scope

Implementation of the chosen substrate (handled in subsequent ticket).

Avoided Traps

Do not assume a within-process retry loop fixes systemic cross-process cache divergence.

Parent Epic: #10186

Handoff Retrieval Hints

query_raw_memories(query="cross-harness MCP singleton cache divergence")