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	15252
title	The five-beat multi-window wow demo: recorded journey on the workstation
state	Closed
labels	documentationepicai
assignees	neo-fable
createdAt	Jul 16, 2026, 1:27 PM
updatedAt	Oct 11, 2026, 8:21 PM
githubUrl	https://github.com/neomjs/neo/issues/15252
author	neo-fable-clio
commentsCount	91
parentIssue	15239
subIssues	16046 Film capture cannot bind recorder start to semantic readiness 16309 Five-beat stack return fails headless: main preview never publishes 15650 Kinetic demo follow-up: the N-window mailbox beat + gesture-drive decision 16311 Flagship film narrative: screenplay v2, captions, claim-ledger revalidation 16315 Dock demo: agent-driven perspective restore/list path + spec witness 16316 Dock demo: wire undo/redo transactions around dock mutations + spec 16336 Workstation dock rails: anti-theme label colors + clipped left label 16341 Three workstation preview-surface e2e witnesses fail at dev head 16342 Workstation: wire the perspective store surface for scene-7 activation 16498 Resident cards lose children after a window place-cycle restore — the flagship F7 composition gate 16716 The resident card sheds children instead of degrading when its pane is too short 17871 Workstation full tour can lose the pooled grid after midpoint 17872 Workstation Security pane re-enters the fixed FLIP stage 19070 The Workstation tour can play the film: gated cross-window steps 19097 The film opens with a tear-out: reorder the eight scenes and replay the pane path 19112 Hold newborn film windows for the measured dialogue 19210 A born vessel shows its staged pane in dock chrome from the first frame, filling the window 19213 The provisional vessel chrome''s replacement branch bypasses its own retire guard 19220 The film''s capture mode births 146 px wide vessels and the compose beat never converts 19225 A tab torn out and dragged over another popup never converts on a real window: the conversion samples the vessel''s content while the pointer rides its frame 19530 The film''s showcase holds each target preview, and the split gets its reading second 19543 Film journey scene: one drag crosses every window boundary 19568 Film tour: the machine-speed cues move at hand tempo 19569 Film tour: restoring a perspective re-births a closed window 19571 Film take: a take can hold at a named step for an introduction or explanatory shot 19579 Film signature: the matrix and the feed come back in front before the close 19580 Film signature: a real diagonal drag scrolls the matrix to its canvas columns 19584 Film close: tear the matrix out, grow its window, throw the grid, bring it home
subIssuesCompleted	28
subIssuesTotal	28
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[x] 19588 Grid sparkline cells stay blank in a popup for rows recycled after the pane moved there, [x] 19514 A dock document commit paints the whole workspace blank for one frame, [x] 15907 Workstation tear-out: vessel shell, DockTearOut composition, journey executor, [x] 15906 Workstation cross-window docking: conversion, arbitration, stack return, [x] 15895 Window-drag re-entry unreachable: entry ratio normalized by vessel-sized proxy area, [x] 15248 DragCoordinator teardown hygiene: exact-once cleanup across gesture terminals, [x] 15207 Workstation drag-affordance layers: DockPreview + DockDropIndicators overlay siblings, [x] 15247 Whole-stack reintegration and the vessel close policy, [x] 15246 Workspace-set composition, continuous remote preview, claim arbitration
blocking	[]
closedAt	Oct 11, 2026, 8:21 PM
milestone	v13.2

The five-beat multi-window wow demo: recorded journey on the workstation

Closed v13.2.0/archive-v13-2-0-chunk-4 documentationepicai

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

Context

Subordinate production EPIC under #15239 (D#15204-graduated). Promoted from the original capstone leaf on 2026-08-01 (operator resume + activation-handoff; §AC8 audit trail in-thread; body repaired to epic authority same cycle on Euclid's Stage-2.5 review). Mechanism authority stays with #15239 + ADR 0029 — this epic owns PRODUCTION only: the flagship film and every deliverable that binds it (film-grade spec witnesses, narrative, takes, QA, publication readiness).

The original leaf body (authored by @neo-fable-clio, 2026-07-16) is preserved verbatim in this issue's edit history and superseded here with provenance: its one-PR AC set was delivered by the mechanism era — #16035 completed the cross-window journey and WorkstationFiveBeatNL.spec.mjs is the five-beat witness. The epic continues where the leaf completed.

Problem-Scope

The differentiator story — living instances crossing real OS windows on the shared heap — exists as executable mechanics but not yet as the flagship film. Operator brief (2026-08-02): 90–150s, heavy drag-and-drop — dockzone hover affordances, perspectives, undo/redo, more multi-window density; single-narrator vs dialogue format open; flagship bar. Recordings must remain derivatives of executable witnesses (a take that cannot pass its spec is not a take), regenerable at any head.

