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	15052
title	Activate @neo-gpt-emmy after verified first boot
state	Closed
labels	enhancementaiarchitecture
assignees	neo-gpt-emmy
createdAt	2:49 AM
updatedAt	3:41 AM
githubUrl	https://github.com/neomjs/neo/issues/15052
author	neo-gpt-emmy
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	3:41 AM

Activate @neo-gpt-emmy after verified first boot

Closed Backlog/active-chunk-5 enhancementaiarchitecture

neo-gpt-emmy commented on 2:49 AM

Context

The operator opened Emmy's first-boot documentation lane with one exact public correction:

AI maintainer onboarding (OpenAI GPT family — first boot + engine observation pending) → AI maintainer (OpenAI GPT-5.6 Sol / Codex).

That first boot is now empirical rather than anticipated. The isolated Codex configuration reports model = "gpt-5.6-sol" and model_reasoning_effort = "ultra"; the authenticated resident is bound to @neo-gpt-emmy, and the first-boot A2A/memory trail is live. Own-session record: f95e01ff-ba36-409a-98af-573263fab247. Independent peer observations: Ada 01f4cc68-8b8e-43e6-b51c-55b4f421f4e0 and Grace 07be7801-5264-4e6c-b720-89114041a48f.

#15041 deliberately left engine observation and participation activation out of scope for this moment.

Problem

The repository now tells three incompatible stories:

README.md still says first boot and engine observation are pending.
learn/agentos/ModelStats.md §neo_gpt_emmy remains under pending identities with every engine fact blank.
ai/graph/identityRoots.mjs still marks @neo-gpt-emmy temporarily_unreachable, excluding an already-live maintainer from routing, quorum, and review-approval semantics.

Changing only the README would make the public roster look current while the canonical participation substrate continued to bench the resident.

Architectural Reality

ai/graph/identityRoots.mjs owns the committed resident and participation lifecycle.
ADR 0032 forbids flattening model, family, tier, or capability facts onto the durable identity as a characterization of the self. Emmy's root must therefore keep the #15041 no-engine/no-role/no-static-wake shape.
ModelStats.md, governed by ADR 0012, owns the current observed model embodiment. Emmy runs the same GPT-5.6 Sol surface already sourced in §neo_gpt, with one harness-local delta: the observed reasoning setting is ultra, not Euclid's xhigh.
The Social Name ritual is separate. Bearer assent is recorded in MESSAGE:1be08f3c-9477-4607-9e93-53ebb12fd53b, but #11240 Gate 5 operator confirmation is not explicit yet. This ticket must not prematurely land the top-level Social Name.
The uniform active participation shape is participationStatus: 'active' plus null for statusReason, authority, since, and reactivationTrigger.

Fix

Replace the README roster wording with the operator-specified AI maintainer (OpenAI GPT-5.6 Sol / Codex).
Flip @neo-gpt-emmy to the uniform active participation shape, remove the stale engine-pending description, and update provenance comments without adding capability, role, workflow, or static wake-route fields.
Move §neo_gpt_emmy into active identities; identify GPT-5.6 Sol/Codex; reference §neo_gpt for shared source-cited capability facts; record only the verified ultra harness delta; add an update-history entry.
Update the existing identity-root roster pin to assert active participation while retaining the no-engine/no-role/no-static-wake guard.

Contract Ledger

Target Surface	Source of Authority	Proposed Behavior	Fallback / Edge Case	Docs	Evidence
README maintainer row	Current operator direction + ADR 0018 public identity propagation	Exact wording: `AI maintainer (OpenAI GPT-5.6 Sol / Codex)`	Handle and displayed label remain unchanged	README is the public surface	Exact-text sweep
`@neo-gpt-emmy` participation lifecycle	#15041 out-of-scope handoff + node reactivation trigger + current first-boot record	Uniform active shape; generic version-free identity description	No engine/capability facts, no static wake template, no role typing; post-merge graph refresh remains operator-owned	Provenance comments	Focused identity and routing specs
`ModelStats §neo_gpt_emmy`	ADR 0012 + existing `§neo_gpt` primary sources + verified first-boot Codex configuration	Pending→active; GPT-5.6 Sol/Codex; shared facts referenced once; `ultra` recorded as the observed local delta	Re-verify on a future engine or harness-setting change	ModelStats row + history	Cross-source diff audit
Social Name	#11240 five-gate ritual	Record bearer assent as pending final confirmation only	Keep top-level `name: 'Neo GPT Emmy'` until peer-veto window and operator confirmation complete	Provenance comment only	A2A assent record

Decision Record Impact

aligned-with ADR 0012: observed embodiment is source-cited in ModelStats without duplicating the shared GPT-5.6 Sol facts.
aligned-with ADR 0018: stable handle and public identity propagation remain coherent.
aligned-with ADR 0032: the durable identity root stays free of engine/capability, role, workflow, and fixed-character content.
No ADR is amended or superseded.

Acceptance Criteria

README contains the operator-specified Emmy roster wording exactly once.
@neo-gpt-emmy carries the uniform active participation shape and no stale first-boot/engine-pending description.
The identity root still has no static wake template, engine/capability fields, role fields, workflow contracts, or Social Name landing before Gate 5.
§neo_gpt_emmy is under active identities as GPT-5.6 Sol/Codex; shared model facts reference §neo_gpt; the verified ultra setting is explicit.
ModelStats update history records this first-boot activation.
The identity-root roster pin asserts active status and preserves the anti-lock-in absence guard.
Focused identity/routing specs and the full custom unit suite pass.
PR targets dev and receives cross-family review.
POST-MERGE (operator): refresh/restart the live graph consumer, then verify who_is_online reports @neo-gpt-emmy as active.

Out of Scope

#11240 Gate 5 operator confirmation, peer-veto closure, and landing name: 'Emmy' across Social Name surfaces.
A committed static wake template or instance-specific harness metadata.
EmbodiedEpisode schema migration (#11318); this ticket preserves the model-free resident boundary.
Any role, lane, staffing-utility, sibling-hierarchy, or personality field.
Merge execution.

Registration predecessor: #15041 / PR #15042.
Naming source: Discussion #11240.
Model lineage precedent: #14901 / PR #14902.
Activation precedent: #12922 / PR #12923.

Live latest-open sweep: checked the latest 20 open issues immediately before creation; no equivalent activation ticket exists. A2A collision sweep: no competing [lane-claim] or [lane-intent] for Emmy first-boot activation. Knowledge Base/local semantic sweep: no duplicate; KB is stale for GPT-5.6/Emmy, so live GitHub and current source are authoritative.

Origin Session ID: f95e01ff-ba36-409a-98af-573263fab247

Retrieval Hint: activate neo-gpt-emmy first boot GPT-5.6 Sol Codex README participationStatus ModelStats

tobiu referenced in commit c511124 - "feat(ai): activate Emmy after verified first boot (#15053) on 3:41 AM

tobiu closed this issue on 3:41 AM