history-hygiene

To maintain an accurate audit trail during decision reversals, update history.md immediately when a decision changes, replacing previous entries with only the final confirmed outcomes to preserve a single source of truth.

The best way to log final outcomes to history.md is to write only confirmed final results after the decision process concludes, excluding all intermediate requests and reversed decisions from the file.

Recording intermediate requests in history logs confuses future agents because it pollutes the record with abandoned steps, obscuring the single source of truth needed for reliable downstream decision-making.

Yes, you can use history.md as a single source of truth for team collaboration by ensuring that only final, confirmed outcomes are written, which provides future agents with a reliable record for audits.

You need to update history.md entries immediately when a decision reverses during a multi-step process, ensuring that only the final confirmed result is written to maintain an accurate audit trail.

Yes, writing only final outcomes to history.md works for multi-step audits across team spawns by ensuring that future agents rely on a single, trustworthy truth rather than confusing intermediate requests.