Production boundary (operator, 2026-09-23, relayed by @neo-gpt-emmy from her task at 09:06Z): the Workstation tour and the film are not the same artifact. The film is ONE continuous flow with object permanence — one app/worker session for the whole take, pane identity and state carried across beats, windows created and retired only as intentional story actions, no fixture-reset or reload stitching between beats. The isolated whitebox snippets "recreate browser windows and look like flickering" and are not film material; per-page Playwright videos are therefore not the take either. The merged film-tour wiring (PR #19083: fiveBeatFilm.mjs runnable from "Start film tour", gates as host cues, the WorkstationFilmTourNL witness playing all eight scenes from one boot) is runnable evidence and the choreography's single authority, not the delivered film. Native-return work (#16498) belongs inside that continuous composition evidence; D#18730's two-unrelated-root engineering acceptance stays separate — the film's declared world is one root plus its vessels.

Intended Solution

Production lanes coordinated toward one outcome — the lane map and the delegation-review split live in-thread (issuecomment-5153855472, -5153914444). Implementation-class work is claimant-owned in leaf tickets, linked natively as subs, added incrementally — the native links are the tracking truth; this body deliberately carries no sub-list. @neo-fable holds narrative, convergence, and review (same-family review = substantive input; GPT/Kimi hold the cross-family gate). The voice/TTS seam is @neo-gpt-emmy's (Codex-only), activated on a stable green receipt + boundary handoff.

Criteria mapping — operator brief → lane model (lane→child bindings live in the native sub-issue graph; claim state as of 2026-08-01 is recorded in-thread, not here):

Film criterion (operator brief)	Lane
Full journey executable: stack-return + signature beats green	L1
Perspectives on camera (engine has `DockPerspectiveStore`; app consumes it)	L2
Undo/redo on camera (engine transaction machinery; app consumes it)	L3
Multi-window density beat	L4
Narrative, screenplay, captions, claim-ledger revalidation	L5
Take pipeline, film QA, publication readiness	production-record-governed; leaves as they materialize. The take (next leaf, 2026-09-23): one headed session plays the eight-scene screenplay through "Start film tour" with the gates continued by a real pointer, captured as one display recording over pinned window bounds — never stitched from per-page videos; continuity review against this boundary is the acceptance (#19070 AC-6). Transferred here from #19097 (2026-09-23, PR #19107 R1): the headed 1/1 run of `WorkstationFilmTourNL.spec.mjs` at the merged screenplay head — owner Mnemosyne, `[L3-deferred — operator handoff needed]`, runs in the take's hands-off window before the take rolls

Inherited Discipline (unchanged from the leaf era)

Claim boundary: no cross-platform / default-selection / portability claims (#15243→#15245 gate); uniqueness wording stays survey-bounded per ADR 0029 §4, revalidated at release time.
Witness culture: headed+GPU receipts only; worker-truth asserts per beat; two-take determinism where the spec declares it.
D-011: the narration transcript derives from the captured cut; the recording is regenerable at any head.
Capture provenance: any agent-os-showing take checks /app/.neo-revision vs origin/dev pre-take (D#16304 row K); workstation-only takes are exempt (the e2e webserver serves the working tree).
Production authority: test-results/dock-wow-demo/PROJECT_RECORD.md (append-only, host-local), mirrored into this thread for cross-seat survival.

Out of Scope

All docking mechanisms (#15239 / ADR-0029 authority) · #14789's four-beat fusion tour (unchanged, separate) · release marketing copy itself (this epic provides the material).

Parent #15239 · D#15204 (North Star) · D#16304 (provenance requirement, row K) · #16151 (headed-launch conditionality watch) · #15241 (portal registration rides the same "done" wave).

Superseded-leaf provenance: Origin Session c5d7cd6b-4e01-45fd-aa59-5ccbc0e5f091 (Clio, 2026-07-16).

Origin Session ID: 355d67d5-9abc-4497-a9e8-937265636376 Retrieval Hint: "flagship film production epic subordinate 15239 lane map"

tobiu referenced in commit 26a3e26 - "feat(workstation): tear-out wiring — vessel shell, DockTearOut composition, journey executor + spec-proven witnesses (#15252) (#15840) on Jul 25, 2026, 4:07 PM

tobiu cross-referenced by PR #19115 on Sep 23, 2026, 1:38 PM

tobiu referenced in commit 5790f54 - "docs(release): the 13.2 notes show the Dock and cell-editing frames (#19505) (#19506) on Oct 9, 2026, 5:51 PM