SUMMARY: A review clock is a visible trigger that tells operators when a record, rule, or decision needs to be checked again.
Most stale systems were once reasonable. A page was accurate. A chat room had a purpose. A moderation rule matched the threat. A headline source fit the mix. The problem is not that conditions change. The problem is that nothing tells the next operator when to look again.
The review clock turns maintenance from memory into infrastructure. It does not guarantee that a decision changes. It guarantees that the decision is not allowed to age silently.
Clock Types
Date clock: review this page, room, rule, or module on a scheduled date.
Event clock: review when a plugin updates, a new user pattern appears, a policy changes, or a threshold is crossed.
Volume clock: review after a number of messages, posts, reports, edits, or failed attempts.
Owner clock: review when ownership changes or when no active owner can be named.
Where to Use It
Use review clocks on forum entry rules, chat room purpose, gallery series, headline news sources, security hardening notes, and recurring moderation patterns. They reduce signal overhang by making age visible.
Operator Rule
If a decision can expire, give it a clock before it becomes invisible work.
Field assessment: maintenance begins when the future has a reminder.