Timestamp beliefs with validity windows — convert apparent time-based contradictions into explicit version transitions

Why This Is a Rule

Many apparent contradictions in a knowledge system aren't contradictions at all — they're temporal transitions. "Remote work reduces productivity" (your 2020 note) and "Remote work increases productivity" (your 2023 note) seem contradictory until you add validity windows: the first applied during the chaotic early pandemic transition, the second after organizations adapted their processes. Both were true in their time period. Without timestamps, they look like a confused mind holding contradictory beliefs; with timestamps, they look like documented learning.

Validity windows transform your knowledge system from a snapshot of current beliefs into a versioned history of understanding. This serves three functions. First, it eliminates false contradictions: beliefs that seem opposed but actually apply to different time periods. Second, it preserves epistemic history: you can trace how and when your understanding evolved, which is itself a valuable knowledge artifact. Third, it prevents premature deletion: instead of removing an "outdated" belief, you mark its validity window, preserving it as historical context for the current belief.

This is version control for beliefs — the same principle software engineers use for code, applied to knowledge.

When This Fires

• When you notice your knowledge system contains beliefs that seem to contradict each other
• When updating a belief based on new evidence — mark the old belief's validity window rather than deleting it
• During knowledge system audits when cleaning up apparent contradictions
• When referencing historical beliefs to understand how your thinking evolved

Common Failure Mode

Deleting old beliefs when you update your understanding: "I used to think X, but now I think Y — delete X." This loses the historical context. If you later encounter evidence that supports X under certain conditions, you've destroyed the note that would have helped you understand the scope boundaries. Keep X with a validity window; add Y with its own window. The contradiction resolves into a documented transition.

The Protocol

(1) When adding a belief to your knowledge system, include a "valid from" date (at minimum). (2) When a belief is superseded, add a "valid until" date and link to the successor belief with an "updated by" or "superseded by" edge. (3) When two beliefs appear to contradict, check their validity windows first. If they don't overlap → temporal transition, not contradiction. Label accordingly. (4) If validity windows overlap → genuine contradiction requiring resolution (Link contradicting ideas together in your graph — spatial proximity forces the confrontation that compartmentalization prevents, Use the cascade test — 'If I resolved this, what else changes?' — to distinguish surface from deep contradictions). (5) During audits, identify undated beliefs and add validity windows retroactively based on when the source material was created or when you acquired the knowledge.