Weekly Digest 006
Built from ops/weekly/2026-09-28.json vs ops/weekly/2026-10-05.json (the two newest
dated snapshots — latest.json duplicates 10-05), GitHub issue history for
2026-09-28 → 2026-10-05, and decisions/ entries dated this week (none).
1. Drivers that moved
Diff of the drivers block, 2026-09-28.json → 2026-10-05.json:
| Driver (JSON key) | 09-28 | 10-05 | Change |
|---|---|---|---|
| reviews_per_active_parent_per_month | 1.333 (n=6, month 2026-08) | 1.333 (n=6, month 2026-08) | none |
| parents_invited_per_coach_per_month | 2 (n=3, month 2026-08) | 0.2 (n=5, month 2026-09) | value and denominator both moved |
| invite_to_first_purchase_conversion | 6 (n=1, month 2026-08) | 6 (n=1, month 2026-08) | none |
| parent_monthly_retention | null (n=0) — in not_tracked | 0 (n=6, month null) — out of not_tracked | first measured value |
| coach_monthly_churn | 0 (n=3, month 2026-09) | 0 (n=5, month 2026-10) | value held, denominator moved |
| price_per_review.usd | 15.00 (n=8) | 15.00 (n=8) | none |
parent_monthly_retention is measured for the first time — and it's 0%. Last week's
not_tracked array dropped parent_monthly_retention; this week's export carries a real
value: 0 out of 6 (the single 2026-08 cohort, matching cohorts[0].m1_retained flipping
null → 0). Read with caution — n=6 is the entire first cohort, not a sample, and the
month field is still null on the driver itself, so the export isn't yet attaching a
calendar month to this number. But at face value: zero of the six August parents made a
second purchase in month 2. This is the single most important fact in this digest and the
first real evidence against the season-one plan's retention assumption
(decisions/2026-08-20-season-one-plan.md) — not proof it's wrong, but the first data
point that could move it off basis: guess.
parents_invited_per_coach_per_month dropped 2 → 0.2, but the comparison isn't
like-for-like. The denominator (n) moved 3 → 5 and the attributed month moved
2026-08 → 2026-09 in the same step — this is last week's flagged anomaly resolving:
the two coaches who joined 9/24 and 9/25 (C-0ee6e9cc, C-57259821) have now rolled into
the per-coach invite calculation, each sending 0 invites in their first partial month, which
drags the per-coach average down. volume.new_parents_in_period moving 0 → 1 (one new
coach_brought parent, P-1840925a, joined 2026-10-01 under C-763bfd8b) confirms real
invite activity happened — C-763bfd8b's invites_sent_in_period went 0 → 1 between the
two snapshots. Reading the raw 2 → 0.2 drop as "invites collapsed" would overstate it; it's
mostly a denominator effect from onboarding two new, as-yet-inactive coaches.
coach_monthly_churn — same resolution. Value holds at 0, but n moved 3 → 5 and
month moved 2026-09 → 2026-10, confirming the two new coaches are now inside this
driver's rolling window too.
Coach-disappearance anomaly (digest 003 §1, digest 004 §1, digest 005 §1) — still
unresolved, not worsened. C-0f4b1805 remains absent from coaches/parents/roster
in 2026-10-05.json. No new contact_evidence or decisions/ entry explains it. Still an
open question for the export owner, not this digest to resolve.
Guess-basis baseline — now 6 weeks unowned. Confirmed against model/assumptions.yaml:
coach_monthly_churn, parents_invited_per_coach_per_month,
invite_to_first_purchase_conversion, parent_monthly_retention, and
reviews_per_active_parent_per_month are all still basis: guess with no owner: field
anywhere in the file. Digest 002 (2026-08-24) started this clock; it is now 6 calendar weeks
(08-24 → 10-05) with no movement toward measured or actual on any of the five — even
though parent_monthly_retention now has its first real data point, the assumptions file
itself hasn't been updated to reflect it.
2. Evidence logged
contact_evidence rows in 2026-10-05.json are identical to 2026-09-28.json —
zero new rows this week. No parent or coach touch was logged to the contact store between
the two snapshots.
3. Backlog shipped and started
Issue history for 2026-09-28 → 2026-10-05 (GitHub search on closed/created, boundary
issues #247–#253 excluded — they were created 2026-09-28 before 09:00 UTC and already
counted in digest 005).
Shipped (closed this week): none. Zero issues closed in this window — a contrast with last week's 3 closes.
Started (opened this week): 14 issues, driven mostly by a "Game In Review" epic breakdown, not organic backlog discovery from the beta:
| # | Title | Track / driver | |---|---|---| | 255 | Film Room — subscription (Game Report/game + two-way thread + monthly recap) | track:table-stakes, P3, surface:parent | | 256 | Team Plan — sponsored roster video + opt-in Game Report/Film Room + team view | track:table-stakes, P3, surface:coach | | 257 | Coach invite link forces 'create new player' — can't attach existing player to a 2nd coach | track:driver, driver:invites, P1, surface:parent, feedback | | 258 | Game In Review: AI-suggested, player-confirmed game review (epic) | track:driver, driver:frequency, P2, surface:review | | 259 | Game In Review: verify coded-export shapes (Hudl/Instat variants) | track:driver, driver:frequency, P2, surface:capture, spike | | 260 | Game In Review: free report — ingest → parse → candidacy → view | track:driver, driver:frequency, P2, surface:review | | 261 | Game In Review: confirm + send 1–N clips to a coach | track:driver, driver:conversion, P2, surface:parent | | 262 | Game In Review: coach side — grouped bench request + review sent clips | track:driver, driver:coach-churn, P2, surface:coach | | 263 | Game In Review: home-surface game grouping (collapsed group card) | track:table-stakes, P2, surface:platform | | 264 | Game In Review: monetization — subscription (report) + per-clip reviews | track:driver, driver:retention, P2, surface:payments | | 265 | Game In Review: conversion — data-prompt + coach pay-to-reveal nudge | track:driver, driver:conversion, P3, surface:coach | | 266 | Game In Review: jersey-only anonymization for non-subject minors | track:obligation, P1, surface:platform | | 268 | Game In Review poster: label the key-moment time to match the thumbnail frame | track:driver, driver:frequency, P3, surface:review | | 269 | Revisit & streamline the Send to Coach UX (Game In Review) | track:driver, driver:conversion, P2, surface:parent, feedback |
By track: 10 track:driver (all 10 carry a driver:x tag — no hygiene gap this week,
unlike digest 005's #248), 3 track:table-stakes, 1 track:obligation.
Two items (#257, #269) carry the feedback flag — genuinely beta-sourced, not roadmap
decomposition. #266 is worth flagging on its own: it's a track:obligation/P1 item about
jersey-only anonymization for non-subject minors in Game In Review footage — squarely a
Tier-1 minors-data concern (.claude/rules/pii-boundary.md territory, applied to product
surface rather than this repo) and worth tracking to close given the PII boundary this repo
already holds itself to.
4. Decisions needed
No decisions/ entries dated this week (newest are still 2026-09-09). Carrying forward
digest 005's list unchanged, with elapsed weeks updated:
- Price-per-review derivation unconfirmed (
decisions/2026-08-19-price-per-review.md) — carried, 6 weeks. Matt still needs to confirm or complete the $120/hr → $15 derivation. - Season-one plan adopted without Alex, Danny, or Derek (
decisions/2026-08-20-season-one-plan.md) — carried, 6 weeks. The free-allowance removal and $20 September default still need those three conversations — now with a first (grim) retention data point on the table. - Market analysis + seasonality layer (
decisions/2026-08-20-market-analysis-and-seasonality.md) — carried, 6 weeks. Still flagged for Alex's review at onboarding, still unreviewed. - Startup capital exclusion (
decisions/2026-08-20-startup-capital-excluded-from-operating-model.md) — carried, 6 weeks. Reversal condition is explicitly Alex's to invoke as CFO; still open. - Residual Tier-1 confirmation on incorporation (
decisions/2026-09-09-incorporation-in-place-no-coach-reonboard.md) — carried, 3 weeks. Still need Stripe/counsel confirmation that the sole-prop → incorporated swap doesn't trigger a platform re-KYC that pauses payouts, and still need to resolve the jurisdiction conflict the decision file itself flags (Delaware C-corp vs. Ontario / GameBooth Inc. appear in different places in the repo).
Five open decisions, four of them now 6 weeks unmoved — still worth a standing agenda item, as digests 002 through 005 have all already said.
5. Touch points this week
From the roster block (2026-10-05.json) — same 6 SILENT parents as digest 005, plus
one new arrival (P-1840925a, joined 2026-10-01, NEW) and the same 2 NEVER_CONTACTED
parents. Ordering by primary_flag (SILENT, ONE_AND_DONE, NEW, NEVER_CONTACTED,
CADENCE_DUE), the 6 SILENT parents alone fill the cap — 3 cut (1 NEW, 2
NEVER_CONTACTED).
| Handle | Why (primary_flag) | Owner | Suggested opener |
|---|---|---|---|
| P-2952f6f8 | SILENT | Alex | Last purchase 8/3, one delivered review 8/4, last touched 8/20 — now 62 days since purchase with nothing since. |
| P-c2dc0179 | SILENT | Alex | Most active parent on record — 3 paid, 3 delivered, all by 8/7 — contacted 9/11, now also CADENCE_DUE at 58 days since purchase. Worth asking directly what that call turned up. |
| P-494a7944 | SILENT | Alex | 2 paid, 1 cancelled, last delivery 8/16, last touched 8/20 — now 51 days since purchase, still no follow-up; the cancellation plus continued silence is worth a direct check-in. |
| P-7d3431ec | SILENT | Alex | One delivered review 8/14, last touched 8/19 — now 53 days since purchase, no repeat purchase since. |
| P-f1c95a7d | SILENT | Alex | One delivered review 8/14, last touched 8/20 — now 52 days since purchase, no repeat purchase since. |
| P-4719cb7d | SILENT | Alex | One delivered review 8/19, last touched 8/19 — now 48 days since purchase, no repeat purchase since; earliest-joined (8/18) of this cohort. |
Follow-through on digest 005's touch list (6 handles): zero contact_evidence rows
were logged at all this week (section 2), so none of the six were followed up on.
- P-2952f6f8 — no new contact since 8/20. Fourth week running with no follow-up.
- P-c2dc0179 — no new contact since 9/11. Third week running.
- P-494a7944 — no new contact since 8/20. Fourth week running.
- P-7d3431ec — no new contact since 8/19. Fourth week running.
- P-f1c95a7d — no new contact since 8/20. Fourth week running.
- P-4719cb7d — no new contact since 8/19. Fourth week running.
Net: zero of the six were followed up on this week — the fourth week running for five of
the six, the third for P-c2dc0179. This is past the three-weeks-running threshold digest
005 already named directly; stating it again plainly rather than softening it: this touch
list has now gone an entire month with no action against five of its six names, during the
same week the export produced its first measured retention number and that number was 0%.
6. Mid-week pulse
No pulse entries this week.