v4.0 closeout: validation-ledger debt for phases 64–69 (deferral mismarked 'resolved')

[szTheory]

Summary

The Phase 69 v4.0 Closeout Proof (phase69-proof.yml → merge-blocking-closeout-proof) fails closeout.validation.ledger for archived phases 64, 65, 66, 67, 68, 69. This is genuine pre-existing debt, surfaced (not caused) by an unrelated change to lib/crosswake/planning/closeout_verifier.ex — that file is in the proof's relevance trigger.

The debt

• Phases 64–69 have no *-VALIDATION.md ledgers under .planning/milestones/v4.0-phases/.
• .planning/milestones/v4.0-CLOSEOUT.md deferred this (scope: validation-ledger-finalization, revisit_phase: 70) but marked the entry status: resolved — recorded as paid, while the ledgers were never created.

Why it can't be papered over

The verifier intentionally makes the deferral state contradictory when ledgers are missing:

• closeout.validation.ledger (v4.0 proof) passes only if the deferral is active (status ≠ resolved/closed).
• closeout.validation.prior_debt (any current-milestone run) passes only if the deferral is resolved or the ledgers are actually compliant.

So the only honest resolution is to create nyquist-compliant validation ledgers for 64–69, or make a deliberate maintainer decision to formally retire the debt.

Impact

• Non-blocking: merge-blocking-closeout-proof is NOT in main's required checks (merge-blocking rulestead proof, brand-structural), so it does not block merges. It will show red on any PR that touches closeout_verifier.ex or the v4.0 closeout paths.

Options

1. Author the 64–69 validation ledgers (real validation work / evidence).
2. Formally retire the debt (decide these archived phases need no ledger; encode that honestly).
3. Accept as a known-red non-required check until a future milestone addresses it.

Context: this is the "validation-ledger debt that rolled forward each milestone (v3.6→48, v3.9→64), never done" pattern.

🤖 Generated with Claude Code