launch: tracking issue + playbook for the patina launch sequence (KO community → Show HN → PH → Reddit/X)

[devswha]

Why it matters

A coordinated launch beats scattered posts. This is the umbrella tracking issue: sequence, per-channel copy, prerequisites, scoring proof, and post-launch feedback capture in one place.

✅ Decided plan (locked 2026-05-29)

The original 2026-05-26 KR date slipped; re-anchored after a launch-readiness audit. Strategy is concentrate-don't-sequence (per .omc/research/star-growth.md): a low-key Korean warmup, then a single simultaneous global spike that can trigger GitHub Trending.

• Phase 1 — KR soft pre-launch: Mon 2026-06-01 (~10:00 KST). GeekNews Show section first, then Velog, then Clien. This is the homeground warmup + the wedge (Korean AI-tell detection), and seeds real users whose comments validate the tool when the global crowd arrives.
• Phase 2 — Global 48h concentrated push: Tue 2026-06-02. Fire Show HN + Product Hunt + Reddit + X/Threads/LinkedIn together, not spread across days. (HN/PH proven window 08:00 ET = 21:00 KST; PH live 00:01 PT = 16:01 KST — a Korea overnight shift.)

Friday/weekend launches were avoided (HN/PH traffic cliff). Tue 6/2 keeps the 72-hour momentum window inside weekdays (Wed–Fri).

Copy source of truth

Finalized launch copy lives in docs/social/patina-launch-copy.md, with supporting top-of-funnel guides in:

• docs/social/signs-of-ai-writing.md
• docs/social/signs-of-ai-writing_KR.md
• docs/social/share-card.md

Paste-ready per-channel kits (gitignored): .omc/research/{geeknews,korea,global}-launch-kit.md, reddit-launch-package.md.

Copy blockers — fixed (2026-05-29)

