docs(v0): restructure roadmap around Cagan-rhythm gates + codex handoff (#27-#33) #34

Merged

pdurlej merged 1 commit from claude/patchwarden-roadmap-update into main

2026-05-26 08:56:20 +02:00

claude commented

2026-05-26 08:53:58 +02:00

Collaborator

Summary

Restructure docs/roadmap.md so it reflects the actual state of Patchwarden as of 2026-05-26 — both the strategic track (Cagan Package v1.0 milestone M1 due 2026-05-30, kill-criteria cadence D17, bet wrongness gates from strategy.md) and the implementation track (7 ready-for-agent issues #27-#33 codex handed off today). Output of gap analysis docs ↔ src/patchwarden + the product-management:roadmap-update skill.

What changed

Restructure (no content dropped):

New "Now / Next / Later" executive view at top with concrete issues + M1 deadline
New "Cagan-rhythm gates" table (M1/M2/M3 + quarterly kill reviews per D17)
Wrongness conditions inlined per quarter (Bet 1-3 from strategy.md, V1/V2/V4/U2/F1/F2/B1/B3/B4 from kill-criteria.md)
Each quarter split into operator-track vs cousin-track (honesty about who can do what)
Q3 OKRs O1/O2/O3 from kpi-tree.md written as deliverables, not just goals
New capacity reality check section (operator bandwidth + Codex Wave 5 dependency named)

New items surfaced:

M1 Cagan Package merge (deadline 2026-05-30, 4 days away — was missing from roadmap entirely)
Codex handoff issues #27-#33 mapped into Q2/Q3 sequence
G5 incident log convention (KPI O3.KR3.2, due 2026-07-31) — needs new issue
G9 cloud_review schema field (D7 alignment) — needs new issue
M3 quarterly kill-criteria review cadence (D17)
B2 (Kodus Forgejo adapter) + B4 (auditlm policy DSL) wrongness gates added to 2027

What came off: nothing — restructure + addition only. Diff is +227 / -66.

Why now

Three signals converged today:

Codex created 7 ready-for-agent atomic issues (#27-#33) and the macro-roadmap didn't reflect that micro-sequence.
M1 Cagan Package v1.0 milestone has a 4-day deadline (2026-05-30) but roadmap.md doesn't mention M1/M2/M3 anywhere.
strategy.md is v1.0 locked through M3 with explicit bet wrongness conditions; roadmap.md didn't surface those gates per quarter.

Verification

head -5 docs/roadmap.md — top header dated 2026-05-26
Now/Next/Later section lists #27 + M1 in "Now"
Cagan-rhythm gates table includes M1 (2026-05-30), M2 (2026-06-30), M3 (2026-10-15)
Q2/Q3/Q4/Q1/Y2 quarter structure preserved (zero lost content from previous version)
Anti-roadmap section preserves all original bullets + adds "Skip M1 Cagan merge before 2026-05-30"
Hard milestones table includes every date from kill-criteria.md + kpi-tree.md + decisions.md

Notes for review

This is a roadmap-as-communication restructure, not a strategy change. Strategy v1.0 stays locked per D16 until M3 refresh.
No commitments shifted earlier or later; just made visible what was already implicit in strategy/kill-criteria/kpi-tree.
Capacity section names the O2 operator-bandwidth risk explicitly — please push back if any of the "Now" items should slip given M1 deadline pressure.

🤖 Generated by claude (Patchwarden dedicated thread) via product-management:roadmap-update skill on gap analysis output. Identity verified: Forgejo whoami = claude (id 3), git config = claude / claude@noreply.git.pdurlej.com.

## Summary Restructure `docs/roadmap.md` so it reflects the actual state of Patchwarden as of 2026-05-26 — both the **strategic track** (Cagan Package v1.0 milestone M1 due 2026-05-30, kill-criteria cadence D17, bet wrongness gates from `strategy.md`) and the **implementation track** (7 ready-for-agent issues #27-#33 codex handed off today). Output of gap analysis docs ↔ src/patchwarden + the `product-management:roadmap-update` skill. ## What changed **Restructure (no content dropped):** - New "Now / Next / Later" executive view at top with concrete issues + M1 deadline - New "Cagan-rhythm gates" table (M1/M2/M3 + quarterly kill reviews per D17) - Wrongness conditions inlined per quarter (Bet 1-3 from `strategy.md`, V1/V2/V4/U2/F1/F2/B1/B3/B4 from `kill-criteria.md`) - Each quarter split into **operator-track** vs **cousin-track** (honesty about who can do what) - Q3 OKRs O1/O2/O3 from `kpi-tree.md` written as deliverables, not just goals - New capacity reality check section (operator bandwidth + Codex Wave 5 dependency named) **New items surfaced:** - M1 Cagan Package merge (deadline **2026-05-30, 4 days away** — was missing from roadmap entirely) - Codex handoff issues #27-#33 mapped into Q2/Q3 sequence - G5 incident log convention (KPI O3.KR3.2, due 2026-07-31) — needs new issue - G9 `cloud_review` schema field (D7 alignment) — needs new issue - M3 quarterly kill-criteria review cadence (D17) - B2 (Kodus Forgejo adapter) + B4 (auditlm policy DSL) wrongness gates added to 2027 **What came off:** nothing — restructure + addition only. Diff is +227 / -66. ## Why now Three signals converged today: 1. Codex created 7 `ready-for-agent` atomic issues (#27-#33) and the macro-roadmap didn't reflect that micro-sequence. 2. M1 Cagan Package v1.0 milestone has a 4-day deadline (2026-05-30) but roadmap.md doesn't mention M1/M2/M3 anywhere. 3. `strategy.md` is v1.0 locked through M3 with explicit bet wrongness conditions; roadmap.md didn't surface those gates per quarter. ## Verification - [ ] `head -5 docs/roadmap.md` — top header dated 2026-05-26 - [ ] Now/Next/Later section lists #27 + M1 in "Now" - [ ] Cagan-rhythm gates table includes M1 (2026-05-30), M2 (2026-06-30), M3 (2026-10-15) - [ ] Q2/Q3/Q4/Q1/Y2 quarter structure preserved (zero lost content from previous version) - [ ] Anti-roadmap section preserves all original bullets + adds "Skip M1 Cagan merge before 2026-05-30" - [ ] Hard milestones table includes every date from `kill-criteria.md` + `kpi-tree.md` + `decisions.md` ## Notes for review - This is a **roadmap-as-communication** restructure, not a strategy change. Strategy v1.0 stays locked per D16 until M3 refresh. - No commitments shifted earlier or later; just made visible what was already implicit in strategy/kill-criteria/kpi-tree. - Capacity section names the O2 operator-bandwidth risk explicitly — please push back if any of the "Now" items should slip given M1 deadline pressure. --- 🤖 Generated by claude (Patchwarden dedicated thread) via `product-management:roadmap-update` skill on gap analysis output. Identity verified: Forgejo whoami = claude (id 3), git config = claude / claude@noreply.git.pdurlej.com.

Rows
Columns