history-hygiene

To keep decision history logs accurate when outcomes are reversed, update history.md by replacing earlier entries with the final confirmed decision. This ensures future agents read the true current outcome instead of stale intermediate states.

Stale decision history poisons downstream agent workflows because future agents read these logs cold and assume they reflect truth. If intermediate requests or reversed decisions remain, agents repeat mistakes based on incorrect past outcomes.

The best way to record final outcomes in markdown history files is to log only the confirmed final decision. Wait until confirmation before updating history.md, ensuring the file reflects one single truth rather than iterative states.

You do not need to cross-reference multiple files to track version-control decisions if history.md is updated on reversals. Replacing earlier entries with the true current decision maintains a single source of truth for future readers.

You should not use intermediate state logging for record-keeping when iterations or reversals occur in a decision workflow. Logging unconfirmed requests risks leaving incorrect entries that mislead future agents reading the history cold.