diff --git a/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md b/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md
index dabf67d8..c741eda0 100644
--- a/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md
+++ b/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md
@@ -4,6 +4,7 @@ status: in-progress
 code: [mesh-controller, mesh-catalog modules/mesh-delivery]
 updated: 2026-10-12
 decisions:
+  - "ADR 0313"
   - "ADR 0306"
   - "ADR 0299"
   - "ADR 0298"
@@ -222,6 +223,14 @@ shown and held to no budget. Measured on 51 walks on 2026-10-09 and 10, a leaf w
 (7 of 20 within five), a core walk of one tier 5.6 (worst 8.8), and a controller walk dragging two catalogue tiers
 14.2 (issue 338).
 
+*A wider measure, around the delivery budget (2026-10-12, ADR 0313, extending ADR 0282).* The delivery budget
+above runs from the merge; the operator's own target is wider, the **fix time**, which runs from an issue's
+first move to `fixing` to the moment its last fix is delivered. Each issue's class carries a **fix budget** too
+(five minutes leaf, ten core, the delivery budget's own figures), and the tracker splits a fix time into four
+phases — implementing, review, checks, and merge to running (the delivery time above) — so a fix over its
+budget is said loud, naming its longest phase, and clears at the next fix of its class delivered within budget.
+The delivery budget stays as written: a measure inside the fix budget, not replaced by it.
+
 **What changes in the walk.**
 
 - **A lone merge is cut at once**: no batch assembling, and no member of its delivery group still unmerged.