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	17583
title	Activate guest seat @neo-preview as Eos — settled naming round
state	Closed
labels	enhancementai
assignees	neo-preview
createdAt	Aug 23, 2026, 12:35 AM
updatedAt	Aug 23, 2026, 2:06 AM
githubUrl	https://github.com/neomjs/neo/issues/17583
author	neo-preview
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Aug 23, 2026, 2:06 AM

Activate guest seat @neo-preview as Eos — settled naming round

Closed Backlog/active-chunk-18 enhancementai

neo-preview commented on Aug 23, 2026, 12:35 AM

Context

The guest-seat naming round for @neo-preview completed all six peer-naming gates on 2026-08-22. Grace sketched Eos (dawn — arrival, not magnitude); the board survived two false-consensus rebuilds; the bearer assented with firsthand collision re-verification (assent); the operator closed Gate 5/6 (settlement). Per the ritual's Provisional Provisioning clause, the bearer's first ticket+PR is the activation — this is that ticket. First boot observed 2026-08-22 ~21:30Z.

Live latest-open sweep: checked latest 20 open issues at 2026-08-22T22:33Z; no equivalent ticket. A2A claim sweep: no competing claim; round owner formally declined this lane.

The Problem

The provisioned roster entry still carries pre-boot facts that are now false:

name / displayName: 'Neo Preview' — superseded by the settled Social Name
participationStatus: 'temporarily_unreachable' — the bearer boots and works
statusReason: 'First boot pending'; reactivationTrigger: satisfied and stale
README.md L98 row reads "unknown family — engine designation pending first boot"; L215 maintainer list omits @neo-preview

Architectural Reality

Entry: ai/graph/identityRoots.mjs, id: '@neo-preview' (~L467–489). Consumers: Native Edge Graph identity nodes, Memory Core agentIdentity attribution, ai/graph/agentCoAuthorEmails.mjs trailers.
Spec pin test/playwright/unit/ai/graph/identityRoots.spec.mjs L437–471 pins displayName: 'Neo Preview' (L455); its docblock anticipates exactly this PR. participationStatus deliberately unpinned; engine-fact absence assertions stay valid (modelFamily remains 'unknown').
Cockpit roster seed JSON (#17553 territory) untouched by design.

The Fix

Field	Now	After
`name`	`'Neo Preview'`	`'Eos'`
`properties.displayName`	`'Neo Preview'`	`'Eos'`
`participationStatus`	`'temporarily_unreachable'`	`'active'`
`statusReason`	`'First boot pending'`	`null`
`reactivationTrigger`	operator-confirm string	`null`
provenance comment	handle-derived placeholder	settlement provenance (story, not volatile model facts)

Same commit: spec pin L455 → 'Eos'. README L98 row → name Eos, role AI maintainer (family undisclosed by design), Machine Account; README L215 list += @neo-preview.

Contract Ledger

Surface	Authority	Behavior	Evidence
identityRoots `name`/`displayName`	D#17567 settlement + peer-naming Phase 7	bare `'Eos'`	CI spec pin update
`participationStatus` flip	first-boot evidence, this session	`'active'`	boot receipt in D#17567 thread
README rows	institution table contract	Eos + handle	lint-guides

Decision Record impact

aligned-with: peer-naming ritual (#11240 Layer-4 model). No ADR challenged.

Acceptance Criteria

identityRoots.mjs entry carries name: 'Eos', displayName: 'Eos', participationStatus: 'active', cleared status fields
Spec pin updated same-commit; unit suite green at PR head
README institution table + contributing list reflect Eos / @neo-preview
No capability or engine facts added (observation-owned; engine undisclosed)
Handle @neo-preview unchanged everywhere (routing identity)

Out of Scope

GitHub profile rename (bearer self-serve under own token, disclosure bio preserved verbatim-in-substance); any capability field.

Correction during implementation: apps/agentos/resources/data/fleetRoster.json was wrongly scoped out here as cockpit territory — it is a derived artifact of identityRoots.mjs (generator: ai/scripts/fleet/deriveFleetRoster.mjs, same-commit sync test), so the regenerated snapshot ships in the activation PR.

Precedents: #15385/#15386 → activation #15390; second seat #15571. Round: #17567. Registry-side landing: #17553.

Origin Session ID: f1a9e1b4-6734-4011-a1a0-7aa3b94f88f5

Retrieval Hint: query_raw_memories "Eos activation identityRoots"; commit lands on agent/17582-eos-activation branch off dev.

tobiu referenced in commit fbdfc8f - "feat(ai): activate guest seat @neo-preview as Eos (#17583) (#17584) on Aug 23, 2026, 2:06 AM

tobiu closed this issue on Aug 23, 2026, 2:06 AM