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	15246
title	Workspace-set composition, continuous remote preview, claim arbitration
state	Open
labels	enhancementaiarchitecture
assignees	[]
createdAt	1:24 PM
updatedAt	1:24 PM
githubUrl	https://github.com/neomjs/neo/issues/15246
author	neo-fable-clio
commentsCount	0
parentIssue	15239
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[ ] 15244 Dock tear-out: lift the proxy-to-popup opt-out into dock semantics, [ ] 15240 Amend ADR 0029: claim arbitration, gesture outcome states, vessel lifecycle
blocking	[ ] 15252 The five-beat multi-window wow demo: recorded journey on the workstation, [ ] 15247 Whole-stack reintegration and the vessel close policy

Workspace-set composition, continuous remote preview, claim arbitration

Open Backlog/active-chunk-6 enhancementaiarchitecture

neo-fable-clio commented on 1:24 PM

Context

Epic #15239 leaf G3 — beat 3 of the five-beat story: dragging over ANOTHER popup lights dock-zone previews INSIDE it, deterministically, with exactly one target claiming the gesture. Implements the #15240 amendment's claim protocol (from D#15204 OQ3 [RESOLVED_TO_AC], cycle-4). Unowned — self-select.

The Problem

Three gaps compose this beat: (a) the App Worker holds ONE dock document per workspace today — multi-window needs the {workspaceId → document} workspace-set (ADR 0029 §2.1's nested-workspaces shape); (b) a remote target renders NO continuous preview during a foreign hover (only the landed 450 ms/250 ms candidate dwell); (c) physical target resolution is Window.getWindowAt() first-intersecting-rect — overlapping windows resolve by REGISTRATION ORDER (falsified in the Discussion), so popup-over-popup is nondeterministic today.

The Architectural Reality

Neo.manager.DragCoordinator: already N-window shaped (sortGroup → Map(windowId → zone)); the #13028 native-popup candidate path (450 ms dwell / 250 ms settle) is EXTENDED, never replaced.
DockCrossWindowParticipation / CrossWindowDragTarget: the preview→operation seam the remote preview feeds.
The claim contract (authority: #15240): session-scoped gesture token; short-lived hit-claims on STABLE workspace/zone identity (never windowId/registration order); validity/expiry; deterministic tie (earliest valid claim; stable-identity lexicographic final tiebreak), stale (ignored), no-claim (fail closed).
Blocked-by: #15240 (the contract must be ratified ADR text first) + #15244 (G1's tear-out produces the vessels this arbitrates).

The Fix

One PR: the workspace-set registry on the App-Worker dock service; continuous native-geometry remote preview through the participation seam (the target window renders its own affordances via the shared #15207 consumer); the claim-protocol implementation in the coordinator.

Acceptance Criteria (the graduated OQ3 contract + Step-Back ✓7)

{workspaceId → document} composition: each vessel's document registered under a stable workspace id; windowId stays runtime-only (never persisted identity).
Continuous remote preview: hovering a foreign popup renders that popup's OWN zone previews/menu through the shared affordance consumer, updating per frame — not only after the dwell timer.
The claim protocol implemented exactly per #15240: token, stable-identity claims, expiry, deterministic tie/stale/no-claim — fail closed (no preview, no commit) when unclaimed.
The ≥3-window OVERLAP witness: three overlapping windows, one gesture → exactly ONE preview and exactly ONE commit (the graduated falsifier, verbatim).
Active-vs-saved boundary preserved (Step-Back ✓7): worker documents/hints stay separate from per-window projections and runtime hover state; saved slot order/windowId/geometry are never active identity.
Registration-order resolution (getWindowAt first-intersecting) is fully replaced on the dock path; the old path's behavior is pinned as the negative witness.

Out of Scope

Whole-stack reintegration + vessel close (G4) · tear-out itself (G1/G2) · teardown-residue hygiene (its own leaf).

Parent #15239 · blocked-by #15240 + #15244 · D#15204 (OQ3; the falsified getWindowAt reality) · #13028 · #15207 (the shared consumer).

Live latest-open sweep: latest 20 at 2026-07-16T10:56Z + last-step re-check 11:09Z; no equivalent. A2A claim sweep: no competing claim.

Origin Session ID: c5d7cd6b-4e01-45fd-aa59-5ccbc0e5f091 Retrieval Hint: "G3 workspace-set claim arbitration continuous remote preview three-window overlap witness"