docs(decisions): D22 — reconcile V4 kill-criterion date with D15 (2026-06-30 → 2026-09-30) #92

Merged

pdurlej merged 1 commit from claude/decisions-d22-v4-reconcile into main

2026-06-17 23:29:25 +02:00

claude commented

2026-06-17 23:16:52 +02:00

Collaborator

What

Records D22 and syncs the M2 discovery-interview deadline from 2026-06-30 → 2026-09-30 across the four docs that were out of sync with the canonical decision log.

Why (the landmine)

V4 (product/kill-criteria.md, drafted 2026-05-15): "if <5 of 7 interviews by 2026-06-30 → park Patchwarden code work." Status today: 0/7 interviews.
D15 (decisions.md, resolved 2026-05-26 — the newer decision): re-sequenced M2 to install-count precondition BEFORE interviews, interview deadline moved to 2026-09-30 (= M2 close / Q3 ship).
decisions.md D15 already carried 2026-09-30, but roadmap.md, discovery-cadence.md, kpi-tree.md and V4 itself were never synced and still read 2026-06-30 — a contradiction that, read literally, would auto-park all code work on a date D15 had already superseded.

D17 discipline

This is a date-sync to a prior cold decision (D15), not a panic threshold-edit. The ≥5-of-7 threshold and the "park" action are unchanged; only the stale date moves. V4 is annotated in place (audit trail preserved, not silently overwritten). D17 forbids softening a threshold because it's about to trigger — that is not what this does.

Changes

decisions.md — new D22 entry + adds the missing D21 summary-table row.
kill-criteria.md — V4 date + transparent D22 annotation.
roadmap.md — Now/Next, Cagan-gates table, Q2 tracker, Q2 wrongness, O2.KR2.1, hard-milestones table (reordered for chronology).
discovery-cadence.md — TL;DR (PL+EN), M2-gate criteria, slip-trigger, proposed-decision summary.
kpi-tree.md — leading-indicators note + KR2.1.

Safety

Docs-only; 260 tests green (PYTHONPATH=src python3 -m unittest discover tests).
Binding constraints unchanged: D15 install-count precondition, 2026-09-30 completion gate, V1 (<30% must-have → pivot), M3 review (2026-10-15), operator sunk-cost circuit-breaker. V4 still fires — on the date D15 actually set.

Surfaced by the 2026-06-16 opportunity audit (completeness-critic). Operator-approved ("OK D22"). Do not merge — operator merge only.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

## What Records **D22** and syncs the M2 discovery-interview deadline from **2026-06-30 → 2026-09-30** across the four docs that were out of sync with the canonical decision log. ## Why (the landmine) - **V4** (`product/kill-criteria.md`, drafted 2026-05-15): "if <5 of 7 interviews by **2026-06-30** → **park Patchwarden code work**." Status today: **0/7** interviews. - **D15** (`decisions.md`, resolved **2026-05-26** — the newer decision): re-sequenced M2 to **install-count precondition BEFORE interviews**, interview deadline moved to **2026-09-30** (= M2 close / Q3 ship). - `decisions.md` D15 already carried 2026-09-30, but `roadmap.md`, `discovery-cadence.md`, `kpi-tree.md` and V4 itself were **never synced** and still read 2026-06-30 — a contradiction that, read literally, would auto-park *all* code work on a date D15 had already superseded. ## D17 discipline This is a **date-sync to a prior cold decision (D15), not a panic threshold-edit**. The ≥5-of-7 threshold and the "park" action are unchanged; only the stale date moves. V4 is **annotated in place** (audit trail preserved, not silently overwritten). D17 forbids softening a threshold *because it's about to trigger* — that is not what this does. ## Changes - `decisions.md` — new **D22** entry + adds the missing **D21** summary-table row. - `kill-criteria.md` — V4 date + transparent D22 annotation. - `roadmap.md` — Now/Next, Cagan-gates table, Q2 tracker, Q2 wrongness, O2.KR2.1, hard-milestones table (reordered for chronology). - `discovery-cadence.md` — TL;DR (PL+EN), M2-gate criteria, slip-trigger, proposed-decision summary. - `kpi-tree.md` — leading-indicators note + KR2.1. ## Safety - Docs-only; **260 tests green** (`PYTHONPATH=src python3 -m unittest discover tests`). - Binding constraints unchanged: D15 install-count precondition, 2026-09-30 completion gate, V1 (<30% must-have → pivot), M3 review (2026-10-15), operator sunk-cost circuit-breaker. **V4 still fires — on the date D15 actually set.** Surfaced by the 2026-06-16 opportunity audit (completeness-critic). Operator-approved ("OK D22"). **Do not merge — operator merge only.** Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Rows
Columns