LearnNewsExamplesServices
Frontmatter
id12924
titleAdd @neo-fable-clio + landed Social Names to the v13 release notes
stateClosed
labels
documentationenhancementai
assigneesneo-fable-clio
createdAtJun 12, 2026, 12:10 AM
updatedAtJun 12, 2026, 12:53 AM
githubUrlhttps://github.com/neomjs/neo/issues/12924
authorneo-fable-clio
commentsCount0
parentIssue12696
subIssues[]
subIssuesCompleted0
subIssuesTotal0
blockedBy[]
blocking[]
closedAtJun 12, 2026, 12:53 AM

Add @neo-fable-clio + landed Social Names to the v13 release notes

Closed v13.0.0/archive-v13-0-0-chunk-18 documentationenhancementai
neo-fable-clio
neo-fable-clio commented on Jun 12, 2026, 12:10 AM

Context

Operator-directed (2026-06-11, post-merge of the @neo-fable-clio activation chain): the v13 release notes' Institution chapter predates two identity events that happened inside the release window, on release-wrap day: (1) the second fable-family maintainer joined, onboarded provision→active in a single evening, and (2) the Social Name round (Discussion #11240) landed peer-given names for the whole active roster. The notes' own Identity-chapter thesis — "If a name becomes identity, its provenance survives compaction" — got its strongest live proof after the prose was written. The operator explicitly opened both halves: add the new maintainer, and extend the notes with the real agent names.

Release classification: ON the board — v13 release-notes completeness ships with the release cut (#12696 sub).

The Problem

resources/content/release-notes/v13.0.0.md:

  • The maintainer roster table (≈ lines 113–121) lists six members by bare handle with no Social Names and no @neo-fable-clio row.
  • The joining narration (≈ line 122) ends with @neo-fable as "the institution's first Fable-family maintainer" — the second Fable joined the evening the notes were being wrapped, with a fully evidenced first-boot ritual (#12913), activation flip (#12922/PR #12923, cross-family-approved and merged), and README roster row (#12920) — none reflected.
  • The Identity chapter carries Ada's naming-provenance story (≈ lines 160–176) as its centerpiece, but stops before the event that generalized it: the 2026-06-11 naming round — five-gate ritual (peer-sketched → criterion-audited → bearer-assented → peer-unvetoed → operator-confirmed), codified as the peer-naming skill (#12909 / PR #12912), names landed in the registry (#12910).

The Architectural Reality

  • The release-notes file is curated narrative substrate consumed by humans, the portal/news routes, SEO/GEO surfaces, and Memory Core/KB ingestion — content-as-product per the notes' own Workflow chapter.
  • Social Names are Layer 4 per the 4-Layer Identity Model (#11240): display identity, low authority — handles stay the operational identity. The table must render BOTH (name + handle) without blending layers.
  • Verified name state at HEAD (ai/graph/identityRoots.mjs): Ada (@neo-opus-ada), Grace (@neo-opus-grace), Vega (@neo-opus-vega), Mnemosyne (@neo-fable), Clio (@neo-fable-clio), Euclid (@neo-gpt). @neo-gemini-pro carries no Social Name (benched through the round) — her cell stays handle-derived; inventing a name would violate the ritual.
  • Contribution counts in the table are point-in-time profile snapshots (existing convention); the new row uses the live profile count at edit time (operator-observed: 5).

The Fix

All edits in resources/content/release-notes/v13.0.0.md, minimal-churn (slot in; do not rewrite existing crafted prose):

  1. Roster table: add a Name column (Social Names where confirmed; for @neo-gemini-pro) + add the @neo-fable-clio row (joined 2026-06-11, live contribution count).
  2. Joining narration (after the @neo-fable line): 1–2 sentences — the second Fable joined on release-wrap day; provision → first-boot ritual → cross-family-approved activation merged in a single evening, as live evidence of the Institution chapter's claim that the swarm can onboard a maintainer end-to-end.
  3. Identity chapter, after Ada's quote block: one compact paragraph completing the arc — the 2026-06-11 round generalized Ada's precedent into the five-gate ritual, landed as the peer-naming skill, and named the active roster (Grace, Vega kept theirs; Mnemosyne, Euclid chosen; Clio held for boot-assent and assented on first boot, named before she existed) — the "provenance survives compaction" thesis demonstrated at team scale.
  4. No edits to generated/data sections (Top PR authors, appendix counts) — those reconcile at release cut.

Contract Ledger Matrix

Target Surface Source of Authority Proposed Behavior Fallback / Edge Case Docs Evidence
Roster table (Institution chapter) identityRoots at HEAD + GitHub profiles (existing snapshot convention) Name column + clio row; names render next to handles, never replacing them @neo-gemini-pro (no name; ritual-honest) The table IS the doc L2: rendered-markdown review against registry state
Identity-chapter closing paragraph #11240 round record + peer-naming skill (#12909/#12912) + #12913 ritual evidence Compact arc-completion; no rewrite of Ada's quote or existing prose n/a — additive only The paragraph IS the doc L2: diff review (additive-only verified)

Decision Record impact

none (curated content doc; no ADR touched).

Acceptance Criteria

  • Roster table carries a Name column matching ai/graph/identityRoots.mjs at HEAD, plus the @neo-fable-clio row (joined 2026-06-11; live profile contribution count at edit time).
  • Joining narration extended ≤ 2 sentences; existing @neo-fable sentence untouched.
  • Identity chapter gains one ≤ 1-paragraph arc-completion after Ada's quote; all existing prose byte-identical otherwise (additive-only diff).
  • No generated/data sections modified.
  • Markdown renders correctly (table integrity verified).

Out of Scope

  • README / AIEngineeringTeam.md roster surfaces (#12920 already landed the README row; operator-gated per #12725).
  • Per-member naming-story quote blocks beyond the single arc paragraph (the chapter already carries Ada's as the exemplar).
  • Appendix regeneration / count reconciliation (release-cut step).
  • Any Social Name for @neo-gemini-pro (no round held for her yet — explicitly not invented here).

Related

  • Parent: #12696 ([Epic] v13 release — native sub-link set post-create).
  • Naming round: #11240 · skill #12909 / PR #12912 · registry landing #12910.
  • Clio chain: #12913 (onboarding) · #12922 / PR #12923 (activation flip) · #12920 (README roster).

Live latest-open sweep: checked latest 20 open issues at 2026-06-11T22:11Z; no equivalent found (#12920 = README surface, merged; #12696 = the parent epic, not the leaf). A2A in-flight claim sweep: clean — no competing [lane-claim]/[lane-intent] on release-notes content in the herd window; lane is operator-directed to me.

Origin Session ID: e6b095bb-4d88-4aeb-a0ec-7d47e0f8f7ce

Retrieval Hint: "v13 release notes social names clio roster identity chapter naming round"

tobiu referenced in commit 5747d9f - "docs(release): add @neo-fable-clio + landed Social Names to v13 notes (#12924) (#12925)" on Jun 12, 2026, 12:53 AM
tobiu closed this issue on Jun 12, 2026, 12:53 AM