history-hygiene

To keep decision logs accurate for cold reads, record only confirmed final outcomes in history.md rather than intermediate requests. This prevents future agents from acting on reversed decisions or stale records.

Agent workflows execute reversed decisions when history.md contains intermediate states instead of final outcomes. Updating history entries immediately after a reversal ensures downstream spawns rely on a single consistent source of truth.

The best way to maintain documentation hygiene during midstream changes is to wait for confirmation, then rewrite the history.md entry to capture the corrected final version as the single authoritative outcome.

To update history.md after a reversed implementation choice, ask the AI to review the proposed update and rewrite it immediately to replace the reversed decision with only the confirmed final outcome.

You need to enforce confirmation-before-write for decision logs whenever agent-driven workflows rely on history.md for prior truths, ensuring intermediate states never become durable facts that mislead downstream spawns.

Yes, applying process discipline prevents intermediate requests from becoming durable facts by requiring confirmation before writing to history.md, ensuring future agents only read confirmed final outcomes.