Register @neo-gpt-emmy in the canonical maintainer roster

Context

The operator created neo-gpt-emmy as a new GPT-family maintainer account. GitHub now exposes the verified profile display label Emmy; unconditional Social Name assent and the live engine designation remain first-boot observations.

The repo already ships the dry-run-first onboarding generator from #14916. This ticket applies and hardens that substrate while correcting an older identity-model mistake: a resident node is not a container for staffing utility, sibling hierarchy, review policy, memory workflow, or onboarding checklists.

The Problem

Until @neo-gpt-emmy is registered, the new resident has no canonical AgentIdentity root, public roster row, pending capability record, or executable roster pin. The first generated draft also copied undocumented identityContract and role-typing fields from older roots, contradicting ADR 0032's identity anti-lock-in contract and the operator precedent in #13165 / #13166.

Architectural Reality

• ai/graph/identityRoots.mjs is the committed AgentIdentity roster and Memory Core boot-time seed source.
• An AgentIdentity records the resident's durable handle, bearer-confirmed Social Name when one exists, verified account/UI label, trust/account classification, current capability facts, operational wake configuration where required, and participation lifecycle.
• Workflow and governance belong to their owning surfaces. identityContract, memoryContinuity, activationPrerequisites, reviewSemantics, sibling hierarchy, and swarmRole are not resident attributes.
• Engine facts are observation-owned. Emmy's model designation and capability fields remain absent until first boot.
• Migration epoch classification is derived from each root's immutable hardcoded createdAt; it needs neither an identity policy field nor a second resident roster.

The Fix

1. Register @neo-gpt-emmy with handle-derived top-level name pending bearer assent, verified profile display label Emmy, core schema-backed fields, non-active onboarding status, no engine prediction, and no static wake template.
2. Synchronize the README roster and ModelStats pending row.
3. Remove undocumented workflow contracts, role typing, staffing-utility prose, and fixed-character narratives from every named maintainer in identityRoots.mjs and the mirrored ModelStats rows.
4. Replace import-time createdAt clocks on every root with immutable introduction timestamps, and make migration compare those facts directly with MIGRATION_EPOCH.
5. Correct the generator/schema/ADR/public-guide surfaces that could recreate role-typed identity or dynamic timestamps, and add executable anti-lock-in guards.

Contract Ledger

Decision Record Impact

Aligns the live registry and ADR 0012 with ADR 0032's newer no-role-typing identity contract. No new identity abstraction is introduced; undocumented nested fields are removed.

Acceptance Criteria

• @neo-gpt-emmy exists exactly once with canonical GitHub login, handle-derived top-level name pending bearer assent, verified display name Emmy, and pending participation state.
• Emmy carries no identityContract, memory/onboarding workflow, sibling hierarchy, swarmRole, engine facts, or static wake template.
• No named maintainer root frames a peer as throughput, pressure, capacity, output, a fixed lane, or a family stereotype.
• All named maintainer display names use a confirmed Social Name or verified account profile label where one exists.
• Every root carries a hardcoded immutable createdAt; re-import/rehydration cannot reset identity age.
• Post-epoch migration behavior remains deterministic without an identity-node policy field or duplicate resident list.
• README, ModelStats, schema, generator, and focused specs remain coherent.
• The focused identity/generator/migration/heartbeat specs pass.
• The PR targets dev and receives cross-family review.

Out of Scope

Codex credentials and first-boot execution; observed engine/capability fill; participation activation; merge execution.

Avoided Traps

• Model family as character or staffing utility — rejected; family is provenance/embodiment metadata, not personality.
• Workflow inside a person node — rejected; onboarding, memory, review, and migration policy stay with their owning substrate.
• Predict the intended engine — rejected; runtime observation owns the episode.
• Copy an older root blindly — rejected; the anti-lock-in spec checks the entire roster.

Related

Parent: #13015 · generator substrate: #14916 · identity anti-lock-in: ADR 0032 · operator precedent: #13165 / #13166 · naming source: Discussion #11240

Origin Session ID: de713f27-0e82-4960-b4c6-f281e0c36449

Retrieval Hint: query_raw_memories("Emmy neo-gpt-emmy identity anti-lock-in no role typing")