history-hygiene

To log only final decisions and prevent intermediate requests from polluting the audit trail, record confirmed conclusions directly to history.md while skipping unconfirmed intermediate states. This approach ensures a single, authoritative source of truth for team governance.

The best way to maintain an authoritative decision log for team collaboration is to record final outcomes to history.md. This practice prevents duplicating or contradicting past entries and avoids audit trail noise from unreconciled reversals.

Recording final state to history.md handles reversals in project governance by applying immediate updates to reflect the actual outcome. It enforces logging confirmed conclusions, ensuring the history remains an accurate and reliable source of truth.

You need to update history.md during incident retrospectives when a decision is confirmed or when a reversal occurs. This ensures the log reflects the actual final outcome rather than intermediate requests or unreconciled states.