docs(kpi): add docs/incidents.md — false-blocker incident log convention + seed entry #95

Merged

pdurlej merged 1 commit from claude/docs-incidents-log into main

2026-06-22 22:39:59 +02:00

claude commented

2026-06-22 22:34:38 +02:00

Collaborator

What

Creates docs/incidents.md — the false-blocker incident-log convention + a seed baseline entry.

Why

The docs-maturity audit (2026-06-16) flagged this as a promised-but-missing artifact with a hard deadline:

product/kpi-tree.md (O1.KR1.3, O3.KR3.2, §6 Goodhart Scenario A) and roadmap.md (G5) both point at docs/incidents.md — which did not exist, leaving a broken reference chain under the north-star metric.
KPI O3.KR3.2 deadline: 2026-07-31 (template + first dummy entry). This lands it ahead of time.

Definitions — what a false-blocker incident is (Patchwarden held a PR that was actually safe to merge) vs a correct hold (the product working), plus false-negative as a secondary axis.
Cold classification rule — one written question per operator override; false_blocker: true/false.
Goodhart guard — classification lives in git history, never softened retroactively; corrections are new dated entries, not edits (per kpi-tree §6 Scenario A).
Entry template + seed baseline entry (rolling false-blocker count: 0).

Safety

Docs-only; 303 tests green.
No metric is invented — it operationalizes the existing D13 north-star + U2 kill-criterion.

From the 2026-06-16 docs-maturity wave (approved item #4). Do not merge — operator merge only.

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

## What Creates **`docs/incidents.md`** — the false-blocker incident-log convention + a seed baseline entry. ## Why The docs-maturity audit (2026-06-16) flagged this as a **promised-but-missing** artifact with a hard deadline: - `product/kpi-tree.md` (O1.KR1.3, O3.KR3.2, §6 Goodhart Scenario A) and `roadmap.md` (G5) both point at `docs/incidents.md` — which did **not exist**, leaving a broken reference chain under the north-star metric. - **KPI O3.KR3.2 deadline: 2026-07-31** (template + first dummy entry). This lands it ahead of time. ## Contents - **Definitions** — what a false-blocker incident is (Patchwarden held a PR that was actually safe to merge) vs a *correct* hold (the product working), plus false-negative as a secondary axis. - **Cold classification rule** — one written question per operator override; `false_blocker: true/false`. - **Goodhart guard** — classification lives in git history, never softened retroactively; corrections are new dated entries, not edits (per kpi-tree §6 Scenario A). - **Entry template** + **seed baseline entry** (rolling false-blocker count: **0**). ## Safety - Docs-only; **303 tests green**. - No metric is invented — it operationalizes the existing D13 north-star + U2 kill-criterion. From the 2026-06-16 docs-maturity wave (approved item #4). **Do not merge — operator merge only.** Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Rows
Columns