# Sprint 109 Plan: Cross-Epoch Technical Debt Burn-Down

## Context

Long-lived programs accumulate debt across adapters, policies, and artifacts.
Sprint 109 systematizes debt identification and burn-down execution.

---

## Goals

1. Build debt inventory across code, policy, and process layers
2. Prioritize debt by risk and maintenance burden
3. Schedule debt burn-down without disrupting critical operations
4. Track debt retirement impact on quality and velocity

---

## Steps

### Step 1319: Technical debt inventory schema (12 tests)
### Step 1320: Debt risk/impact scoring model (10 tests)
### Step 1321: Burn-down planning optimizer (10 tests)
### Step 1322: Debt execution queue integration (10 tests)
### Step 1323: Debt retirement effectiveness tracker (10 tests)
### Step 1324: Critical-path disruption guardrails (8 tests)
### Step 1325: `whetstone_get_debt_inventory` MCP tool (8 tests)
### Step 1326: `whetstone_plan_debt_burndown` MCP tool (8 tests)
### Step 1327: Debt burn-down report artifact (8 tests)
### Step 1328: Sprint 109 integration summary + regression (8 tests)

---

## Debt Rule

- Critical-path debt with high risk cannot be deferred without documented rationale.