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	docs: refresh v12.2 goal #1 state to reflect merged sub-tickets (#9748)
author	tobiu
state	Merged
createdAt	Apr 20, 2026, 5:26 PM
updatedAt	Apr 20, 2026, 5:42 PM
closedAt	Apr 20, 2026, 5:42 PM
mergedAt	Apr 20, 2026, 5:42 PM
branches	`dev` ← `agent/roadmap-v12-2-progress-refresh`
url	https://github.com/neomjs/neo/pull/10130

Merged

tobiu commented on Apr 20, 2026, 5:26 PM

Summary

Refreshes ROADMAP.md v12.2 goal #1 (Cloud-Native Knowledge & Multi-Tenant Memory Core) to reflect the sub-tickets that merged during 2026-04-20.

Changes

Sub-epic #10015 Dynamic Topology — checkbox flipped from [ ] to [x]. Client-side routing (#10001) and lifecycle bypass (#10007) both merged. Playwright coverage in #10008 / #10009 explicitly marked as deferred follow-up polish (not a release blocker).
Sub-epic #10016 Multi-Tenant Identity & Data Privacy — #10000 now marked merged with a one-line summary of what landed (JWT-claim identity propagation via new RequestContextService singleton, per-tenant write tags + read filters + tenant-safe deleteAllSummaries). #10010 / #10011 / #10017 remain queued with explicit capability summaries.

Test plan

Documentation-only change — no code paths affected. Verified:

All 7 cross-referenced issue IDs resolve
No commercial-partner references (per the CRITICAL confidentiality feedback memory)
Checkbox state reflects current reality: #10015 = done (minus optional Playwright coverage), #10016 = in-progress (1/4 merged)

Continues the #9748 ROADMAP maintenance cadence established by PR #10122
Reflects merges from PR #10121 (#10001), PR #10123 (#10007), PR #10124 (the client scrub), PR #10128 (#10000), PR #10122 (earlier ROADMAP update itself)
Follow-up tickets filed this session and parented under #9999 via update_issue_relationship: #10125 (engine/architecture drift — standalone), #10126 (engines.neo missing — standalone), #10127 (HealthService topology reporting — parented #9999), #10129 (backup substrate atomic-bundle rewrite — parented #9999)

Resolves a maintenance-cadence check on #9748 (the "ROADMAP state sync" follow-up flagged in PR #10122's body as something worth formalizing into a chore schedule).

Origin Session ID: 1c001810-be28-4554-bb56-c98f9b91bbfb

Summary

Changes

Test plan

Related