Weekly Digest 005
Built from ops/weekly/2026-09-24.json vs ops/weekly/2026-09-28.json (the two newest
dated snapshots — latest.json duplicates 09-28), GitHub issue history for
2026-09-21 → 2026-09-28, and decisions/ entries dated this week (none).
1. Drivers that moved
Diff of the drivers block, 2026-09-24.json → 2026-09-28.json:
| Driver (JSON key) | 09-24 | 09-28 | Change |
|---|---|---|---|
| reviews_per_active_parent_per_month | 1.333 (n=6) | 1.333 (n=6) | none |
| parents_invited_per_coach_per_month | 2 (n=3) | 2 (n=3) | none |
| invite_to_first_purchase_conversion | 6 (n=1) | 6 (n=1) | none |
| parent_monthly_retention | null (n=0) | null (n=0) | none |
| coach_monthly_churn | 0 (n=3) | 0 (n=3) | none |
| price_per_review.usd | 15.00 (n=8) | 15.00 (n=8) | none |
Zero movement — nothing was learned this week that changes a driver value. All five
behavioral drivers are still anchored to month: "2026-08" or "2026-09" with an
unchanged n.
Two new coaches joined, but no driver denominator moved yet. volume.active_coaches
jumps 3 → 5 between the two snapshots (coaches array gains C-0ee6e9cc, joined 9/24,
and C-57259821, joined 9/25), yet parents_invited_per_coach_per_month and
coach_monthly_churn both hold at the same n and month as last week — the new
coaches haven't rolled into either calculation yet. Flagging so next week's diff isn't
read as organic movement if/when it catches up.
Coach-disappearance anomaly (digest 003 §1, digest 004 §1) — still unresolved, not
worsened. C-0f4b1805, dropped from coaches/parents/roster between the 09-07 and
09-14 exports, remains absent from both 09-24.json and 09-28.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 5 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.
Digest 002 (2026-08-24) started this clock; it is now 5 calendar weeks (08-24 → 09-28)
with no movement toward measured or actual on any of the five.
2. Evidence logged
contact_evidence rows in 2026-09-28.json not present in the 09-24.json snapshot:
| Handle | Date | Channel | Driver tags | Direction | |---|---|---|---|---| | C-0ee6e9cc | 2026-09-24 | call (them) | (none) | Indeterminate — no driver tags logged |
One new row, and it carries no driver tags — same pattern digest 004 flagged for the two
09-14 C-763bfd8b rows. Not inventing a direction where none is logged.
No other rows are new since digest 004: the five 08-19/08-20 parent rows, the 09-09 and
09-11 rows, and the two 09-14 C-763bfd8b rows all already appear in the 09-24.json
snapshot, which is otherwise identical to 09-21.json (the base digest 004 used).
3. Backlog shipped and started
Issue history for 2026-09-21 → 2026-09-28 (GitHub MCP search on closed/created).
Shipped (closed this week):
| # | Title | Track / driver | |---|---|---| | 244 | Parent home roadmap — V1 In their corner (epic) | track:table-stakes, P1, surface:parent | | 202 | Coach home V1.1: Coach identity band | track:table-stakes, P1, surface:coach | | 194 | Coach onboarding console — Phase 1 (keys + gate) | track:table-stakes, P1, surface:coach |
No track:driver issue closed this week — all three closes were track:table-stakes
scaffolding for the coach/parent home surfaces.
Started (opened this week): 54 issues — a roadmap-decomposition event, not organic
backlog discovery. The large majority (51) are track:table-stakes: the Coach Home
roadmap broken into V1–V5 epics and numbered sub-items (#195–#239, surface:coach),
the Parent Home roadmap epics V2–V5 (#250–#253), a shared-services index (#247),
and a Coach AI Assistant epic (#249). Reading this batch as backlog growth this week
would overstate it — it's the roadmap being seeded into the tracker, not new work
discovered from the beta.
Only 3 opened issues carry track:driver:
| # | Title | Track / driver |
|---|---|---|
| 248 | S1: Next-clip ask — shared coach↔parent loop (epic) | track:driver, P2, surface:coach — no driver:x tag present |
| 243 | Goalie coaches may need a distinct Parent User Journey (clip composition), cross-sport | track:driver, driver:coach-churn, P2, spike, feedback |
| 242 | Cap review clip length for goalie coaches (max ~90s) | track:driver, driver:coach-churn, P2, feedback |
#248 is flagged for issue hygiene: it's labeled track:driver but carries no
driver:x tag, so this digest can't say which driver it's meant to move.
4. Decisions needed
No decisions/ entries dated this week (newest are 2026-09-09). Carrying forward digest
004's list unchanged, with elapsed weeks updated:
- Price-per-review derivation unconfirmed (
decisions/2026-08-19-price-per-review.md) — carried, 5 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, 5 weeks. The free-allowance removal and $20 September default still need those three conversations. - Market analysis + seasonality layer (
decisions/2026-08-20-market-analysis-and-seasonality.md) — carried, 5 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, 5 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, 2 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 5 weeks unmoved — still worth a standing agenda item, as digests 002, 003, and 004 have all already said.
5. Touch points this week
From the roster block (2026-09-28.json) — same 8 parents as last week, same flags
except P-c2dc0179 newly gained CADENCE_DUE (its last paid purchase, 8/7, is now 51
days out). 6 parents carry a flag (all SILENT); 2 cut (P-c4005031, P-64d03653, both
NEVER_CONTACTED, unchanged since digest 002 — no new facts to report).
| 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 39 days ago with nothing since. |
| P-c2dc0179 | SILENT | Alex | Most active parent on record — 3 paid, 3 delivered, all by 8/7 — contacted 9/11 (17 days ago); now also CADENCE_DUE. 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 39 days ago, still no follow-up purchase; 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 40 days ago, no repeat purchase since. |
| P-f1c95a7d | SILENT | Alex | One delivered review 8/14, last touched 8/20 — now 39 days ago, no repeat purchase since. |
| P-4719cb7d | SILENT | Alex | One delivered review 8/19, last touched 8/19 — now 40 days ago, no repeat purchase since; earliest-joined (8/18) of this cohort. |
Follow-through on digest 004's touch list (6 handles):
- P-2952f6f8 — no new contact since 8/20. Third week running with no follow-up.
- P-c2dc0179 — no new contact since 9/11. Second week running.
- P-494a7944 — no new contact since 8/20. Third week running.
- P-7d3431ec — no new contact since 8/19. Third week running.
- P-f1c95a7d — no new contact since 8/20. Third week running.
- P-4719cb7d — no new contact since 8/19. Third week running.
Net: zero of the six were followed up on this week — the third week running with zero
follow-through for five of the six (P-c2dc0179 is on its second, having reset the clock
with its 9/11 contact). Per the honesty rule on a three-weeks-running miss: this is that
threshold, stated directly rather than softened.
6. Mid-week pulse
No pulse entries this week.