history-hygiene

Prevent stale decision history by logging only the final confirmed outcome to history.md, replacing prior intermediate entries. This ensures future agents read a single authoritative truth instead of outdated or reversed decisions.

The best way to maintain an audit trail after a reversal is to update history.md immediately with the new final state. This overwrites the previous entry to keep the decision-tracking file synchronized with actual outcomes.

Recording final outcomes to history.md improves incident response by providing a single source of truth. It prevents future agents from reading intermediate states or reversed decisions, which avoids repeating past mistakes during audits.

Enforce final-state logging for team collaboration documentation whenever a decision is confirmed or reversed. This practice is necessary in software projects, incident reviews, and audits to ensure the history file reflects the actual current truth.

Yes, you can use history.md as a single source of truth for decision tracking in software projects. By maintaining one authoritative history entry per decision, you ensure all downstream agents and team members read the correct final outcome.

Intermediate decision logging causes problems because future agents read history files cold. If stale or incorrect intermediate entries are not replaced by the final outcome, agents base their decision-making on poisoned or reversed truths.