The idea
Accepted, stored, processed and delivered describe different states. A positive acknowledgement is only useful when both sides agree which state it confirms. Confusing receipt with completion can make a dashboard look successful while work is still pending.
Design choice
Choose the acknowledgement boundary according to the consequence of loss. If completion is asynchronous, provide a way to inspect the final outcome. Document whether a consumer acknowledges before or after committing its own changes.
Worked example
A report service immediately returns an accepted job identifier. A separate status resource records finished or failed; the first response does not claim the report exists.
Before you ship
- Name each lifecycle state
- Align acknowledgement with durable work
- Expose a final outcome
Examples are illustrative. Adapt the checks to your own environment.