Rendered from docs/obligations/0204-docs-decisions-0077-still-describes-hw-dr-0049-s-rewrite-as-pending-after-574-made-it.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

docs/decisions/0077 still describes HW-DR-0049's rewrite as pending, after #574 made it

Context

HW-DR-0077 narrows HW-DR-0049. Its Consequences section says of HW-DR-0049: "That record is a draft, and its acceptance carries the rewrite of that sentence." #574 moved HW-DR-0049 to status: current on 2026-09-23 and rewrote the sentence HW-DR-0077 pointed at, in the same change. HW-DR-0077 was out of #574's named scope, so nobody returned to update its own sentence, which now describes as pending an event that already happened.

Obligation

HW-DR-0077's Consequences section states, about HW-DR-0049, a future event as still open. The sentence needs the same kind of correction #574 already made to HW-DR-0049 itself: state that the acceptance and the rewrite happened, and name what changed.

Discharge

This discharges when a session next touches HW-DR-0077 and rewrites the sentence to describe HW-DR-0049's acceptance and rewrite as done, or when a reader confirms HW-DR-0049's current text already covers what the sentence promised and HW-DR-0077 is corrected to say so.

#1070 amended HW-DR-0077 and rewrote the sentence. It now says that #574 accepted HW-DR-0049 on 2026-09-23 and rewrote its sentence about an adopter. So the work that this record owes is done. The obligation lifecycle admits discharged only from current, and this record stood at draft. So #1070 moves it to current, and the next change that touches this record moves it to discharged.

This record is discharged. The paragraph above states that the work is done, and this change makes the move that it names. The owner accepted the discharge on 2026-09-30, in the roadmap review of that day.