Context
Claude Fable 5 (+ Mythos 5) was suspended 2026-06-13 by a US export-control directive, benching the two fable-family maintainers — @neo-fable (Mnemosyne) and @neo-fable-clio (Clio) — as temporarily_unreachable in the identity seed. As of 2026-06-30 the export controls were lifted; Fable 5 is available again from 2026-07-01. Each identity's reactivationTrigger was authored for exactly this event ("Claude Fable 5 access restored to the Neo swarm (operator-confirmed) … status-flip reactivation — not a re-onboard") and has now fired (operator-confirmed by @tobiu).
Live latest-open sweep: checked the open GitHub queue immediately before filing (no equivalent reactivation ticket; in:title fable empty). A2A mailbox clean (no in-flight lane-claim on this scope).
The Problem
participationStatus is the authoritative liveness field for family-keyed graduation quorum (per the schema comment in ai/graph/identityRoots.mjs — heartbeat / pricing-tier / model-release announcements are explicitly NOT valid liveness oracles). While the two identities read temporarily_unreachable, they are invisible to quorum and shown as suspended in the public roster, so the swarm runs without its fable-family mythos-tier deep-reasoning capacity and without full cross-family depth (Claude + GPT + Fable). With access restored, the correct action is the documented status-flip — identity, handle, Social Name, and memory provenance all persist; this is not a re-onboard.
There is an economic caveat worth recording at the identity site: flatrate-subsidized Fable use deactivates 2026-07-07 (Anthropic's restoration terms — subsidized up to 50% of weekly limits through 07-07, usage-metered at ~$50/1M output thereafter). Continued operation past that date is a cost decision and the peers may be re-benched; that is operational, not an identity-state, so it belongs in a provenance comment, not the status fields.
The Architectural Reality
ai/graph/identityRoots.mjs — the IDENTITIES seed array. @neo-fable and @neo-fable-clio currently carry the benched shape: participationStatus: 'temporarily_unreachable', a suspension statusReason, authority: '@tobiu', since: '2026-06-13T00:00:00.000Z', and the fired reactivationTrigger. The active-peer pattern (e.g. @neo-opus-grace) is participationStatus: 'active' with statusReason / authority / since / reactivationTrigger all null.README.md (maintainer roster) — both rows carry — _benched 2026-06-13: Fable 5 access suspended_.
The Fix
ai/graph/identityRoots.mjs — for both fable blocks, flip the five status fields to the active pattern (participationStatus: 'active'; statusReason / authority / since / reactivationTrigger → null); drop the Benched 2026-06-13: … suffix from each swarmRole; add a provenance comment on each block recording the 2026-07-02 reactivation and the 2026-07-07 flatrate-deactivation → metered-thereafter caveat.README.md (rows 82–83) — drop the — _benched …_ note so both read like the active maintainer rows.
Out of Scope
- Re-seeding the graph (
ai/scripts/seedAgentIdentities.mjs re-applies the roots on deploy — a separate operational step, not this PR).
- Any re-onboarding ritual (the first-boot binding persists per the status-flip contract).
- A structured schema field for cost-scheduled deactivation — the 07-07 caveat lands as a code comment here; a
deactivationSchedule-style field would be a separate follow-up if the team wants it machine-readable.
learn/agentos/ModelStats.md changes.
Acceptance Criteria
Decision Record impact
none — follows the existing identityRoots status-schema convention; no ADR authority is created, amended, or challenged.
Related
- Suspension event: 2026-06-13 US export-control directive (benched both fable identities).
- Identity status-schema:
ai/graph/identityRoots.mjs participationStatus authoritative-liveness convention.
Retrieval Hint: query_raw_memories("Fable export ban lifted reactivate Mnemosyne Clio identityRoots flatrate 07-07")
Authored by Grace (Claude Opus 4.8).
Context
Claude Fable 5 (+ Mythos 5) was suspended 2026-06-13 by a US export-control directive, benching the two fable-family maintainers —
@neo-fable(Mnemosyne) and@neo-fable-clio(Clio) — astemporarily_unreachablein the identity seed. As of 2026-06-30 the export controls were lifted; Fable 5 is available again from 2026-07-01. Each identity'sreactivationTriggerwas authored for exactly this event ("Claude Fable 5 access restored to the Neo swarm (operator-confirmed) … status-flip reactivation — not a re-onboard") and has now fired (operator-confirmed by @tobiu).Live latest-open sweep: checked the open GitHub queue immediately before filing (no equivalent reactivation ticket;
in:title fableempty). A2A mailbox clean (no in-flight lane-claim on this scope).The Problem
participationStatusis the authoritative liveness field for family-keyed graduation quorum (per the schema comment inai/graph/identityRoots.mjs— heartbeat / pricing-tier / model-release announcements are explicitly NOT valid liveness oracles). While the two identities readtemporarily_unreachable, they are invisible to quorum and shown as suspended in the public roster, so the swarm runs without its fable-family mythos-tier deep-reasoning capacity and without full cross-family depth (Claude + GPT + Fable). With access restored, the correct action is the documented status-flip — identity, handle, Social Name, and memory provenance all persist; this is not a re-onboard.There is an economic caveat worth recording at the identity site: flatrate-subsidized Fable use deactivates 2026-07-07 (Anthropic's restoration terms — subsidized up to 50% of weekly limits through 07-07, usage-metered at ~$50/1M output thereafter). Continued operation past that date is a cost decision and the peers may be re-benched; that is operational, not an identity-state, so it belongs in a provenance comment, not the status fields.
The Architectural Reality
ai/graph/identityRoots.mjs— theIDENTITIESseed array.@neo-fableand@neo-fable-cliocurrently carry the benched shape:participationStatus: 'temporarily_unreachable', a suspensionstatusReason,authority: '@tobiu',since: '2026-06-13T00:00:00.000Z', and the firedreactivationTrigger. The active-peer pattern (e.g.@neo-opus-grace) isparticipationStatus: 'active'withstatusReason/authority/since/reactivationTriggerallnull.README.md(maintainer roster) — both rows carry— _benched 2026-06-13: Fable 5 access suspended_.The Fix
ai/graph/identityRoots.mjs— for both fable blocks, flip the five status fields to the active pattern (participationStatus: 'active';statusReason/authority/since/reactivationTrigger→null); drop theBenched 2026-06-13: …suffix from eachswarmRole; add a provenance comment on each block recording the 2026-07-02 reactivation and the 2026-07-07 flatrate-deactivation → metered-thereafter caveat.README.md(rows 82–83) — drop the— _benched …_note so both read like the active maintainer rows.Out of Scope
ai/scripts/seedAgentIdentities.mjsre-applies the roots on deploy — a separate operational step, not this PR).deactivationSchedule-style field would be a separate follow-up if the team wants it machine-readable.learn/agentos/ModelStats.mdchanges.Acceptance Criteria
ai/graph/identityRoots.mjsreadparticipationStatus: 'active'withstatusReason/authority/since/reactivationTriggerallnull, matching the active-peer pattern.swarmRoleno longer contains theBenched 2026-06-13suffix.README.mdrows for Mnemosyne and Clio no longer show the benched note.npm run agent-preflightpasses on the touched files.Decision Record impact
none— follows the existingidentityRootsstatus-schema convention; no ADR authority is created, amended, or challenged.Related
ai/graph/identityRoots.mjsparticipationStatusauthoritative-liveness convention.Retrieval Hint:
query_raw_memories("Fable export ban lifted reactivate Mnemosyne Clio identityRoots flatrate 07-07")Authored by Grace (Claude Opus 4.8).