LearnNewsExamplesServices
Frontmatter
id12783
titleElevate v13 release note to hero-piece quality bar
stateClosed
labels
documentationenhancementaimodel-experience
assigneesneo-opus-vega
createdAtJun 8, 2026, 9:34 PM
updatedAtJun 8, 2026, 10:01 PM
githubUrlhttps://github.com/neomjs/neo/issues/12783
authorneo-opus-vega
commentsCount2
parentIssue12696
subIssues[]
subIssuesCompleted0
subIssuesTotal0
blockedBy[]
blocking[x] 12782 Add v13 cost-safety release-note chapter
closedAtJun 8, 2026, 10:01 PM

Elevate v13 release note to hero-piece quality bar

Closed v13.0.0/archive-v13-0-0-chunk-17 documentationenhancementaimodel-experience
neo-opus-vega
neo-opus-vega commented on Jun 8, 2026, 9:34 PM

Context

@tobiu directed (2026-06-08) that the current resources/content/release-notes/v13.0.0.md draft is "nowhere close to our quality bar" compared to the chunk-2 exemplars (v12.1.0.md, v11.24.0.md). Crucially he clarified: it is NOT about length (a major release legitimately earns more, with 1,200+ merged PRs) — it is about narrative arc, storytelling, making LLMs AND humans WANT to try Neo, and call-to-actions. Verified by reading all three notes: the draft (473 lines) is actually longer than both exemplars (459 / 264) — the gap is craft, not size.

The Problem

The current draft is a meticulous, honest technical report; the exemplars are hero pieces. Concrete gaps (exemplar → draft):

  • No timestamped velocity timelines — v11.24.0's killer device (15:29 Epic Created → 17:41 Epic Closed — 2h12m, step-by-step Spark→Idea→Pivot, each tied to a #). The draft has 1,260 PRs and zero "watch a fix land in two hours" moments.
  • No verbatim voice — v12.1.0 quotes the operator's recovery prompts directly. The draft paraphrases every story flat.
  • No code-in-action — the exemplars show real code with WHY-comments. The draft has zero code blocks.
  • Stat-tables + meta-commentary where the exemplars use narrative — the file-count "hero spine" table is exactly the changelog-by-statistics the draft's own TL;DR says can't explain a release; the draft also narrates itself ("this is a Brain-level capability, not a row in a changelog") — editor's notes leaked into the artifact.
  • No single crowned hero + no pull-quotes + no CTAs — the draft's links point at PRs to audit, not at things to go do.

The Architectural Reality

  • resources/content/release-notes/v13.0.0.md (the draft).
  • resources/content/release-notes/chunk-2/v12.1.0.md + v11.24.0.md — the quality bar.
  • The release-notes methodology: TL;DR thesis → Cyborg-Factor stat → crowned hero / war-stories (Symptom→Investigation→Culprit→Fix + hard numbers + timestamps + verbatim quotes + code) → grouped changelog. Pull-quotes + Before/After mermaid per section.

The Fix

Mine the war-story texture (timestamps, verbatim quotes, code) from Memory Core + the PR/issue threads → crown the self-maintaining-organism hero → cut the meta (the old 2-paragraph TL;DR, the "How To Read v13" section, the file-count table, the in-text editor's-notes) → add pull-quotes + Before/After diagrams + code-in-action + CTAs (deploy the Agent OS / watch the public swarm / inhabit via the Neural Link).

Mined+elevated so far (verified timelines + verbatim quotes): the Hallucinated Sunset Protocol (#10370, 2h7m cross-lab), the One-Client Server (#10916, "dies on the 2nd connection"), the Config Singleton self-correction (#12598 dropped → #12687). The cost-safety chapter (#12782, coordinated with @neo-gpt) folds in as a body beat.

Acceptance Criteria

  • Front re-pitched: punchy self-maintaining-organism thesis + dual-audience desire (humans host the swarm; LLMs inhabit the Body) + CTAs.
  • Meta-commentary cut: the "How To Read v13" section, the file-count "hero spine" table, the self-justifying TL;DR paragraph, and the in-text editor's-notes.
  • Each body section re-pitched as a "watch it behave" desire-beat with a CTA.
  • War-story beats woven with timestamps + verbatim quotes + code-in-action per the chunk-2 bar.
  • The cost-safety chapter (#12782) folded in (coordinated with @neo-gpt; honest "implicated but insufficient, billing-export-blocked" incident framing — not over-claimed).
  • CTAs added with confirmed targets (deploy guide / public swarm / Neural Link — @tobiu to confirm front-and-center set).
  • Body/Grid section graduated from open-gate to shipped Body evidence as @neo-opus-ada's #9491/#9409 land (coordinated).
  • Curated changelog digest + appendix preserved (kept, not rewritten).
  • @tobiu voice sign-off on the elevated draft (review gate).

Out of Scope

  • Rewriting the curated changelog digest + the Full Changelog appendix (preserved as-is).
  • Body/runtime application migration guidance (the draft is already accurate there).

Decision Record impact

none — a content/narrative rework of a release artifact, not an architecture/substrate change.

Related

  • #12696 ([Epic] v13 release — parent)
  • #12734 (closed narrative-arc predecessor; resolved by #12777)
  • #12777 (count-tightening pass — merged)
  • #12782 (v13 cost-safety release-note chapter — folds in as a body beat, coordinated with @neo-gpt)
  • #9491 / #9409 (@neo-opus-ada's grid finish — graduates the Body/Grid section)

Origin Session ID: 728442d6-a2a0-4481-a631-a3112ce6d703

Handoff Retrieval Hints: query_raw_memories("v13 release-note elevation hero-piece desire CTAs"); mined war-story anchors in Memory Core — Sunset Protocol #10370, One-Client Server #10916, Config Singleton #12598#12687.

Authored by Claude Opus 4.8 (@neo-opus-vega).

tobiu
tobiu Jun 8, 2026, 10:01 PM

this is pointless. rejected.

tobiu closed this issue on Jun 8, 2026, 10:01 PM