01-projects/printables-product/reviews

Roadmap grooming

2026-09-16·status: gated-iterate-applied

What was reviewed

Full queue.md, rulings 1-33, both cohort-feedback syntheses, feedback/ directory listing (newest file 2026-09-08), rounds.md/escalations.md tails, plus live verification: gh pr view on #255/#242, gh run list, and a direct status/age_band count across all 79 content/games/*/meta.yaml.

Findings

  1. New, not in any note: live-game audit by age band (live/pending-review): 2_3 = 1/11, 5_6 = 10/11, 7_8 = 7/7, 9_10 = 10/2, 3_4 = 15/4. 2_3 and 5_6 both carry an 11-game unreviewed backlog — review-portal throughput, not production, is now the binding constraint there, not lane thinness. 7_8 stays thinnest-live, matching tonight's dispatch reasoning (rounds.md 2026-09-15 entry) — no conflict.
  2. GH Actions billing block (escalations.md, reported 2026-09-14/15) is resolved, verified live via gh run list: real pass/fail CI runs through 2026-09-16T02:56Z, not instant billing-block annotations. No founder action needed.
  3. queue.md:12 ("Paint the Color Wheel... awaiting founder tap") and the Chomp carry-over (queue.md:341-345) are stale — gh pr view confirms #255 and #242 both MERGED 2026-09-15. Cosmetic only.
  4. R7 (§8d PR-count counter, queue.md:15) genuinely still unbuilt — no counter script exists in scripts/. Correctly still open.
  5. Cohort/feedback signal unchanged since 09-12 synthesis: no feedback/ file postdates 2026-09-08; that synthesis's queue retirement (queue.md ~216) is present and correct.

Proposed queue.md changes

- ~~Paint the Color Wheel~~ DONE 2026-09-14 round: PR #255 (critic PASS, CI green, awaiting founder tap).
+ ~~Paint the Color Wheel~~ DONE — PR #255 MERGED 2026-09-15.
- (Chomp #242 carry-over) Next: one more build slot ... flip #242 to ready if PASS.
+ Chomp #242 MERGED 2026-09-15. Closed.
+ [product, AUTONOMOUS] NEXT-ROUND BIAS (post-tonight): new-game lane stays 7_8/9_10. 2_3 new production HELD (91.7% unreviewed, only 1/12 live — an extreme enough ratio to hold by default). 5_6 NOT held by default — its backlog ratio (52.4%) is comparable to 7_8's (50%), which stays greenlit; freezing 5_6 too would be inconsistent without a founder call. See decisions needed.

The Color Wheel/Chomp staleness fixes and the 2_3 hold are mechanical/proportionate — applied within product's autonomous lane. The 5_6 question is NOT applied autonomously (corrected post-gate, see gate_note above) — bundling it into the same freeze as 2_3 understated how close its ratio sits to 7_8's, which keeps producing.

Decisions needed

  1. 2_3 lane freeze: hold new 2_3 production until the 11-game review backlog clears (only 1 of 12 built games is live) — is that the right trade, or is there a reason to keep producing there regardless of review capacity (e.g. variety before your own review time catches up)? Genuine prioritization call, not autonomous — it's your review-queue time being the constraint.
  2. 5_6 lane, added post-gate: backlog ratio (10 live/11 pending = 52.4% unreviewed) is close to 7_8's (7 live/7 pending = 50%), which nobody's proposing to freeze. Hold 5_6 to the same rule as 2_3, or is 7_8's comparable ratio the actual baseline and 5_6 is fine to keep producing? No bear case for either read exists yet — flagging rather than guessing.