OPS.1:7 - Conformance Checklist
- The opening names a first user, operating decision, horizon, and useful stop.
- The operating System has a supported boundary; materially different plausible candidates are resolved when they affect the choice, or the result returns to the appropriate subject pattern.
- The continuing result or service names its receiver and conditions without declaring value, quality, safety, acceptance, or fulfilment by wording.
- Demand, commitments, admitted Work, subjects, records, and units remain distinct.
- Every decision-bearing commitment names parties, content, conditions, horizon, authority, status, and evidence limits.
- Every counted or tracked unit has an identity rule and receiving use.
- The boundary names included Work and relations, consequential exclusions, any needed specialist results and any evidence or authority gaps.
- A control concern is recorded only when it can change the decision; no diagram or controller label establishes it.
- Any still-needed contribution is explicit; a maintained or reused focus states the changes that would require revision.
- A changed focus is checked against known uses of the changed field, and affected participants can recover the needed revision or continued use.