What should a useful publishing incident note contain?

Capture the intended action, the confirmed result, the affected account or job identifiers, the timeline and the point where expectations diverged. Distinguish observed facts from hypotheses. Include the immediate correction and the systemic change, if one is justified.

Avoid turning one incident into a broad product rule without checking its scope. A useful note lets another operator recognize the same failure and know what evidence to collect. Keep private customer details out of any public version of the lesson.