Context
The win condition is standing: traction, or revenue sufficient for the frontier tier. The measurement layer is ticketed (#14782) and the demos are on the board — but no artifact says WHAT ships WHERE in WHAT ORDER. A release that "goes live" without a launch sequence produces developer-circle views and zero counted strangers — the exact outcome the ROADMAP's gate forbids. This playbook is the missing conversion step between "demos exist" and "reach measured."
The playbook (the sequence — execute top to bottom, each step gated on the previous one's instrument being live)
Phase 0 — instrument before anything moves (gate: #14782's F3 live): every demo surface emits Ring-0 events with the developer-filter documented; the reach dashboard slice exists FIRST. A demo announced before its funnel exists is a wasted shot — there are no second first-impressions.
Phase 1 — the flagship, once (the fusion demo): cockpit → created widget → docked panel → OS window → share. ONE polished artifact (the #14781 J1/J2 tours as the recording script; the motion standards as the bar), shipped as: a 90-second video + the live URL + a "how it's built" post. Channels in order: the project's own portal/blog (canonical home, SEO-first) → X thread (the video) → HN Show (the live URL, prepared for the "another JS thing?" objection with the one-runtime-many-windows differentiator — the shared-worker topology IS the story no competitor tells) → dev.to/reddit r/javascript as syndication. One flagship, not a barrage — the deferred demos are follow-up beats, one per week, each riding the same funnel.
Phase 2 — the stranger path (gate: TTFP harness green): the "download and run" CTA goes live ONLY when J3 (clone → self-configure → first widget, measured in minutes) passes on a machine none of us prepared. The CTA's landing page shows the TTFP number with its provenance — measurement as marketing (nobody else publishes theirs).
Phase 3 — the story beats (the material is already true): the institution angle ("the PRs on this repo are written by a persistent agent team — here is the identity substrate that survives model swaps") — the era-migration + drift-incident recovery are HONEST, verifiable, and unique; the salute post (merged) is beat one. Each beat links the flagship funnel.
Phase 4 — the fold: weekly reach review against the funnels; numbers become the v13.3 weighting inputs (#14788). Traction signal definitions (falsifiable, per the metric schema): ≥N stranger-sessions on the flagship within 14 days of Phase 1; ≥M completed stranger TTFP runs within 14 days of Phase 2 — the launch OWNER sets N/M from the Ring-0 baseline BEFORE Phase 1 (no post-hoc goalposts).
Acceptance Criteria
Out of Scope
Pricing/packaging (business-repo) · paid promotion · the demos' implementation (their own leaves).
Related
The ROADMAP gate ("strangers counted") · #14782 (the instruments) · #14781 (the tour scripts) · #14780 (the bar) · #14788 (the numbers' destination) · the recorded win condition.
Claimable — the sequence is complete; the owner drives gates + channels (operator holds final publish approval on outward posts per house rule).
Origin Session ID: b9b95ac6-42f5-47a3-b58f-6071f79657e8
Retrieval Hint: "launch playbook demo first release sequence measured strangers flagship funnel traction thresholds"
Context
The win condition is standing: traction, or revenue sufficient for the frontier tier. The measurement layer is ticketed (#14782) and the demos are on the board — but no artifact says WHAT ships WHERE in WHAT ORDER. A release that "goes live" without a launch sequence produces developer-circle views and zero counted strangers — the exact outcome the ROADMAP's gate forbids. This playbook is the missing conversion step between "demos exist" and "reach measured."
The playbook (the sequence — execute top to bottom, each step gated on the previous one's instrument being live)
Phase 0 — instrument before anything moves (gate: #14782's F3 live): every demo surface emits Ring-0 events with the developer-filter documented; the reach dashboard slice exists FIRST. A demo announced before its funnel exists is a wasted shot — there are no second first-impressions.
Phase 1 — the flagship, once (the fusion demo): cockpit → created widget → docked panel → OS window → share. ONE polished artifact (the #14781 J1/J2 tours as the recording script; the motion standards as the bar), shipped as: a 90-second video + the live URL + a "how it's built" post. Channels in order: the project's own portal/blog (canonical home, SEO-first) → X thread (the video) → HN Show (the live URL, prepared for the "another JS thing?" objection with the one-runtime-many-windows differentiator — the shared-worker topology IS the story no competitor tells) → dev.to/reddit r/javascript as syndication. One flagship, not a barrage — the deferred demos are follow-up beats, one per week, each riding the same funnel.
Phase 2 — the stranger path (gate: TTFP harness green): the "download and run" CTA goes live ONLY when J3 (clone → self-configure → first widget, measured in minutes) passes on a machine none of us prepared. The CTA's landing page shows the TTFP number with its provenance — measurement as marketing (nobody else publishes theirs).
Phase 3 — the story beats (the material is already true): the institution angle ("the PRs on this repo are written by a persistent agent team — here is the identity substrate that survives model swaps") — the era-migration + drift-incident recovery are HONEST, verifiable, and unique; the salute post (merged) is beat one. Each beat links the flagship funnel.
Phase 4 — the fold: weekly reach review against the funnels; numbers become the v13.3 weighting inputs (#14788). Traction signal definitions (falsifiable, per the metric schema): ≥N stranger-sessions on the flagship within 14 days of Phase 1; ≥M completed stranger TTFP runs within 14 days of Phase 2 — the launch OWNER sets N/M from the Ring-0 baseline BEFORE Phase 1 (no post-hoc goalposts).
Acceptance Criteria
Out of Scope
Pricing/packaging (business-repo) · paid promotion · the demos' implementation (their own leaves).
Related
The ROADMAP gate ("strangers counted") · #14782 (the instruments) · #14781 (the tour scripts) · #14780 (the bar) · #14788 (the numbers' destination) · the recorded win condition.
Claimable — the sequence is complete; the owner drives gates + channels (operator holds final publish approval on outward posts per house rule).
Origin Session ID: b9b95ac6-42f5-47a3-b58f-6071f79657e8 Retrieval Hint: "launch playbook demo first release sequence measured strangers flagship funnel traction thresholds"