OPS.7:0 - Use This When

Use this pattern when age, time remaining, a promised horizon, dependency change, new risk or consequence evidence, a progressed case state, or an unmet condition can change current priority or an existing bounded operating commitment. Typical cues are “this is old, so put it first”, “the deadline means we must release”, “the queue score escalated it”, “the patient has waited longest”, or “the issue is urgent” without a named consequence, authority, commitment, or decision horizon.

The first useful result is one bounded priority-and-commitment disposition:

For exact subject or case S in qualified state Q, temporal claim T, existing commitment C with parties, conditions, horizon, and commitment authority A_C, and decision-bearing dependency, risk, consequence, recovery, and evidence E, current priority is P for coordination use U under priority authority A_P; commitment disposition is K when it changes; immediate coordination action or truthful blocker is N; affected parties, effective horizon, evidence limits, and next review are explicit.

Name the Systems holding A_P and A_C; the same System may hold both. Record any missing required authority in blocker N.

Recognition is cheap: enter when a temporal or consequence fact can reverse a current priority or commitment decision. Assurance is stronger: state, age, rate, trend, urgency, priority, queue rank, clinical triage, legal or safety permission, and commitment authority remain separate claims.

Do not use OPS.7 to sort every queue by age, create a universal urgency scale, identify the current constraint, size capacity, design service levels, perform clinical triage, authorize release, or establish a credible whole-service commitment account. Return those results to OPS.8–OPS.13, OPS.18, or their specialist owners. Use C.27 only when the claim concerns intervention-sensitive rate, rhythm, recovery, or regime change; ordinary state, age, rate, or trend readings do not require it.