Persistent

Durable artifacts like notes, ledgers, and databases carry state so it stays current and retrievable over time.

A colleague asks how the vendor negotiation stands, and you realize the answer exists only as a smear across your memory: half a number from a call, a concession mentioned in some email, a deadline you are pretty sure is the 14th. Every time anyone needs the current state, you reconstruct it from scratch, slightly differently each time.

PERSISTENT names durable artifacts, notes, checklists, ledgers, databases, records, calendars, versioned files, as a carrier space for cognitive work. What it is best suited for is holding state: facts and status that must stay current, retrievable, and identical for everyone who consults them. The cue to route work here is exactly the reconstruction ritual above, or its sibling, two people acting on different versions of the truth. The operation: create one artifact as the canonical home for the state (a single negotiation page with current terms, open questions, and next deadline), update it at the moment things change rather than later, and point every question at the artifact instead of at your recall. What changes is that "where does this stand?" becomes a 10-second lookup with one answer, and your memory is freed for thinking rather than storage. The boundary: an artifact holds state but exercises no judgment, so decisions, interpretation, and anything requiring presence should not be routed here, and an artifact nobody maintains becomes confidently wrong, which is worse than absent.