Add Silphe GTM: Show HN draft, publicity plan, launch sequence (Closes #10)

docs/0006-gtm.md

@@ -0,0 +1,114 @@
+# 0006 — Silphe GTM: launch & publicity
+
+Actionable launch plan. Builds on `0001-launch-plan.md` (positioning, channels,
+support inboxes, the two-sided story).
+
+> ## ⚠️ The wall — read before publishing anything
+> The **public** story is the toy/instrument only: capture, the games, the
+> visualization, the arc. The **clinical applications and patent filings**
+> described in `0001-launch-plan.md` are **IP** and must never appear in public
+> collateral, the Show HN, comments, or replies.
+>
+> **This doc and `0001-launch-plan.md` both describe the wall and therefore must
+> NOT ship in the public repo.** Before flipping the repo public (step 3 below),
+> move these planning docs to a private location or delete them — and audit the
+> rest of `docs/` and the git history for any IP / patent / clinical reference.
+> If asked publicly "what's it for, medically?" → keep it at the level of the
+> public science ("movement changes with fatigue and the like — that's why it's
+> local-first") and do not tease the productized applications.
+
+## Positioning
+
+One line: **"Everyone's cloning voices; nobody's cloning movement."** Silphe is a
+fun, local, privacy-first desktop toy that learns your pointer signature — and an
+honest longitudinal instrument for how it drifts.
+
+Three audiences, three hooks:
+
+- **Hacker News / makers** — "I built a game that learns how you move the mouse,
+  and watches it drift when you're tired." Local-first; pure-stdlib; the
+  predictive-vs-reactive split.
+- **Python developers (the PyPI niche)** — `pip install silphe`: a clean, typed,
+  cross-platform human-cursor *model* + movement-*analysis* library. This is the
+  "human cursor" search audience (pyclick / ghost-cursor): automation that needs
+  natural movement, plus HCI research.
+- **HCI / accessibility / quantified-self** — Fitts's law, smooth-pursuit lag,
+  tremor as a device-labeled variable, and the speed-vs-learned-the-board
+  question.
+
+## Launch sequence (in order)
+
+1. **Reserve the name** — publish `silphe 0.1.0` to PyPI (#1).
+2. **Land the OIDC release workflow** (#6) so future releases are tag-push.
+3. **Flip the repo public** (currently private). Pre-public gate: remove/relocate
+   the wall-bearing planning docs (this file + `0001`), and verify no
+   `recordings/`, no PII, and no IP references anywhere in tree or history.
+4. **Deploy** the landing + privacy pages to Cloudflare Pages at
+   `thrivetech.ai/silphe` (#8).
+5. **Provision support inboxes** — `privacy@` is *required* by the privacy page;
+   also `hello@ / support@ / security@ / press@`.
+6. **Capture** an `og.png` social card + a short GIF (the Andvari hunt and the
+   arc view) — the scroll-stopper for HN/social.
+7. **Post Show HN** and be at the keyboard for the first 2–3 hours to reply.
+
+## Show HN draft
+
+**Title candidates** (HN rewards plain + specific):
+- *Show HN: Silphe – a local desktop game that learns how you move the mouse*
+- *Show HN: I measured my own mouse-movement signature (and watched it drift)*
+- *Show HN: Silphe – your pointer has a signature; this captures it, locally*
+
+**Body:**
+
+> Silphe is a tiny desktop game that records how *you* move a pointer — not
+> whether you hit the target, but how you miss it on the way there: the
+> overshoot, the corrective sub-movements, the tremor while you hold, the lag
+> while you chase.
+>
+> It started as a mouse-calibration chore and turned into something I couldn't
+> stop poking at. Two things surprised me:
+>
+> - **Predictive vs. reactive tracking are cleanly separable.** Following a
+>   smooth, predictable dot, my lag was ~7 ms — I was *predicting* it. Chasing an
+>   evasive target, it jumped to ~230 ms — pure reaction time. Same hand, same
+>   session.
+> - **The input device is a variable.** A mouse's mass low-pass-filters your
+>   physiological tremor; a trackpad reveals far more of it.
+>
+> It's fully local — no cloud, no telemetry, no account, no network calls. Your
+> movement is biometric data and it stays on your machine. It's also a Python
+> library (`pip install silphe`, Apache-2.0, pure stdlib): a cross-platform
+> human-cursor *model* and a movement-*analysis* toolkit (Fitts fit, tremor
+> frequency, tracking lag/offset).
+>
+> The question I'm chasing now: when your scores improve, are you genuinely
+> *faster*, or have you just *learned the board* — strategy compensating for
+> reaction time that hasn't actually moved?
+>
+> GitHub: … · `pip install silphe`
+
+*(Show HN comment discipline: do not mention clinical/medical applications. If
+commenters push toward "could this detect impairment/decline?", answer at the
+level of the public science and stop there.)*
+
+## Channels beyond HN
+
+- **Reddit** — r/Python (the library angle), r/programming, r/QuantifiedSelf,
+  r/coolgithubprojects. Lead with the angle each sub cares about; never
+  cross-post the same text.
+- **PyPI discoverability** — keywords are set; the README long-description is the
+  conversion surface (it's good — keep it).
+- **X / Bluesky** — the human-vs-robot path visual is the scroll-stopper.
+  "Everyone clones voices; nobody clones movement."
+- **HCI / writeup** — the predictive-vs-reactive + device-as-variable framing is
+  genuinely novel to that crowd; worth a short blog (the `dispatch` repo).
+
+## Metrics (launch week)
+
+PyPI downloads · GitHub stars + issues · landing visits · HN rank/comments ·
+inbound to `hello@` / `privacy@`.
+
+## Tracked
+
+#1 publish · #6 OIDC workflow · #8 landing deploy + `og.png` · #2 GTM umbrella
+(inboxes, screenshots, Show HN posting).