• Show HN title was 82 chars (HN limit 80) → now the rewrite framing, 77 chars: Show HN: Patina – rewrite AI text patterns in Korean/English/Chinese/Japanese (docs: CHANGELOG Unreleased section + clear two launch-copy blockers #317, trimmed in docs: trim Show HN title to 77 chars for headroom #329). "rewrite" reads as editing, not detection — fits HN's anti-detector crowd.
• Install reply led with curl … | bash → now leads with npx patina-cli, one-liner kept as a "review the script first" secondary option (docs: CHANGELOG Unreleased section + clear two launch-copy blockers #317).

Sequence detail

1. Korean communities (GeekNews → Velog → Clien) — angle: "한국어 AI 티 제거" + auditable editing. (Phase 1, soft.)
2. Show HN — local, auditable, benchmarked cleanup + playground link + "free via local codex/claude/gemini CLI, no API key." (Phase 2.)
3. Product Hunt — visual-led: brand kit + playground + share card; maker comment within 1 min of going live. (Phase 2.)
4. Reddit — per reddit-launch-package.md (🟢 GO): r/LocalLLaMA (local/no-key), r/SideProject (safest), r/opensource (MIT). Skip r/writing and r/Korean (anti-AI-tool / wrong audience). Stagger one sub at a time. (Phase 2.)
5. X / Threads / LinkedIn — reuse short-form drafts, link the playground first. (Phase 2.)

Prerequisites

• Web playground live (distribution: web playground at patina.vibetip.help (audit-only ESM v1) #208) — production URL: https://patina.vibetip.help/
• README score badge (viral: README "patina score" badge (shields.io endpoint) for adopting repos #282).
• Shareable card generator (viral: shareable before/after + score card image generator (OG-style) #283).
• Educational guide (viral(content): "signs of AI writing" shareable guide (KO + EN) from the pattern catalog #285) — top-of-funnel content.
• npm publish (distribution: publish patina-cli (and patina-humanizer alias) on npm with release workflow #203) — verified live: npm view patina-cli version → 3.11.0.
• Action v1 (integration: ship devswha/patina-action@v1 GitHub Action for PR-comment scoring #204) — devswha/patina-action@v1 referenced in docs.
• Comparison page (docs: comparison page vs Quillbot / Undetectable.ai / Humbot / blader/humanizer #213) — cite only factual comparisons.
• Ethics framing (ethics: publish a use-case position statement (what patina is and is not for) #164, docs/ETHICS.md) — position as audit/editing, never detector-evasion.

Latest score proof

Checked on 2026-05-29 (gate <= 30%):

node scripts/precommit-score.mjs docs/social/patina-launch-copy.md docs/social/signs-of-ai-writing.md docs/social/signs-of-ai-writing_KR.md

file	score	status
docs/social/patina-launch-copy.md	6.3%	pass
docs/social/signs-of-ai-writing.md	0.0%	pass
docs/social/signs-of-ai-writing_KR.md	20.0%	pass

Launch execution checklist

Phase 1 — KR soft (Mon 6/1):

• GeekNews Show posted + scored + URL logged.
• Velog posted + URL logged.
• Clien posted + URL logged.

Phase 2 — Global 48h push (Tue 6/2):

• Show HN posted/scored.
• Product Hunt submitted with visual assets + maker comment.
• Reddit posts published (r/LocalLLaMA, r/SideProject, r/opensource).
• X / Threads / LinkedIn posts published.

Throughout:

• False-positive reports collected into follow-up issues or a triage list.

Non-negotiable rules

1. Score every final piece of copy before posting and keep the score proof attached in the launch thread. Target <= 30.
2. Lead with the writing/editing problem. Mention patina after the reader recognizes the problem.
3. Do not use "bypass," "undetectable," or "beats detectors."
4. Avoid hype vocabulary, emoji-bullet stacks, and tidy three-item slogans.
5. Link the playground from every broad-launch post: https://patina.vibetip.help/

Acceptance criteria

• Each channel post drafted in docs/social/, scored (<= 30), and posted or explicitly deferred.
• Phase 1 then Phase 2 completed in order; Phase 2 channels fired together within the 48h window.
• Playground linked from every broad-launch post.
• Post-launch false-positive reports captured with enough context to reproduce the misfire.

[devswha]

Launch playbook/copy source is now tracked via PR #298:

• docs/social/patina-launch-copy.md now includes launch order, prerequisite/blocker table, score gate, channel drafts, assets, reply templates, and post-launch triage rules.
• Latest checked score for the launch copy source: 14.3% with node scripts/precommit-score.mjs docs/social/patina-launch-copy.md.
• viral: README "patina score" badge (shields.io endpoint) for adopting repos #282 is done via PR feat: add patina score badge endpoint #297, with companion devswha/patina-action#1 for badge-json / badge-branch.

Keeping this issue open as the launch execution tracker. Broad launch is still blocked on #208 unless we explicitly waive the playground dependency; #283 and #285 remain useful launch-support follow-ups.

[devswha]

Wave 2 launch-support update:

• viral(content): "signs of AI writing" shareable guide (KO + EN) from the pattern catalog #285 is closed via PR docs: add shareable signs of AI writing guides #299 (shareable signs-of-AI-writing guides).
• viral: shareable before/after + score card image generator (OG-style) #283 is closed via PR feat: add share-card SVG output #300 (--card 1200×630 SVG before/after cards with AI score + MPS).
• Launch-support medium items are now cleared; the remaining broad-launch blocker is distribution: web playground at patina.vibetip.help (audit-only ESM v1) #208 unless the playground dependency is explicitly waived.

Roadmap/memory snapshots were updated to 14 open issues: high=1, medium=3, low=10.

[devswha]

Launch blocker update: #208 is now closed and deployed.

• Try-it-now URL: https://patina.vibetip.help/
• PR distribution: add audit-only web playground #301 added the audit-only static playground.
• PR ops: fix playground root route #302 fixed the root route after live curl caught a / 404.
• Live smoke: /, /app.js, /data/lexicons.js, and /assets/social/patina-og.svg all return HTTP 200.

Remaining launch tracker work should now be final copy scoring / channel-specific posting, not playground infrastructure.

[devswha]

Tracker refreshed.

• Completed prerequisite checkboxes for distribution: web playground at patina.vibetip.help (audit-only ESM v1) #208, viral: README "patina score" badge (shields.io endpoint) for adopting repos #282, viral: shareable before/after + score card image generator (OG-style) #283, and viral(content): "signs of AI writing" shareable guide (KO + EN) from the pattern catalog #285.
• Updated the copy source of truth to docs/social/patina-launch-copy.md instead of the old gitignored .omc note.
• Added latest score proof: launch copy 14.3%, EN guide 14.3%, KR guide 28.6% — all under the 30% gate.
• Added the remaining launch execution checklist by channel.

Next operational step: Korean-first posting pass, then Show HN / Product Hunt / Reddit-X sequence.

[devswha]

Operational follow-up pushed in 5eae5fa.

Launch execution is now ready for maintainer-owned posting:

• Korean-first channel drafts: docs/social/patina-launch-korean-first.md
• General launch copy: docs/social/patina-launch-copy.md
• Playground URL in every draft: https://patina.vibetip.help/
• Latest local prose gates:
  • Korean-first drafts: 17.4%
  • General launch copy: 13.8%

No external/community post was made by the agent. Next action is to copy the exact channel draft, re-score after any edits, then capture false-positive reports with language/register/score output and the fired paragraph.

[devswha]

Final execution checklist after 741f33d.

Current state:

• Playground is live: https://patina.vibetip.help/
• Korean-first drafts: docs/social/patina-launch-korean-first.md
• General launch copy: docs/social/patina-launch-copy.md
• False-positive intake form: https://github.com/devswha/patina/issues/new?template=false_positive.yml
• Latest local prose gates:
  • docs/social/patina-launch-korean-first.md: 17.4%
  • docs/social/patina-launch-copy.md: 13.8%
  • Target remains <= 30%

Before each channel post:

1. Copy the matching draft, then make only channel-specific edits.
2. Re-score the exact final text before posting.
3. Keep the playground link in the post.
4. Keep the false-positive form link in Korean-first posts where it fits.
5. Do not use "bypass", "undetectable", "beats detectors", or authorship-proof wording.
6. Attach the final score output back to this issue.

After each channel post, add a comment here with:

• channel name
• public URL, or "deferred" with reason
• exact score output
• any copy changes from the checked-in draft
• false-positive reports or useful feedback captured

Recommended close condition for this tracker:

• each listed channel is either posted or explicitly deferred;
• every posted copy has a saved score proof;
• playground link appears in every broad-launch post;
• at least one feedback/false-positive triage path is linked from the launch thread.

No external/community post has been made by the agent; posting remains maintainer-owned.

[devswha]

Reopened: the roadmap commit used the phrase "Close #286" inside a rejected-alternative note, which GitHub interpreted as a smart-close. This tracker should remain open until the launch posts are either published or explicitly deferred with score evidence.

[devswha]

Wave ledger/status sync landed on main.

Current state:

• Latest main: 51e8903 (ledger sync) after implementation commit 83675bc.
• GitHub Actions run 26225709876 succeeded.
• docs/ISSUE-WAVES.md now tracks the remaining open work as Wave A/B/C/D.
• Launch service runbook in docs/integrations/playground.md includes the Vercel alias smoke for https://patina.vibetip.help/ plus latest.json/analyzer.js parity checks.
• profiles: add NamuWiki (나무위키) tone profile — ko-scoped, license-safe #304 is closed; the remaining launch action here is still maintainer-owned posting/feedback capture, not agent-owned account posting.

No new public model-performance claims were added; corpus-gated claims remain blocked behind #155/#160/#303.