SIE.2:7 - Conformance Checklist

• Every included source can change a named contract position.
• Source asset, carrier, local scheme, semantic endpoint, identifier, claim, data item, and referent remain distinguishable.
• Edition, profile/module, effectivity/configuration/interval, and local extensions are explicit where load-bearing.
• Definitions or operative rules include scope and at least one discriminating example or counterexample where ambiguity matters.
• Identifier scheme, issuer/owner, grain, interval, restrictions, and resolution assumptions are explicit.
• Claims retain provenance, scope, time, status, and uncertainty without treating provenance as truth.
• Meaning, identifier, authoritative-value, extension, access, and receiving-use authorities remain separate.
• Every row has an adequate, conditional, unresolved, obsolete, inaccessible, missing, or model-gap disposition.
• Consuming rows and reopen conditions are recoverable.