Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Decision and method
Distinguish received, validated, processed and applied to the business. A technical response may acknowledge transport without proving that an order exists or is usable. Define what each message confirms, which reference it preserves and how later status can be checked. State names should reflect available evidence rather than optimistic expectations.
Illustrative example
Illustrative example: the receiver accepts a file and returns a batch reference. Later it processes 98 of 100 records and rejects two. The sender shows batch received, then a partial result with details. It does not announce 100 created orders when the first response only confirmed arrival of the uploaded file.
Acceptance check
Test lost acknowledgements, partial outcomes and repeated status checks. Verify that each record reaches an explainable state and retries preserve identity. Accept when someone can trace the path from sending to confirmed effect, including failures that occur after technically successful receipt but before the intended business operation has actually completed.
Key takeaways
- Confirm only the stage supported by evidence and preserve tracking through the final outcome.