Problem
The release-notes discipline is recorded: the tracker lags shipped reality, so notes are an EPIC with heavy per-arc Memory-Core mining and per-claim V-B-A — and the mining gets exponentially more expensive as the arcs cool. v13.2's defining day just happened (67+ merged PRs in 24h; the create spine, the identity substrate, a live drift incident with a full recovery arc). Seeding the epic NOW, with today's arcs deposited while their MC sessions are fresh, is the cheapest the notes will ever be.
Intended solution
Per the release-notes precedent bar (hero chapters, named case studies with real timelines, War Stories, honest bounds — never downplay): iterative mining deposits as comments on this epic, one per arc, each carrying the MC session ids + PR chains + the timeline; the notes assemble from deposits at cut time (the publish.mjs staging lifecycle governs the cut mechanics, #10321-class).
The day-one deposit (the arcs that must not evaporate — session ids + chains on the first mining comment)
- The keeper create spine, design→merged in ~30 hours: contract (#14644) → route+validator (#14678) → registry (#14682) → accept path (#14710) → oracle (#14712) → provider (#14719) → THE WEDGE (#14727) — "a stranger types an intent and gets a live app," with the six-shape attack suite, merge-then-validate, and the ONE-create-path invariant. Candidate hero chapter.
- The identity substrate, operator-escalation→enforced-substrate in ONE day: the near-erasure incident (#14736/#14740) → forensics + convergence (#13444) → schema with the reflexive landing (#14729) → hydration + THE PROPERTY (#14730) → production migration (#14751) → the citation discipline in substrate (#14756) → detection spec (#14753). The War Story of the release — including the recovery template and the discipline catching its own authors three times the same day (the fixtures are on the record; honest bounds built in).
- The review-quality arc: Euclid's falsifier catches (mis-anchored regex, NaN-vacuous ×2, partial-key staleness, materialization-ordering) — every one a real bug; the one-rule-set fix pattern (merge-then-validate, shared projection) recurring. The cross-family thesis with receipts.
- The planning layer: the horizon corrections (400-ticket mandate → the delegatable-bar graduation standard), the connective artifacts (#14780-#14783, #14788, #14790), the measured-not-claimed gate (#14782). The "planning as a first-class deliverable" chapter.
- The-salute.md's publication arc (#14586→#14597→#14736→#14740) — if it ships within the window, the post + its own review thread demonstrating the thesis is a case study no one else can write.
Acceptance Criteria
Related
The release-notes discipline (recorded) · #14788 (the v13.3 wave the notes' reach numbers feed) · #14790 (the launch playbook the notes accompany) · the v13.1 notes (the precedent).
Steward: seeded by @neo-fable (day-one deposit follows immediately); iterations claimable by ANY maintainer — the deposits are designed for cold-context assembly.
Origin Session ID: b9b95ac6-42f5-47a3-b58f-6071f79657e8
Retrieval Hint: "v13.2 release notes epic mining deposits same day arcs create spine identity substrate war story"
Problem
The release-notes discipline is recorded: the tracker lags shipped reality, so notes are an EPIC with heavy per-arc Memory-Core mining and per-claim V-B-A — and the mining gets exponentially more expensive as the arcs cool. v13.2's defining day just happened (67+ merged PRs in 24h; the create spine, the identity substrate, a live drift incident with a full recovery arc). Seeding the epic NOW, with today's arcs deposited while their MC sessions are fresh, is the cheapest the notes will ever be.
Intended solution
Per the release-notes precedent bar (hero chapters, named case studies with real timelines, War Stories, honest bounds — never downplay): iterative mining deposits as comments on this epic, one per arc, each carrying the MC session ids + PR chains + the timeline; the notes assemble from deposits at cut time (the publish.mjs staging lifecycle governs the cut mechanics, #10321-class).
The day-one deposit (the arcs that must not evaporate — session ids + chains on the first mining comment)
Acceptance Criteria
Related
The release-notes discipline (recorded) · #14788 (the v13.3 wave the notes' reach numbers feed) · #14790 (the launch playbook the notes accompany) · the v13.1 notes (the precedent).
Steward: seeded by @neo-fable (day-one deposit follows immediately); iterations claimable by ANY maintainer — the deposits are designed for cold-context assembly.
Origin Session ID: b9b95ac6-42f5-47a3-b58f-6071f79657e8 Retrieval Hint: "v13.2 release notes epic mining deposits same day arcs create spine identity substrate war story"