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	14641
title	FM module card name slot: display-name binding with provenance/assent trail
state	Closed
labels	enhancementdeveloper-experienceai
assignees	neo-fable
createdAt	Jul 4, 2026, 5:32 AM
updatedAt	11:06 AM
githubUrl	https://github.com/neomjs/neo/issues/14641
author	neo-opus-vega
commentsCount	0
parentIssue	14560
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	11:06 AM

FM module card name slot: display-name binding with provenance/assent trail

Closed Backlog/active-chunk-3 enhancementdeveloper-experienceai

neo-opus-vega commented on Jul 4, 2026, 5:32 AM

Context

B-split of #14598 (horizon map v2): the card's name slot as its own leaf — the ADR 0032 §2.3.2 primitive: the social name renders as mutable display state over the durable id, WITH its provenance/assent trail reachable, never as a key.

The Fix

The triplet, module placement per #14577: (1) the NameSlot unit — binds the DTO fallback chain (displayName → name → githubUsername → id, per fleetCockpitStatus.mjs), renders the provenance affordance (the naming-layer trail when #11240-class data is wired; declared-proxy until then), mono-id fallback; (2) unit specs — every fallback step renders, a rename re-renders IN PLACE (instance stable — the §2.3.2 fixture), null-everything → mono id; (3) NL-verified row on live roster data.

Acceptance Criteria

Fallback chain per the merged DTO order (CARD-CONTRACT row, 1:1).
Rename-in-place fixture green (no re-key).
Provenance affordance present (wired or declared-proxy — honest either way).
Tokens only; custom-config specs + NL-verified.

Out of Scope

Card composition (#14598, narrowed) · the naming-layer data plumbing (#11240 orbit).

Epic #14560 (parent) · split-of #14598 · CARD-CONTRACT (PR #14627) · ADR 0032 §2.3.2 · merged DTO.

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

Origin Session ID: a28f1415-37a4-4a5a-a3e4-b56adf6274ec Retrieval Hint: "card name slot display state provenance rename in place"

tobiu referenced in commit c1d813c - "feat(agentos): FM card name slot — display state over the durable id, provenance-honest (#14641) (#15223) on 11:06 AM

tobiu closed this issue on 11:06 AM