history-hygiene

To prevent stale decision logs, record only the final outcome to history.md after confirmation. This ensures future agents read a single truth rather than intermediate requests or reversed decisions that no longer apply.

Incorrect decision tracking occurs when history files log interim requests instead of final outcomes. Update history.md entries immediately when decisions are reversed so future agents read the actual final state rather than outdated requests.

The best way to maintain a single source of truth is to wait for confirmation before writing to history.md, then update the entry whenever a decision changes. This prevents readers from cross-referencing multiple conflicting sources.

Write to a history log only after a decision is finalized and no longer subject to change. Waiting for confirmation prevents premature entries that would need correction if the decision is later reversed.

Yes, you can and should update history entries when decisions are reversed. Recording the ultimate decision to history.md ensures that future spawns read the correct final state rather than the stale original entry.

Yes, this approach suits team collaboration audit trails by ensuring record-keeping reflects the ultimate decision. History entries capture one truth per outcome, preventing downstream agents from acting on incorrect or stale information.