We optimize for clarity and operational usefulness.

Guidelines:

• Lead with concrete outcomes, not slogans.
• Include dates, versions, and impacted surfaces.
• Prefer examples readers can run or verify.
• If there is risk, say it explicitly and include mitigation.
• Keep ownership clear: who should act next.

When in doubt, write for the person debugging this six months from now.