01-projects/printables-product/reviews

Cohort feedback synthesis

2026-09-12·status: gated-pass

What was reviewed

feedback/ for files postdating [[2026-09-05-cohort-feedback-synthesis]]: only [[2026-09-08-michelle-homemade-games]] (Sep 8, 20:29) is new; [[2026-09-08-vaughn-feedback-log]] (Sep 8, 17:00) was already resolved (queue.md:314, PR #132). D1 feedback table via node scripts/feedback-triage.mjs --all: zero rows. escalations.md:96/100 (#30, cohort un-parking, resolved 2026-09-05) and escalations.md:44-49 (feedback door built + self-tested 2026-09-02). Vault-wide grep -ril cohort under printables-product/ returns 12 hits by mtime after 09-05; almost all are unrelated-content mtime noise from a 2026-09-06 bulk touch. By content date, three are genuinely new but off-topic: [[2026-09-06-content-outreach-research-scribble-works]] (Sol/Codex-commissioned outreach research, "cohort" as a phase term, already filed); [[2026-09-11-business-opportunity-pricing-and-acquisition]] (cohort-tracking pricing proposal, not tester signal); [[2026-08-31-studio-charter]]'s 2026-09-10 PRs-direct-to-main amendment (process, already reflected in queue.md). escalations.md:226 (2026-09-12 production auto-deploy question) checked per dispatch.

Findings

  1. No new tester feedback since 09-08; [[2026-09-08-michelle-homemade-games]] is filed as design inspiration, explicitly not queued as a build task.
  2. D1 feedback table is empty — zero organic use, not broken plumbing. rounds.md:87 + escalations.md:49 confirm the feedback@ → Worker → D1 path was built and self-tested end-to-end 2026-09-02 (Resend test row written, matched, deleted); no later re-verification exists anywhere in the cited files. Adoption gap, not a build gap.
  3. queue.md:198 is stale. Its "[ops] After founder fixes Email Routing perms..." line predates the fix — the founder set the rules and Ray confirmed the self-test 2026-09-02 (escalations.md:49; rounds.md:87). Retiring it is bookkeeping, not a new decision.
  4. Cohort stays at 2 kids (daughter + niece), no expansion signal (escalations.md:100).
  5. escalations.md:226 (production auto-deploys on green CI to main) remains open, unresolved as of tonight. Nothing below proposes or implies a merge to main.

Proposed queue.md changes

- [ops] After founder fixes Email Routing perms: add rules hello@ → ben, feedback@ → Worker sw-feedback-intake, catch-all → ben. Twilio = founder "open Twilio".
+ 2026-09-12 RESOLVED — feedback@/hello@/catch-all rules were set by the founder and self-tested end-to-end 2026-09-02 (escalations.md:49; rounds.md:87). Item closed.

Decisions needed

  1. The feedback@ door is live, tested, and unused for ten days — worth deciding whether to prompt the two active testers directly, since discovery, not plumbing, looks like the gap.