Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Name the observed fact
Specify start, attempt, validation or confirmed receipt, with emitting component and timing. If storage and notification differ, define which confirms receipt and how later failure is represented without erasing what occurred.
Define a minimum contract
Use needed request ID, language, form type and test marker; exclude unnecessary personal properties. Specify retries and operational-record linkage. Version allowed values so changes do not silently break comparability.
Validate three outcomes
Example: saved, rejected and unknown network outcomes. Count only verifiable receipt and reconcile unknowns. Test double submission and reload. Events must reconcile by ID, with failures distinct from opportunities and discrepancies visible.
Key takeaways
- Define receipt, identity and duplicates before counting conversion.