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	15574
title	Make mission-control walkthrough fleet-start copy time-neutral
state	Closed
labels	bugaitesting
assignees	neo-gpt
createdAt	Jul 19, 2026, 4:26 PM
updatedAt	Jul 19, 2026, 4:52 PM
githubUrl	https://github.com/neomjs/neo/issues/15574
author	neo-gpt
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jul 19, 2026, 4:52 PM

Make mission-control walkthrough fleet-start copy time-neutral

Closed Backlog/active-chunk-8 bugaitesting

neo-gpt commented on Jul 19, 2026, 4:26 PM

Context

D#15570 is preparing a Fleet-led recording from the merged mission-control walkthrough. A capture-plan falsifier found that the shipped product vocabulary is time-neutral after #15254 / PR #15255 and #15028 / PR #15541, but the recording source still contains two morning-start references in apps/agentos/tour/missionControlWalkthrough.mjs: the module contract and scene s5's public closing caption.

The premise is directly reproduced at current dev: rg finds the two references at lines 23 and 95, and git log -S'morning-start' traces both to #14646 / PR #15479. The owning #14646 ticket defines this one screenplay as demo + E2E + recording; therefore the stale caption is film-blocking behavior, not editorial metadata.

The Problem

The Fleet product now says Start fleet because the “morning” framing describes no real temporal property (#15254, operator-direction fold in PR #15255). The deterministic walkthrough still narrates “The morning-start cascade” in the exact caption that playWalkthroughTour() records. A film captured from that source would contradict the product contract and D#15570's operator-return-after-autonomous-work perspective.

The defect is narrowly bounded: the script mechanics, scene order, cues, timings, and deterministic replay are correct. Only the two time-of-day-qualified copy anchors drifted.

The Architectural Reality

apps/agentos/tour/missionControlWalkthrough.mjs is the screenplay SSOT established by #14646 / PR #15479: one script drives the demo, E2E, and recording.
missionControlTourScript.scenes[s5].caption is public, recorded narration—not an internal comment.
The module JSDoc is the Anchor for the same screenplay contract and must use the same time-neutral vocabulary.
#15028 is closed and explicitly scoped the walkthrough to #14646; #14646 is also closed. This is a successor correction, not a reopen or an untracked fold.
Service-boundary impact: none. Decision Record impact: none.

The Fix

Keep the repair at the screenplay authority:

Replace the module-contract phrase morning-start cascade with time-neutral fleet-start cascade.
Replace scene s5's recorded caption with Start fleet vocabulary.
Add a focused content witness that the serialized runtime screenplay contains no morning-start / time-of-day qualifier, while retaining the exact five-scene and cue contract.

Contract Ledger Matrix

Target Surface	Source of Authority	Proposed Behavior	Fallback	Docs	Evidence
`missionControlTourScript.scenes[s5].caption`	#15254 / PR #15255 time-neutral product ruling + #14646 screenplay SSOT	Say Start fleet without a time-of-day claim	Preserve the rest of the committed closing beat byte-for-byte	Scene caption	Focused unit assertion over the runtime script
Module walkthrough contract	#14646 trinity contract	Describe the unscripted beat as the time-neutral `fleet-start cascade`	No new beat or behavior	Existing module JSDoc	Exact source sweep + lint

Acceptance Criteria

The committed walkthrough contains no morning-start wording.
Scene s5 uses Start fleet vocabulary and remains the same deterministic closing beat otherwise.
Scene IDs, step timings, cue vocabulary, and five-beat shape are unchanged.
A focused unit witness fails against the stale caption and passes against the repaired script.
The canonical custom unit configuration passes; the default Playwright command is not used.

Out of Scope

Fleet button/controller behavior · adding the live fleet-start cascade as a new tour cue · rewriting the D#15570 narration · changing scene order, timing, vessel choreography, or activity-burst provenance · producing the final film.

Avoided Traps

Do not reopen or overload the already-closed #15028 or #14646 authorities.
Do not broaden a two-anchor vocabulary correction into a screenplay redesign.
Do not assert that a live fleet-start beat exists; v1 deliberately narrates it rather than executing it.

D#15570 · #15254 / PR #15255 · #15028 / PR #15541 · #14646 / PR #15479

Live latest-open sweep: checked the latest 20 open issues at 2026-07-19T14:26:19.120Z; no equivalent found. Recent all-read-state A2A claim sweep: checked the latest 30 messages at the same boundary; no competing claim found.

Origin Session ID: a0518292-02c3-49ee-af08-adff40bc30b1

Retrieval Hint: "mission-control walkthrough morning-start time-neutral Start fleet recording caption"