Captured content lifecycle

The Lifecycle

Transitions Explained

Request and response capture progress independently. Admission refusals leave both pending. Capture failure is recorded without guaranteeing evidence exists. Purged can be a read-time answer while the row still says captured; deletion of an organization removes its dependent rows before its object versions.

What Cannot Happen

The database requires an object reference for captured status. The runtime provides no capture retry or restore flow, but the metadata writer does not enforce a formal transition graph.

Concurrency and Timing

The body and its reference are separate writes. The retention timestamp and ninety-day bucket policy express the same configured duration but do not establish simultaneous expiry. Noncurrent-version expiry is measured separately by object storage.