OPS.6:7 - Conformance Checklist

• The exact case subject, configuration, horizon, and served demand or commitment are named.
• The required current permission is supported for the same matter and conditions; admission alone is not treated as that permission.
• Current case state, domain Method, obligations, commitments, evidence, and exception are recovered.
• The deciding System, responsible performer, permission, capability, assignment, and authority remain distinct.
• Available actions, selected action, actual Work, records, evidence, and state claims remain distinct.
• Direct mandatory or recognition branches are used when adequate.
• C.11 is used only when several admissible live actions genuinely require comparison.
• The continuation contract names Work, performer, conditions, stop or fallback, expected evidence, refresh, and return.
• Case progression is reported only after independently supported Work and adequate resulting evidence.
• A plan, ticket, model output, episode, trace, or record update is not treated as progress by itself.
• The result is either evidenced progression or an exact unmet-condition return with owner, fallback or stop, and retry.
• Specialist and wider Operations results remain with their owners.