How do retention clocks start if nobody sets them?

Retention schedules fail at the beginning rather than the end. If the triggering event was never captured, the clock never starts and the record is kept forever by default — which is how organizations end up with a documented policy and an estate that grows indefinitely.

Because Centralpoint infers record type and triggering dates at ingestion, clocks start without anyone selecting a category. Disposition then operates on the record with its version lineage and derived artefacts, so executing the schedule reaches interaction logs, cached answers and index membership rather than stopping at the document itself.