The lifecycle of a stored decision seems like an important fourth question alongside where it lives, who reads it, and what it remembers. A rationale can be perfectly accurate when written and still become misleading after the architecture, dependencies, or business constraints change. At IT Path Solutions, we’ve found that durable context becomes much safer when the agent can distinguish between an active decision, a superseded one, and a decision that needs revalidation before reuse. That could make the “why” layer more than historical documentation—it becomes a piece of context with its own validity state. Otherwise, preserving the reasoning can solve one problem while quietly creating another: an agent confidently applying yesterday’s correct reasoning to today’s different system.