Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:40:20 UTC

OPS.6:0 - Use This When

Use this pattern during one admitted continuing case when current facts, an exception, or a changed condition makes the standard next action uncertain. Typical cues are “the normal route no longer fits”, “the ticket moved but nothing changed”, “the model recommends a fix”, “we are waiting for one more result”, or “who may act now?” while the case subject, permission, performer, evidence, and next permissible Work are unclear.

The first useful result has one of two forms:

Progression: for case subject S in qualified state Q at configuration and horizon H, matching permission P and domain Method M support next Work W by responsible performer R, with stop or fallback F and expected evidence E; after independently supported performance, report the progressed state Q' and its evidence to the participant responsible for the next operating decision under return conditions N.

Blocker: condition K is missing, stale, contradicted, unauthorized, unsafe, unsupported, or unavailable; the result needed from source O is specified; the safe fallback or stop is F; reconsider when T makes that useful.

Recognition concerns a next action left uncertain by current case facts. Before action, assurance establishes the needed permission and performance conditions. After action, any progression claim needs performance evidence and support for the reported state.

Do not use OPS.6 to design one universal workflow or case lifecycle, reconstruct a reusable Method from event data, infer progress from a ticket, plan, model, trace, or record update, or revise priority merely because the case is old. Use A.15.7 for the general situation-responsive next-action Method, A.3.1.MR when reusable Method recovery from several performances is the actual question, and OPS.7 when temporal or consequence evidence can change priority or an existing commitment.

OPS.6:0.1 - Working Distinctions

Name used hereMeaning
caseOne bounded continuing Work situation organized around an exact subject, state, commitments, evidence, authority, and permissible next Work. It is not its file, ticket, queue position, or every Work item within it.
case subjectThe patient, incident, user issue, release candidate, service relation, request, physical item, or other identified subject around which continuation is being coordinated.
case-state claimA qualified claim about the case subject and relevant relations at a stated time or horizon. Revise it when warranted by new evidence, a corrected interpretation or a change in its conditions of use.
exceptionA fact or condition for which the standard continuation branch is absent, contradicted, no longer adequate, or requires bounded choice or return. It is not automatically an error or rare event.
matching admission and permissionThe applicable case admission and independently supported current permission for the same matter, effective conditions, configuration, and horizon. A valid OPS.5 result may carry both; admission alone is not permission.
deciding SystemThe System authorized to select or confirm the next permissible Work. It may differ from the responsible performer.
responsible performerThe System assigned and capable for the selected Work under its conditions. Assignment, capability, permission, authority, and performance remain distinct.
next permissible WorkThe exact Work that may occur next under the applicable domain Method, permission, obligations, evidence, and stop conditions. A task description or tool call alone does not show that this Work was performed.
action choiceA selected next Work, probe, fallback, stop, or return. Choice does not perform the Work or progress the case.
Work occurrenceDated performance admitted from direct evidence under the relevant configuration. Intention, assignment, invocation, trace presence, or artifact creation does not establish it alone.
evidence expected from performanceThe observations, produced results, or records needed to judge what occurred. State the claim each supports, including any claim of a changed subject state or a failure.
record updateA change to a ticket, case file, plan, model, trace, database, or dashboard. It may carry evidence but is not the case-state change by itself.
unmet conditionThe exact missing, stale, contradicted, unauthorized, unsafe, unsupported, or unavailable condition that prevents a truthful next action or progressed state, together with its return or stop.
progression resultEither an evidenced progressed case state with its next return, or an unmet-condition return with owner, fallback or stop, and retry condition.