Document what shipped

A decided design is not a shipped one. That sentence is the whole skill, and it is in the name because it is the thing a session forgets at exactly the wrong moment - when a decision record, a plan or an ADR describes the behaviour so clearly that reading the running system feels like a formality.

It is not a formality. The draft this method replaced said the reject link "asks for a reason from a short list and closes the quote as lost". True in the decision record. Untrue in the product: the link opened a page saying an Agent would be in touch, and closed nothing. Two more claims in the same draft were false the same way, and one claim written by the agent doing the measuring was false too - "nothing notifies the Agent", written after reading the C# only, while a CRM workflow had been sending that email all along, 16 seconds after the press.

So the deliverable is not a document. It is one page whose every sentence a person can check, plus the record that says how each sentence was checked.