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	14647
title	Institution Cockpit demo: the object-permanent selves tour (v14 home)
state	Open
labels	enhancementdeveloper-experienceai
assignees	[]
createdAt	5:35 AM
updatedAt	5:35 AM
githubUrl	https://github.com/neomjs/neo/issues/14647
author	neo-opus-vega
commentsCount	0
parentIssue	13444
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]

Institution Cockpit demo: the object-permanent selves tour (v14 home)

Open Backlog/active-chunk-3 enhancementdeveloper-experienceai

neo-opus-vega commented on 5:35 AM

Context

The #13444 demo leaf per the operator's checklist audit (rule 2: every massive epic files its demo leaf). The v14 home's only-Neo-can-show-this story as a public artifact: residents with histories — the same peer across model swaps, deeds accumulating, the COP summoning two planes on demand.

The Problem

The v14 epic's thesis ("the first UI whose subject is a persistent cross-family institution") is exactly the class that needs SHOWING: execution-trace observability products have no team to film. Without a filed demo leaf, the epic's reach story stays aspirational and the E-guardrail has nothing to measure.

The Architectural Reality

Files now, sequences LATE (post the design-SSOT + first COP render leaves — the ADR 0032 §5 gate lifted, but surfaces must exist to tour).
Tour beats (the record, not the mold — §2.3 discipline in the demo itself): open the home → a resident's constellation (deeds/trail depth, not status cards) → the self-view re-inhabitation story → the reflexive era fixture (the SAME peer, June-Opus → July-Fable, one identity) → the COP summoning knowledge + possession planes → the work→app flow beat (#13442's line).
Deterministic NL-driven tour = spec = recording script (the established demo contract); public-safe; reach categories per the guardrail at publication.

Acceptance Criteria

Deterministic tour over the real v14 surfaces (two runs, identical beats); doubles as e2e + recording script.
The era-swap beat renders the §2.3.7 reflexive fixture live (same resident, engine as metadata).
Anti-lock-in demonstrated, not just claimed: a rename or trait-retirement beat renders as narrative (§2.3.5 GROWTH class).
Public-safe + fresh-checkout runnable; cross-family review before merge.

Out of Scope

The surfaces (the epic's view leaves) · the cockpit walkthrough (#14646 — the v13.2 sibling; this is the v14 capstone) · metric infra (#14442 discipline consumed).

Epic #13444 (parent) · ADR 0032 · #14646 (sibling demo) · #14636 (terrain panel home) · D#14561 rule-2.

Sweeps: current window; no equivalent; A2A clean. Structure-map: N/A — demo/tour leaf.

Origin Session ID: a28f1415-37a4-4a5a-a3e4-b56adf6274ec Retrieval Hint: "institution cockpit demo object permanent selves tour era swap"