CMP.15:7 - Conformance Checklist
- The data variants, operation meanings and admitted receiving uses determine the required combinations, including nested forms and dependent operations.
- Every required new intersection has an obtainable body or an explicit unsupported-use boundary; its supplier understands both sides.
- Generic derivation is justified by the operation’s meaning, with binding, control or identity distinctions retained where material.
- The composition defines selection, reports missing support and rejects or resolves conflicts without accidental loading-order semantics.
- Recursive and dependent calls reach the implementation selected for the composition.
- Unchanged sources, separate checking and compilation, early coverage and behavior preservation have distinct stated grounds.
- A semantic counterexample can distinguish a present, uniquely selected but wrong body from a correct one.
- Old-use preservation covers the promised observations and assumptions; a new form below an old constructor is exercised separately.
- The full cost is compared with an adequate closed alternative, and a changed required pair or binding condition has a clear return.