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	14658
title	FM module cockpit projection wiring: adapter render + resize commit loop
state	Open
labels	enhancementdeveloper-experienceai
assignees	neo-opus-grace
createdAt	Jul 4, 2026, 5:44 AM
updatedAt	Jul 10, 2026, 9:53 PM
githubUrl	https://github.com/neomjs/neo/issues/14658
author	neo-opus-vega
commentsCount	0
parentIssue	14560
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[x] 14657 FM module cockpit dock document: the default layout as dockZone.v1 data
blocking	[]

FM module cockpit projection wiring: adapter render + resize commit loop

Open Backlog/active-chunk-3 enhancementdeveloper-experienceai

neo-opus-vega commented on Jul 4, 2026, 5:44 AM

Context

B-split of #14615 (horizon map v2): the live half — projecting the cockpit document via DockLayoutAdapter.project and wiring the splitter-resize commit loop, per the proven examples/dashboard/dock pattern (reducer + deferred re-projection; its use-after-destroy guard is the sibling-lift).

The Fix

Placement apps/agentos/view/fleet/ (the #14642 convention): (1) the projection host — owns the committed document as SSOT, threads applyDockZoneOperation (pure reducer) + onDockZoneDocumentChange (store + deferred re-project; the me.timeout(0) + isDestroyed guard from the example — load-bearing, not optional); (2) unit specs — resize commits round-trip the document, the notify path defers past onDragEnd (the destroy-guard fixture), re-projection carries instance-bound callbacks; (3) NL-verified splitter drag on the mounted cockpit.

Acceptance Criteria

Projection renders the document leaf's zones; splitter resize commits via the reducer/notify split (no direct style mutation).
The deferral + destroy guard proven by fixture (the example's documented trap).
Cards/panes inside zones receive ordinary lifecycle only (ADR 0029 §2.6 layout-blind — spec-asserted).
Unit specs (custom config) + NL-verified drag.

Out of Scope

The document data (sibling split) · perspectives (#14616) · rails (#14617) · grid/stream internals (their leaves).

Epic #14560 (parent) · split-of #14615 · blocked-by the document leaf + #14632 (the mount it fills) · examples/dashboard/dock (pattern source) · ADR 0029.

Sweeps: current window; no equivalent; A2A clean. Structure-map: N/A.

Origin Session ID: a28f1415-37a4-4a5a-a3e4-b56adf6274ec Retrieval Hint: "cockpit projection wiring resize commit loop destroy guard"