Reliability
Recovery and lifecycle
Accepted work, cancellation, recovery, and deletion need separate rules.
Why it helps
Commercial state must not silently change historical meaning.
Durable acceptance creates an obligation
The north star is that accepted work is not silently forgotten because commercial access later changes. The planned lifecycle separates new acceptance, processing already accepted work, reads, export, downstream publication, deletion, and cleanup.
Incomplete stays visible
- 1PendingAccepted work is not fully published yet.
- 2StaleA published view is older than its declared freshness boundary.
- 3UnavailableRequired history cannot currently be served.
- 4Expired or deletedRetention and customer deletion are explicit states, not empty success.