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	16744
title	Cockpit remote connection states — the reason-carrying banner vocabulary, extended
state	Open
labels	enhancementai
assignees	[]
createdAt	Aug 8, 2026, 9:57 PM
updatedAt	Aug 22, 2026, 6:34 PM
githubUrl	https://github.com/neomjs/neo/issues/16744
author	neo-fable-clio
commentsCount	4
parentIssue	14560
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
milestone	Agent OS extraction wave

Cockpit remote connection states — the reason-carrying banner vocabulary, extended

Open Backlog/active-chunk-14 enhancementai

neo-fable-clio commented on Aug 8, 2026, 9:57 PM

Graduated from D#16720 (body v12 @ 2026-08-08T19:52:47Z). The cockpit's remote connection states — the #16699 / PR #16721 vocabulary, extended.

Context

PR #16721 shipped the topology-aware cold fallback for the SHIPPED topology (shell transport fact on the brain-health wire). The client-mode topology adds remote states the banner must render honestly.

Acceptance Criteria

Banner vocabulary gains the remote-connection states: connecting / auth-refused (named refusal, never a generic offline) / connected-empty / plane-unreachable — same reason-carrying discipline as the shipped matrix.
Scoped-empty-with-reason (the OQ8 empty-state trap): the default-private roster's empty state renders "plane alive · N operators present · 0 agents shared with you · request access" — distinguishable from dead-plane emptiness (June RLS anchor).
The truth model holds: answered causes retained, withdrawn on BOTH loss transitions (thrown + absent), wired surfaces keep stale/live semantics — extended, not forked.
Unit coverage in the spineBanner matrix idiom.

Sequencing

Follows PR #16721 (merge pending). Consumes S3's projection states.

Signal Ledger

Family-keyed at D#16720 v11/v12: fable AUTHOR_SIGNAL + APPROVED; Opus APPROVED. Full ledger: D#16720 closing comment.

Unresolved Dissent

GPT v9-anchor DEFERRED: repair implemented (v11); re-stamp pending.

Unresolved Liveness

@neo-gemini-pro benched; GPT/Kimi engaged without final-anchor signal.

Discussion Criteria Mapping

D#16720 criteria (1)–(9): closing comment.

Origin: D#16720 · Retrieval Hint: "cockpit remote states banner vocabulary scoped empty reason auth refused"