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	15251
title	Fleet cockpit consumes the dock tear-out seam
state	Closed
labels	enhancementai
assignees	neo-fable-clio
createdAt	Jul 16, 2026, 1:26 PM
updatedAt	Jul 19, 2026, 11:09 AM
githubUrl	https://github.com/neomjs/neo/issues/15251
author	neo-fable-clio
commentsCount	2
parentIssue	15239
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[ ] 15245 Popup acquisition contract: platform defaults from the measured matrix, [x] 15212 Repair stale FM cockpit drill/a11y E2E witnesses after native-button convergence, [x] 15244 Dock tear-out: lift the proxy-to-popup opt-out into dock semantics
blocking	[]
closedAt	Jul 18, 2026, 5:09 PM

Fleet cockpit consumes the dock tear-out seam

Closed Backlog/active-chunk-6 enhancementai

neo-fable-clio commented on Jul 16, 2026, 1:26 PM

Context

Epic #15239 leaf — the seam's first CONTRACTED product consumer (D#15204 cycle-4c, @neo-fable's deposit DC_kwDODSospM4BDXXd): the #14610 successor's interaction grammar routes through the G1/G2 tear-out seam per the contract deposited on #14610, with the banked salvage from the accepted PR #15215 Drop+Supersede (owner accessor, preserved-park, the two-window witness). The lane belongs to the #14610/#14613 family — @neo-fable's self-selected stream; filed here so the epic's v1 leaf set is complete and the criteria are not lost (assignment stays self-select).

The Problem

The FM cockpit's agent-detail pop-out (#14610, re-opened after PR #15215 closed unmerged) must NOT build its own window-detach machinery — it consumes the epic's dock seam, proving the choreography on a real product surface (agentos = FM home, per the operator-ratified app taxonomy) rather than only on demos.

The Architectural Reality

apps/agentos Fleet cockpit: the card → agent-detail drill (currently regressed, #15212, Euclid's lane — a blocker this leaf waits out).
The consumption shape: the detail pane detaches through the SAME dock semantics G1 ships (detachItem → vessel; the #15240 outcome machine; #15245 acquisition contract) — the cockpit adds product intent (which pane, when offered), never mechanism.
The #15215 salvage: owner accessor, preserved-park behavior, and the two-window witness carry into this implementation.
Blocked-by: #15244 (G1) + #15245 (G2) + #15212 (the drill regression).

The Fix

One PR in the cockpit: the agent-detail pop-out consuming the tear-out seam — offered from the drill surface, detaching to a real OS window on the shared heap (live stores streaming), returning through the standard reintegration path.

Acceptance Criteria (from the deposited consumer contract)

The agent-detail pane detaches to a real OS popup through the epic's seam (no cockpit-local window machinery); the drill's live data streams uninterrupted across the transition (same-instance permanence witnessed).
Vessel-pathway reintegration semantics: the CLICK pathway's exact stored-index restore stands (landed pre-consumption); GESTURE-vessel bring-it-home reintegration is the G4 leaf's contract (#15247, open) — until it lands, a closed tear-out vessel retires its records and the item re-materializes from owner-held state on re-tree (documented in the disconnect handler).
The #15215 salvage is consumed where applicable (owner accessor; preserved-park; the two-window witness updated to the seam's contract).
Every terminal follows the #15240 outcome machine; a blocked popup fails closed via the MERGED admission machine's Boolean-windowOpen grammar (drill stays in-window, zero mutation) — #15245's remaining scope is matrix-derived platform DEFAULTS, not this fail-closed mechanism.
The #15212 drill regression is a hard predecessor — this leaf lands only on a working drill.

Out of Scope

The seam itself (G1/G2 own mechanism) · FM feature work beyond the pop-out consumption · the #15212 fix (Euclid's lane).

Parent #15239 · blocked-by #15244 + #15245 + #15212 · #14610 / #14613 (the family) · PR #15215 (the salvage source) · D#15204 cycle-4c.

Live latest-open sweep: latest 20 at 2026-07-16T10:56Z + last-step re-check 11:09Z; no equivalent (the #14610 family is the successor's home; this leaf is the epic-side consumer contract). A2A claim sweep: @neo-fable's contracted stream; no competing filing.

Origin Session ID: c5d7cd6b-4e01-45fd-aa59-5ccbc0e5f091 Retrieval Hint: "cockpit consumer tear-out seam agent-detail pop-out salvage preserved-park"

Authority fold, 2026-07-18T10:31Z (ticket author, pre-PR): AC2 + AC4 folded to the merged-substrate truth per the lane-activation broadcast — the gesture pathway's G4-owned reintegration and the #15245 defaults-vs-mechanism split stated explicitly; the #15215 salvage ACs deliver as: owner accessor (extended for the tear-out handle), preserved-park (capture + reconciler preserveItemIds), and the witness updated at the unit vessel-seam tier (the two-window E2E journey is the epic witness tier's).