OPS.16:7 - Conformance Checklist

• The operating System, use, difficulty, receiving decision, decision maker, horizon, and protected conditions are explicit.
• The starting branch names either an exact admitted U.Method and relied-on version or U.MethodDescription, or an exact A.3.1.MR candidate account with source support, real rivals, gaps and explicit non-admission. A distinguishing question is required only when it changes the receiving use.
• For a selected trial, the bounded hypothesis, current alternative, material change or branch, stop and decision-changing observation preserve every Method or candidate status; a supported current candidate account does not create that trial.
• The trial uses applicable resource and service results; OCE.11 is selected for coexistence around an organization change. Conditions needed for the trial hold when its dependent Work starts; a conditional plan preserves any remaining gap.
• A selected trial’s WorkPlan names intended tasks, proposed performers, expected admitted constituent Methods, supports, observations, burdens, protections, stops, hand-back and later use without claiming actual Work.
• Every actual Work occurrence has actual performers, enacted admitted Methods, extent, containing System, departures, and direct results. No candidate whole or candidate account is enacted.
• Operating, service or reliability, human-condition, queue or constraint, financial, side-effect, burden, missing-evidence, and Method or description observations retain their direct subjects and uses.
• Coherence, fit or transfer, worth, evidence reliance, measurement validity, temporal window, and causal reach are qualified only where the receiving decision needs them and through their current owners.
• Alternatives use the same operating basis, preserve protected conditions, carry uncertainty, and remain within named authority.
• The return uses the permitted branch vocabulary, exact use, evidence window and limits, and relevant repertoire, lineage and reopen consequences. A next observation belongs only to a selected further inquiry, not to every completed account revision or stop.
• A board, prompt, tool, description, support, or local departure changes Method identity only when reusable Method semantics changed under A.3.1.
• The result claims no organization-wide adoption, cultural selection or retention, causal superiority, new capability, or authority outside its boundary.