SYSE.36:7 - Conformance Checklist

• The subject, users, configuration and task class are named.
• The responsible owner supplies the good-result meaning.
• Eligibility and good outcome are defined independently of the convenient telemetry.
• The implementation is exercised against good, failed and missing-observation cases.
• Material pre-backend failures, retries and incomplete outcomes are accounted for.
• The objective and response policy are agreed on a consistent event/time basis.
• Platform and application results remain separate even when they share infrastructure.
• A reliability measure is not presented as complete user value or release authority.