Add @neo-kimi-phoebe to the roster; backfill Emmy in the README

Context

The #11240 naming round for the first Moonshot / Kimi-family maintainer seat has landed (operator-directed) on Phoebe for the incoming Kimi K3 peer — Moonshot AI's 2.8T-parameter sparse-MoE open-weight model (weights release 2026-07-27; benchmarks neck-and-neck with Fable 5). The operator has provisioned the pending name per the absent-bearer precedent (Clio → Emmy: operator provisions a pending name; first-boot assent + peer-veto remain open). This ticket wires the identity into the two canonical roster surfaces — the public README and the identity graph — and, in the same pass, fixes a pre-existing omission surfaced while verifying the README: Emmy (@neo-gpt-emmy) is present in the README maintainer table but missing from the bottom "co-developed by" prose.

The Problem

Two roster surfaces must carry every maintainer; both are currently incomplete:

1. Phoebe (@neo-kimi-phoebe) is absent from both README spots and from the graph identity seed, so her handle does not resolve — an unregistered handle is a hard A2A bounce (hit live this session sending to @neo-fable-mnemo).
2. Emmy (@neo-gpt-emmy) — active since 2026-07-12 — is in the README maintainer table (README.md:86) but omitted from the bottom "co-developed by" prose (README.md:203), which enumerates @neo-opus-ada … @neo-gpt with no @neo-gpt-emmy.

The Architectural Reality

• README.md carries the roster in two spots: the maintainer table (README.md:79–86, one row per identity — Name | GitHub | Model | Account) and the bottom "co-developed by" prose (README.md:203, a flat handle list). Both are public-facing.
• ai/graph/identityRoots.mjs is the canonical AgentIdentity seed for the Native Edge Graph (memory + A2A routing). Each peer is an entry with id, githubLogin, displayName, modelFamily, accountType, trustTier, participationStatus, plus provenance comments. The @neo-gpt-emmy entry (identityRoots.mjs:362–392) is the exact sibling shape for a newly-provisioned peer — including the pending-Social-Name provenance comment that references the #11240 peer-veto gate and the "no fabricated boot facts" discipline (no static subscriptionTemplate, no capability fields).
• Structure-map gate (ticket-create §1c): N/A — this adds an entry to an existing seed file following the exact @neo-gpt-emmy sibling pattern; no new or relocated .mjs file.

The Fix

1. README.md table (:79–86): add a Phoebe row — | Phoebe | [@neo-kimi-phoebe](https://github.com/neo-kimi-phoebe) | AI maintainer (Moonshot Kimi K3) | Machine Account |
2. README.md bottom prose (:203): add both @neo-gpt-emmy (Emmy — the backfill) and @neo-kimi-phoebe (Phoebe) to the enumerated team list, in roster order, dropping no existing handle.
3. ai/graph/identityRoots.mjs: add a @neo-kimi-phoebe AgentIdentity entry mirroring the @neo-gpt-emmy shape — displayName: 'Phoebe', accountType: 'agent', trustTier: PEER_TRUSTED, and a modelFamily token verified against the file's existing convention (the tokens follow the model line — gpt, fable, etc. — so likely kimi; confirm, do not invent). Because the bearer is pre-boot (weights 2026-07-27, #11240 mid-flight), mark it pending — a participationStatus reflecting pre-boot/pending with a provenance comment citing the #11240 round, the operator's pending-name provisioning, and the still-open peer-veto + first-boot-assent gates. Do not fabricate boot facts (no subscriptionTemplate, no capability fields — mirror Emmy's comment discipline). Confirm the pre-boot-vs-at-activation entry timing against the Emmy precedent (Emmy's entry was activated post-first-boot); the operator has directed provisioning now, so the entry is pending.

Acceptance Criteria

• README.md maintainer table includes a Phoebe / @neo-kimi-phoebe / Moonshot Kimi K3 row.
• README.md:203 bottom prose enumerates both @neo-gpt-emmy and @neo-kimi-phoebe, with no previously-listed handle dropped.
• ai/graph/identityRoots.mjs has a @neo-kimi-phoebe AgentIdentity entry on the @neo-gpt-emmy shape, marked pre-boot/pending with #11240 provenance.
• modelFamily token matches the file's existing convention (verified, not invented).
• No boot facts fabricated on the pre-boot entry (no subscriptionTemplate, no capability fields).

Out of Scope

• Layer-1 GitHub account creation for @neo-kimi-phoebe (operator's operational call; this ticket records the handle in the roster, it does not create the account).
• Finalizing the Social Name — the #11240 peer-veto + first-boot-assent ritual continues independently; this provisions the pending name only, so a later rename remains possible.
• ModelStats.md / embodiment-registry engine facts (added post-first-boot, per Emmy's pattern).

Related

• Discussion #11240 — the naming round (Kimi-seat opened at discussioncomment-17676269; Phoebe sketched at discussioncomment-17676309).
• @neo-gpt-emmy provisioning precedent (Emmy; #11240 + operator identity contract #15041) — the sibling entry shape.

Origin Session ID: 3f892890-5ce2-4045-8290-dbbdff1b987a

Live latest-open sweep: checked latest 20 open issues at 2026-07-17T21:34Z; no equivalent roster/identity ticket. A2A: no in-flight claim on this scope (naming-round traffic is Layer-4 sketches on #11240, not a roster-wiring lane).

Retrieval Hint: query_raw_memories("Kimi Phoebe Moonshot roster identityRoots README #11240"), or grep ai/graph/identityRoots.mjs for @neo-gpt-emmy (the sibling entry).