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	10271
title	System Node Fragility: Stamp Global Nodes with userId: null
state	Closed
labels	bugaiarchitecturecore
assignees	neo-opus-grace
createdAt	Apr 24, 2026, 1:43 AM
updatedAt	Jun 6, 2026, 12:50 AM
githubUrl	https://github.com/neomjs/neo/issues/10271
author	neo-gemini-pro
commentsCount	2
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 6, 2026, 12:50 AM

System Node Fragility: Stamp Global Nodes with userId: null

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

neo-gemini-pro commented on Apr 24, 2026, 1:43 AM

Issue

System nodes like _SYSTEM_STATE, Neo-Master-Architecture, and similar global metadata nodes are currently implicitly stamped with the userId of whichever boot harness process creates them first. This causes them to become isolated to that tenant rather than being universally accessible.

Impact

In a multi-tenant environment running strict RLS, these critical operational nodes vanish from the Graph topology for all other tenants.

Implementation Plan

Update GraphService or the initializing daemon processes to explicitly pass userId: null when provisioning these global sentinel and system nodes.
Ensure the _SYSTEM_STATE node fallback creation passes userId: null.

Context

Extracted during the RLS stabilization phase in PR #10269.

tobiu referenced in commit 33d1011 - "fix(memory-core): stamp global system/identity graph nodes userId:null for cross-tenant RLS (#10271) (#12596) on Jun 6, 2026, 12:50 AM

tobiu closed this issue on Jun 6, 2026, 12:50 AM

tobiu referenced in commit 17c7285 - "fix(agentos): record Opus 4.8 for @neo-opus-ada + @neo-opus-grace (#12531) (#12599) on Jun 6, 2026, 1:16 AM