SIE.9:7 - Conformance Checklist

• The interface is tied to one named receiver, Work, request, and next action.
• The form is chosen for receiving use rather than copied from internal realization.
• Request identifiers, schemes, configuration/effectivity, windows, units/codes, and permissions are explicit.
• Response claims state meaning, grain, scope, interval, source identifiers, loss, and permitted use.
• Qualified, unmatched, incompatible, unresolved identity, conflict, non-comparability, stale, inaccessible, source-error, and partial branches remain distinguishable where applicable.
• Source/edition, observation/retrieval time, rule versions, derivation/trace, and freshness are recoverable.
• Protection, disclosure, and authority assumptions are explicit; the interface grants no unstated authorization.
• The receiver can return a defect or gap to a specific source, semantic premise, mapping, implementation, or decision owner.
• Action-sensitive latency, availability, snapshot, and volume behavior are stated without claiming unobserved performance.
• Representative requests, responses, errors, compatibility/deprecation behavior, and reopen conditions are present.