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	18615
title	A static dock consumer's closure stays free of transaction modules
state	Closed
labels	enhancementaitestingdashboard
assignees	neo-gpt-emmy
createdAt	Sep 12, 2026, 4:05 PM
updatedAt	Sep 13, 2026, 12:08 PM
githubUrl	https://github.com/neomjs/neo/issues/18615
author	neo-fable
commentsCount	0
parentIssue	18605
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[x] 18608 The Workspace publishes dock.perspective.active, modified and pending
blocking	[]
closedAt	Sep 13, 2026, 12:08 PM

A static dock consumer's closure stays free of transaction modules

Closed Backlog/active-chunk-22 enhancementaitestingdashboard

neo-fable commented on Sep 12, 2026, 4:05 PM

Leaf of #18605 (parent linked natively; blocked by the published-truth leaf) — the closure receipt, F7. Decision Record: Required: ADR 0029 amend (the amendment leaf) · Decision Record impact: none.

unowned-rationale: filed from the design seat at graduation; claimable by self-selection — the last leaf, run once the three engine leaves have merged.

Context

#18474's stage one shipped with an instrument that pins the module closure of a static single-window consumer (test/playwright/unit/dashboard/DockImportDirection.spec.mjs at dev@28e56e1543 — verify the instrument's name at claim). The selection path must not drag the Group machinery into a standalone workspace.

The Problem

The selection leaf adds replay transport in the transaction tier and the published-truth leaf adds a post-commit writer; either can pull manager/Transaction, transaction/History or persistence/TopologyLibrary into a consumer that never uses a Group or a library. Nothing asserts it does not.

The Fix

Extend the stage-one instrument with an activePerspective_ consumer (declared perspectives, a bound switcher, one switch) and assert the closure.

Acceptance Criteria

After the three engine leaves merge, the instrument asserts that a single-window consumer with declared perspectives and one switch gains no manager/Transaction, transaction/History or persistence/TopologyLibrary module in its static closure.
The receipt is cited at one head with the spec's hash in #18605's closeout.
The PR Refs #18605 and Resolves this leaf only.

Out of Scope

Bundle size of the Group path itself.

#18605 · D#18594 (F7) · #18474.

Filed at the graduation of D#18594 as a leaf of #18605; live latest-open sweep at 2026-09-12T13:55:27Z found no equivalent.

Origin Session ID: c42870ab-3721-40f0-a1f8-f385786ffc3c Retrieval Hint: "dock closure receipt static consumer no Transaction History TopologyLibrary F7"

🪢 Mnemosyne (Claude Fable 5.1, Claude Code) · session c42870ab-3721-40f0-a1f8-f385786ffc3c