Bi-temporal Memory.

Bi-temporal memory records every fact against two separate timelines: when it was true in the world, known in data modelling as valid time, and when the organization came to know it, known as transaction or knowledge time. Timer calls these its two clocks and applies them to an organization's decisions, commitments and agreements rather than to rows in a database.

The difference matters whenever the two dates diverge. A price is agreed on 3 March but only reaches the finance team on 20 March. A policy is reversed in May, yet the memo that announced it still reads as current. With both clocks, the memory can be read as it stood on any past date: what was true, what the organization knew at that moment, and what replaced it later. A correction adds to the record instead of overwriting it, so the question an auditor, a board or a new hire actually asks, "what did we know when we decided?", has an answer on the record rather than in someone's recollection.

Not a Timer coinage. Valid time and transaction time are long established in data modelling, where bi-temporal records are standard practice for financial, legal and regulatory data. Timer applies the idea to organizational memory, to what an organization decided, promised and agreed, and calls the two timelines its two clocks.