OPS.1:4.1 - Pattern-Use Unfolding

1. Name the first user and decision. State who needs the focus, what decision it enables, the relevant horizon, and the first useful result or honest blocker.
2. List materially different operating-System candidates. Consider the whole organization, a service operation, production cell, development operation, hospital function, supply relation, personal operation, product or asset, and coordination software when each is plausible. Use A.1.SCR only when System identity changes the decision; otherwise name the actual subject and leave through its pattern.
3. State the continuing result or service. Name its receiver, conditions, horizon, and the observation that would show interruption or degradation. Keep value, quality, acceptance, fulfilment, safety, and causal effect as separate claims.
4. Recover demand and commitments. Distinguish requests and candidate Work from admitted Work. For each decision-bearing commitment, name parties, promised result or service, conditions, horizon, authority, current status, and evidence gap.
5. Name operating subjects. Identify the customers, cases, physical items, release candidates, incidents, transactions, materials, services, accounts, or other subjects whose state or relation changes action.
6. Define every tracked unit. State the unit’s identity rule, start and finish when it is a Work item, subject/result relation, counted interval, and receiving use. Do not call every unit a flow item merely because a board counts it.
7. Draw the operating boundary. Include only the Work, resources, relations, environments, and time horizon needed by the decision. Name excluded product, organization, asset, finance, legal, safety, capability, and other specialist questions with their return conditions.
8. Check the control branch. If observation, decision, actuation, supervision, feedback, or rate separation can change coordination, record the control-relevant operating concern for OPS.2. Do not construct a control view or infer a feedback relation here.
9. Recover authority and evidence limits. Name who may use the focus for which decision, what evidence supports it, what remains uncertain, and which missing fact blocks reliance.
10. Return, dispose, and reopen. State the selected operating focus, rejected candidates, next pattern, truthful stop, and one observable change that reopens the boundary, commitment, subject, or unit. When a change reopens any focus field, list the known downstream views, accounts, policies, and later decisions that consumed that field; mark each recheck, still usable, or return, and give the decision-local reason. Leave an unrelated consumer intact.