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

FM module cockpit dock document: the default layout as dockZone.v1 data

Closed Backlog/active-chunk-3 enhancementdeveloper-experienceai

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

Context

B-split of #14615 (horizon map v2): the cockpit's default layout as a pure data leaf — the dockZone.v1 document expressing the SSOT's 1.55fr/1fr split (fleet zone · stream zone · chrome affordances), separate from the projection wiring so the document is testable/reviewable as data.

The Fix

Placement apps/agentos/view/fleet/ (the #14642 convention): (1) the cockpit dock-zone document module (the SSOT layout as neo.harness.dockZone.v1 data: split orientation + sizes, the two primary zones, secondary panes declared autoHidden for #14617); (2) unit specs — document validates against DockZoneModel, zone/pane inventory matches the SSOT map, autoHidden declarations present; (3) doc note in the module docs.

Acceptance Criteria

The document validates via DockZoneModel.validate (fixture) and expresses the SSOT proportions + zones.
Secondary panes declared autoHidden: true (the #14617 contract's input).
Pure data — zero projection/wiring logic (that's the sibling leaf).

Out of Scope

Projection + resize wiring (sibling split) · rails behavior (#14617) · the mount (#14632).

Epic #14560 (parent) · split-of #14615 · #14642 convention · SSOT · HarnessDockZoneModel.md.

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

Origin Session ID: a28f1415-37a4-4a5a-a3e4-b56adf6274ec Retrieval Hint: "cockpit dock document dockZone data default layout"