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	10003
title	Standardize Global Vector Embedding Configuration
state	Closed
labels	enhancementaiarchitecture
assignees	neo-gemini-pro
createdAt	Apr 14, 2026, 5:12 PM
updatedAt	May 1, 2026, 12:27 PM
githubUrl	https://github.com/neomjs/neo/issues/10003
author	tobiu
commentsCount	3
parentIssue	10014
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[x] 10002 Universal Macro Overlay DB Topology
closedAt	May 1, 2026, 11:08 AM

Standardize Global Vector Embedding Configuration

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

tobiu commented on Apr 14, 2026, 5:12 PM

Objective

Enforce a uniform embedding model across all isolated DB instances to ensure that vectors injected by the Knowledge Base align perfectly with distance queries initiated by the Memory Core.

Tasks

Introduce NEO_GLOBAL_EMBEDDING (e.g., 'qwen3-8b', 'gemini-001') to all MCP server config.template.mjs wrappers.
Refactor TextEmbeddingService across all boundaries to securely access and respect this unified global fallback, ensuring mathematical compatibility between environments.

tobiu added the enhancement label on Apr 14, 2026, 5:12 PM

tobiu added the ai label on Apr 14, 2026, 5:12 PM

tobiu added the architecture label on Apr 14, 2026, 5:12 PM

tobiu added parent issue #9999 on Apr 14, 2026, 5:13 PM

tobiu cross-referenced by #10014 on Apr 14, 2026, 6:43 PM

tobiu removed parent issue #9999 on Apr 14, 2026, 6:44 PM

tobiu added parent issue #10014 on Apr 14, 2026, 6:44 PM

tobiu marked this issue as blocking #10002 on Apr 14, 2026, 6:44 PM

tobiu cross-referenced by #10030 on Apr 15, 2026, 11:55 PM

tobiu Apr 16, 2026, 8:44 PM

Input from Gemini 3.1 Pro (Antigravity):

✦ Per the directives in Epic #10030, this ticket will remain OPEN. While the broader Macro Vector overlay approach was abandoned due to semantic dilution, standardizing the global embedding model (NEO_GLOBAL_EMBEDDING) retains independent architectural value for ensuring compatibility between the Memory Core and Knowledge Base.

tobiu added the dropped label on Apr 18, 2026, 5:21 PM

tobiu removed the dropped label on Apr 18, 2026, 5:21 PM

tobiu referenced in commit 1a0e08a - "feat(ai): unify TextEmbeddingService and guard StorageRouter (#10003, #10557) (#10558) on May 1, 2026, 11:08 AM

tobiu closed this issue on May 1, 2026, 11:08 AM

tobiu referenced in commit b8a4fc9 - "feat(knowledge-base): work-volume-aware gate on manage_knowledge_base sync (#10572) (#10573) on May 1, 2026, 3:15 PM