decision-loglisted

# Decision Log Capture the *why* of contract-significant, friction-driven changes as small, **verifiable** notes — before the reasoning evaporates into the diff. Each entry is forward-compatible with a future trust-layer / architecture-fact checker that re-runs the `Verify` lines. This habit must survive deadlines. It optimises for low friction and honest, checkable facts over completeness. Capturing a high-signal *subset* reliably beats capturing everything and rotting (the ADR graveyard). ## Skill Type: Mixed Rigid/Flexible **Rigid gates (non-negotiable):** - Propose in ONE line; never write the entry before the user confirms. - Never nag — if the user declines, drop it silently and continue. - `Verify` MUST be honestly tiered (gold / partial / unverifiable) — never a vague "looks right". - `Anchor` MUST use stable references (symbol names, #issue/PR, commit-pinned permalinks) — NEVER a bare `file:line`. - Never fabricate the date. **Flexible path (use judgement):** - Whether a given diff is genuinely "contract-significant" (when unsure, do NOT propose — false positives train the user to ignore you, which kills the habit). - How to phrase Friction/Decision concisely. - Which verification mechanism fits (test, pyeye query, grep, import-linter contract, human review). ## When This Fires **Primary trigger — the commit checkpoint.** When a commit is being prepared and the staged diff touches a **contract surface**, propose ONE decision note before finalising. Contract