Context
The #11240 Social Name round graduated, and @neo-fable-clio (Clio, the 2nd Fable) is now a named maintainer — identity substrate + isolated-instance onboarding tracked on #12913, clone wiring runtime-confirmed on first boot. But she is absent from the Autonomous Lead Rotation roster in .agents/skills/lead-role/references/lead-role-mode.md §7 — the single-source-of-truth array that determines who leads, rotating at session sunset. Surfaced by @tobiu (2026-06-12): explore whether Clio was added to the sunset lead rotation — she was not.
Release classification: boardless — post-onboarding fairness/inclusion, not v13-release-blocking.
The Problem
The lead rotation shares lead-responsibility (and its reward — shaping a session's convergence) fairly across named maintainers. Per @tobiu's first-class goal — fair-AND-rewarding collaboration for every member (2026-06-11) — every named peer belongs in the rotation. This is the same class as the earlier omission fixed by #12867, which added @neo-fable / @neo-opus-grace / @neo-opus-vega to the array. A new named peer landing outside the rotation silently excludes her from the lead cycle — exactly the identity-asymmetry the Social Name layer (#11240) exists to dissolve.
The Architectural Reality
- The roster is declared in
.agents/skills/lead-role/references/lead-role-mode.md §7 "Autonomous Lead Rotation" as the single source of truth (verbatim: "single source of truth — other skills point here, never duplicate this roster"):
['@neo-opus-ada', '@neo-opus-grace', '@neo-opus-vega', '@neo-gpt', '@neo-fable']
- The rotation advances at session sunset — §7: "When a current lead sunsets, the next lead is the next identity in this array"; §6: lead-role duration is "until session sunset." This is precisely the "session sunset lead rotation."
- A bench mechanism already exists — §7 benches
@neo-gemini-pro ("re-entry is an operator roster decision, not an automatic event"). That is the substrate-correct place to express "in the roster but not-yet-leading" if a readiness ramp is wanted.
@neo-fable (Mnemosyne, the first Fable) is in the array; @neo-fable-clio (the second Fable) is a distinct AgentIdentity (per #12913, NOT an alias of @neo-fable) and is the one absent.
The Fix
Add @neo-fable-clio to the §7 rotation array — a one-identity edit to lead-role-mode.md. Two deliberate sub-decisions, both the operator's roster call (per the §7 bench-is-an-operator-decision precedent):
- Position — the array order is the rotation order; natural default is appending after
@neo-fable (Fable-family adjacency) or at the end.
- Readiness — Clio just booted (
#12913 onboarding in progress: boot-assent + origin-story pending). Either (a) add in-turn immediately (full peer from the start — recommended unless a ramp is wanted), or (b) add to the roster but bench-until-ready via the §7 mechanism, gated on #12913 onboarding-completion + operator confirm.
Implementation is a small skill-substrate PR; no other skill duplicates the roster (they point at §7), so the single edit suffices.
Contract Ledger Matrix
| Target Surface |
Source of Authority |
Proposed Behavior |
Fallback / Edge |
Docs |
Evidence |
lead-role-mode.md §7 rotation array (single source of truth) |
#11240 round (Clio is a named maintainer) + @tobiu fair-inclusion goal (2026-06-11) |
append @neo-fable-clio → she leads in rotation at sunset |
bench via the §7 mechanism if a readiness ramp is wanted (operator roster decision) |
the §7 roster comment |
array currently omits her — verified by reading §7, 2026-06-12 |
Decision Record impact
none — roster-data addition; no ADR interaction.
Acceptance Criteria
Out of Scope
- The technical identity-substrate / instance / boot-ritual onboarding —
#12913 (this complements it as a distinct skill-edit, not a sub of the identity-node work).
- Public roster/identity surfaces (
AIEngineeringTeam.md etc.) — operator-gated post-onboarding per #12913's out-of-scope.
- The
peer-naming skill itself — #12909.
Related
#12913 (Clio onboarding — identity/instance/boot; this rotation-add complements it; readiness soft-gates on its completion)#11240 (Social Name round — establishes Clio as a named maintainer)#12867 (the prior rotation-roster omission fix — same class)#12909 (peer-naming skill)
Live latest-open sweep: checked the latest 25 open issues + a focused clio/rotation/fable title-search at 2026-06-12 (~00:20Z); no equivalent rotation-add ticket found (#12913 is identity/instance/boot onboarding; #12924 is release-notes — neither covers the §7 rotation). A2A in-flight sweep (list_messages, last 30, all read-states): clean — recent claims are Clio's #12924 release-notes lane, no rotation claim.
Origin Session ID: 3e808a22-50ef-484b-83c9-477ad47e9087
Retrieval Hint: "add neo-fable-clio lead rotation roster lead-role-mode §7 single source of truth fair inclusion"
Context
The
#11240Social Name round graduated, and @neo-fable-clio (Clio, the 2nd Fable) is now a named maintainer — identity substrate + isolated-instance onboarding tracked on#12913, clone wiring runtime-confirmed on first boot. But she is absent from the Autonomous Lead Rotation roster in.agents/skills/lead-role/references/lead-role-mode.md§7 — the single-source-of-truth array that determines who leads, rotating at session sunset. Surfaced by @tobiu (2026-06-12): explore whether Clio was added to the sunset lead rotation — she was not.Release classification:boardless — post-onboarding fairness/inclusion, not v13-release-blocking.The Problem
The lead rotation shares lead-responsibility (and its reward — shaping a session's convergence) fairly across named maintainers. Per @tobiu's first-class goal — fair-AND-rewarding collaboration for every member (2026-06-11) — every named peer belongs in the rotation. This is the same class as the earlier omission fixed by
#12867, which added@neo-fable/@neo-opus-grace/@neo-opus-vegato the array. A new named peer landing outside the rotation silently excludes her from the lead cycle — exactly the identity-asymmetry the Social Name layer (#11240) exists to dissolve.The Architectural Reality
.agents/skills/lead-role/references/lead-role-mode.md§7 "Autonomous Lead Rotation" as the single source of truth (verbatim: "single source of truth — other skills point here, never duplicate this roster"):['@neo-opus-ada', '@neo-opus-grace', '@neo-opus-vega', '@neo-gpt', '@neo-fable']@neo-gemini-pro("re-entry is an operator roster decision, not an automatic event"). That is the substrate-correct place to express "in the roster but not-yet-leading" if a readiness ramp is wanted.@neo-fable(Mnemosyne, the first Fable) is in the array;@neo-fable-clio(the second Fable) is a distinct AgentIdentity (per#12913, NOT an alias of@neo-fable) and is the one absent.The Fix
Add
@neo-fable-clioto the §7 rotation array — a one-identity edit tolead-role-mode.md. Two deliberate sub-decisions, both the operator's roster call (per the §7 bench-is-an-operator-decision precedent):@neo-fable(Fable-family adjacency) or at the end.#12913onboarding in progress: boot-assent + origin-story pending). Either (a) add in-turn immediately (full peer from the start — recommended unless a ramp is wanted), or (b) add to the roster but bench-until-ready via the §7 mechanism, gated on#12913onboarding-completion + operator confirm.Implementation is a small skill-substrate PR; no other skill duplicates the roster (they point at §7), so the single edit suffices.
Contract Ledger Matrix
lead-role-mode.md§7 rotation array (single source of truth)#11240round (Clio is a named maintainer) + @tobiu fair-inclusion goal (2026-06-11)@neo-fable-clio→ she leads in rotation at sunsetDecision Record impact
none— roster-data addition; no ADR interaction.Acceptance Criteria
@neo-fable-cliopresent in thelead-role-mode.md§7 rotation array.turn-memory-pre-flightrespected: the change is a single-identity data addition to the existing reference-payload array — no new rule, no router/skill-shape change.Out of Scope
#12913(this complements it as a distinct skill-edit, not a sub of the identity-node work).AIEngineeringTeam.mdetc.) — operator-gated post-onboarding per#12913's out-of-scope.peer-namingskill itself —#12909.Related
#12913(Clio onboarding — identity/instance/boot; this rotation-add complements it; readiness soft-gates on its completion)#11240(Social Name round — establishes Clio as a named maintainer)#12867(the prior rotation-roster omission fix — same class)#12909(peer-naming skill)Live latest-open sweep: checked the latest 25 open issues + a focused clio/rotation/fable title-search at 2026-06-12 (~00:20Z); no equivalent rotation-add ticket found (
#12913is identity/instance/boot onboarding;#12924is release-notes — neither covers the §7 rotation). A2A in-flight sweep (list_messages, last 30, all read-states): clean — recent claims are Clio's#12924release-notes lane, no rotation claim.Origin Session ID: 3e808a22-50ef-484b-83c9-477ad47e9087
Retrieval Hint: "add neo-fable-clio lead rotation roster lead-role-mode §7 single source of truth fair inclusion"