SIE.7:7 - Conformance Checklist

• Every rule names a receiving output claim and use.
• Source and target schemes, editions/profiles, meanings, units, codes, and identifiers are exact.
• Accepted correspondence premises and any relied-on identity or composition premises are referenced rather than re-decided in code.
• Selection, joins, filters, windows, effectivity, duplicates, and missing inputs are explicit.
• Transformations, conversions, external lookups, and their authority are explicit.
• Cardinality, split/merge behavior, and source-identifier preservation are specified.
• Absent, unknown, not applicable, inaccessible, stale, incompatible, unresolved, source failure, zero, and empty values remain distinguishable where relevant.
• Defaults have a semantic warrant, accepted loss, and test.
• Information loss, forbidden reuse, provenance, and input-output trace are inspectable.
• Positive, boundary, negative, and unlike cases define observable implementation conformance.
• The specification claims no running pipeline, service level, or receiving-use validation.