SYSE.27:7 - Conformance Checklist

• Actual consumers and their relied-on behavior are identified at the grain that can change the decision.
• Internal change, extension, adapter, break and refusal are compared by effects rather than labels.
• Contributors can exercise the supported interaction and understand a rejection.
• Compatibility examples include meaningful old use and relevant adverse conditions.
• Technical acceptance, actual assignment, permission and deployed configuration remain distinct.
• Migration, outside-provider decisions and missing specialist Methods receive their exact returns.