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

Source changed 2026-11-16 21:18:08 UTC · snapshot created 2026-11-16 21:19:40 UTC · last check 2026-11-17 19:15:10 UTC

Part III — Admit Demand and Continue Cases

OPS.5 - Admit Work and Limit Starts

Status: Stable

OPS.5:0 - Use This When

Use this pattern when you must decide which eligible demand to admit now under the authority and start limits in force. An item can look ready before the conditions for its start are met. Typical cues are “pull the next item”, “approve this case”, “the card is top priority”, “the agent is free”, “the rig has an opening”, or “we already selected it” without a current admission decision, start permission, or explicit start limit.

The first useful result is one bounded admission account:

For eligible demand D serving operating result or commitment R, under criteria and non-negotiable conditions K, explicit-start limit L, deciding authority A, configuration and horizon H, each considered item is admitted, deferred, rejected, or returned; an admitted item has effective start conditions and an authorized starter where one exists; identify any residual demand and the next review or return that is needed.

Recognition asks whether this demand may enter now. Assurance establishes its admission criteria, start permission and effective bound; any later performance or fulfilment claim needs its own evidence.

Do not use OPS.5 to design a queue or buffer policy, identify or exploit the current constraint, size capacity under variability, coordinate interacting structures, or make a whole-service commitment credible. Use a relevant result from OPS.8–OPS.13 or a qualified direct source. When that result is missing, identify the question for its provider. If the current problem is continuing an already admitted case after facts changed, use OPS.6. If age, dependency, risk, or consequence may revise priority or an existing commitment, use OPS.7.

OPS.5:0.1 - Working Distinctions

Name used hereMeaning
eligible demandAn identified demand item, such as a request, need, condition, case, or candidate Work item, that may be considered for current admission. Identify the demand claim and the subject it concerns separately. Eligibility makes it a candidate for this decision, not a permitted start.
option or requestA possible demand item presented for consideration. Its presence in a list or account creates no right to admission.
admission decisionA bounded decision about whether an identified demand item may enter the selected current coordination account under stated criteria, limits, horizon, and authority.
admitted itemEligible demand whose admission conditions obtain for the stated configuration and horizon. Admission permits a further start decision under its conditions; it does not establish start or result.
deferred itemDemand not admitted now, with the observation, condition, horizon, or changed fact that would make reconsideration useful.
rejected itemDemand declined for this operating use, with its reason and any receiving return that another owner can answer.
returned itemDemand for which a named missing, stale, unsupported, or externally owned condition prevents this admission decision.
start permissionAn obtaining permission or authorization for the admitted matter under effective conditions. A comparison or selected answer is not permission unless the deciding System also has and exercises the required authority.
explicit-start limitA stated bound on what may be started now for this operating use. Identify the unit, period and counting rule for this limit.
commitmentA promise or obligation with parties, content, conditions, horizon, authority, and status. Admission can rely on or create a bounded commitment only where the relevant authority is present.
authorized starterThe System permitted to initiate the admitted Work under the effective conditions. Responsibility, capability, availability, and permission remain separate.
Work occurrenceDated Work whose occurrence is established from performance evidence, independently of the demand-admission decision. Use a card change, approval, plan, invocation or artifact as evidence only for the Work it actually records.
residual demandEvery considered or still-relevant demand item not in the admitted set, with enough identity and disposition to avoid hidden starts or silent loss.
admission resultThe dispositions, reasons, conditions, authority, horizon, starter relations, residual demand, and next review or return that make the admission decision usable.

OPS.5:1 - Problem Frame

Continuing operation may receive more apparent demand than it can start under its commitments and operating limits. Requests arrive through customers, incidents, clinical cases, release candidates, providers, planned changes, automated agents, and internal commitments. Each item may be valuable, urgent, visible, or technically ready while still lacking the identity, evidence, permission, access, authority, or explicit-start condition required now.

Decide which demand can enter current operating coordination. Keep the remaining demand visible and distinguish admission from evidence that Work started.

OPS.5:2 - Problem

Boards and intake systems compress unlike truth states. “Ready”, “selected”, “approved”, “assigned”, and “in progress” become interchangeable labels. A high priority is treated as permission; an available performer as authority; a scheduled slot as capacity; a generated change as started Work; and an admission decision as a fulfilled commitment.

The opposite failure keeps every item nominally open. Nothing is explicitly rejected, deferred, or returned, so the operation accumulates hidden commitments and starts. Practitioners cannot recover which demand was considered, why it did not enter, or what would justify another look.

OPS.5:3 - Forces

ForceTension
responsiveness versus truthful startsDelay can harm service, but premature starts create hidden Work, interruption, or unsafe continuation.
common intake versus unlike subjectsA shared account aids coordination, but incidents, patients, release candidates, provider changes, and rig requests retain different identities and conditions.
comparison versus direct ruleSeveral live alternatives may need choice, while mandatory or recognition-based conditions should not be converted into an artificial option contest.
local limit versus wider policyOne explicit-start bound can close the current decision without claiming a complete queue, capacity, or constraint Method.
visibility versus authorityMaking demand and evidence visible helps, but neither visibility nor rank grants permission or commitment authority.
fast admission versus adequate evidenceA short-horizon answer is useful only if evidence currentness, conditions, and reopen triggers remain explicit.
focus versus residual demandA bounded admitted set reduces active burden, but deferred, rejected, and returned demand must not disappear.

OPS.5:4 - Solution

OPS.5:4.1 - Recover the inputs needed for admission

Name the deciding operating System, receiving result or commitment, configuration, and horizon. Reuse matching current OPS.2, OPS.3, and OPS.4 results when their account of the coordination form, subjects, relations, evidence, permissions, commitments or gaps bears on admission or its grounds. If a needed input is stale, mismatched or missing, use a qualified replacement or say how the gap limits this decision. Other admissions can proceed on independent grounds.

OPS.5:4.2 - Name each exact demand item and its proposed use

For every item under consideration, state the demand subject, claimant or source, proposed operating result, relevant commitment, and why admission is current. Keep a request, option, candidate Work item, admitted item, commitment, start permission, and performed Work separate even when one record represents several of them.

OPS.5:4.3 - State criteria, non-negotiable conditions, and the explicit-start limit

Record the conditions on which admission depends. Identify the item and what the proposed start must supply. Check its readiness, evidence, permissions, performer and access against that use. Apply the specialist conditions, commitments, capacity, resource access and concurrency or start limits relevant here.

Judge readiness for the proposed consuming operation, not for every eventual use. OPS.8:4.2 supplies receiver-ready work; OPS.13:4.2 connects preparation to a promised result. Recover the applicable prerequisites and the evidence or authorized source that can confirm them. Name the start bound’s unit, interval and counting rule, including how safe stops and suspended work count. A supplied justified bound can be applied here; deriving its value is a capacity or policy question.

Some conditions are mandatory, some admit qualified comparison, and some require a return to another owner.

OPS.5:4.4 - Choose only where a real choice exists

When a direct domain rule, mandatory condition, or recognition branch gives the answer, apply it and record the basis. When several live admissible alternatives genuinely require comparison, form a stable current OptionSet and comparison basis and use C.11. If the options or comparison facts are insufficient, choose a bounded inquiry when its attainable result could improve the decision or the grounds for relying on it enough to warrant the work. Otherwise state the missing condition and its consequence.

OPS.5:4.5 - Give every item a usable disposition

Return each considered item as:

  • admitted, with reason, effective conditions and horizon, governing authority, authorized starter where established, and the next review if one is required;
  • deferred, with the condition, observation, horizon, or changed fact that makes reconsideration useful;
  • rejected, with the reason and receiving return where another owner can answer the need; or
  • returned, with the exact missing or externally owned result, what it blocks, safe stop or fallback, and when reconsideration could be useful.

Keep the residual demand visible. Record no start merely because the item is admitted.

OPS.5:4.6 - Close the local decision and expose wider returns

State the admitted set and the current limit on starts. Identify any residual demand, its disposition and the conditions for a needed review. For questions of queue order, buffer design, constraints, capacity under variability, interacting structures, whole-service commitments or specialist judgements such as clinical triage, safety acceptance, release, law or finance, use a result qualified for this decision. If a required result is missing, return that question to its owner and identify what can still proceed.

OPS.5:5 - Archetypal Grounding — Three Admission Replays

OPS.5:5.1 - PumpWorks controller service

The following observations and permissions are constructed case inputs. At 09:00, PumpWorks has an established limit of two active engineering work packages for the 09:00–11:00 window. The staffing owner has justified this bound from available performers and protected recovery work; OPS.5 applies it without deriving a universal WIP value. A package counts from actual start until completion or a documented safe stop. Waiting demand is not counted as active. T8 is already running with engineer E17 until its expected safe completion at 09:30, so one slot is free.

Proposed workObtaining conditions at 09:00Disposition and next action
I73-D: inspect the captured incident logsExact installation and log identity confirmed; engineer E18 available; incident lead authorizes read-only diagnosis until 11:00; local copies and diagnostic procedure ready.Admit I73-D under the incident-order exception in OPS.2:5.2. E18 starts at 09:05. With T8, there are now two active packages. No live setting change or release is permitted.
R42-T9: final laboratory validationLab testing is permitted independently of field release, but the signed fixture check is missing and the rig is occupied by T8.Defer until the fixture check and rig access obtain; recheck at 09:40. An empty active slot alone is insufficient.
S19: resolve the safety questionThe operating coordinator is not the safety authority.Return the exact question and supporting material to the safety owner. Release remains blocked pending the safety decision; unrelated permitted diagnosis may continue.
P8-P: provider preparationInputs and permission exist, but it competes for E18; the resource owner confirms an afternoon review can preserve its existing obligation.Defer to 13:00 rather than silently remove it from demand. Reopen earlier if that obligation or E18’s availability changes.

At 09:25 E18 safely completes the bounded log inspection, as developed in OPS.6:5.1. One active slot is freed, but the incident case is not resolved. At 09:30 T8 completes. At 09:40 the fixture owner supplies the missing signed check; the rig owner and E17 confirm access, and the coordinator admits R42-T9. E17 starts its permitted laboratory procedure. This is a new bounded admission, not permission for field release.

At 09:50 the field contact becomes unavailable. The next live I73 verification is returned for restored access and matching permission rather than being counted as started. R42-T9’s independent lab permission and fixture evidence still hold, so that Work continues. The admission return records the permitted starts separately from the supplied observations of actual starts, with the active count at each time, the still-open S19 and I73 returns, and P8-P’s afternoon reconsideration. OPS.7:5.1 shows the resulting promise decision.

OPS.5:5.2 - Public-hospital emergency-care operation

An emergency-care operating function decides whether work on a patient’s case may start. It considers current observations, bed availability, service horizons, clinical and operating evidence, and the permissions the work requires. The qualified clinical service determines clinical priority and may use the patient’s waiting time as evidence.

If a required condition is missing, such as consent, clinical evidence, competence, a medical safety judgement, privacy protection or statutory permission, the result names that blocker and its owner. Operations neither supplies treatment authority nor overrides clinical judgement. The first useful result is an authorized operating admission or an exact returned condition, not a dashboard state or automatic triage result.

OPS.5:5.3 - AI-assisted software operation

One software operation considers user issues, agent episodes, candidate changes, harness and tool access, traces, test results, human decisions, and release commitments. The authorized decision maker uses current context and tool capacity, concurrency, integration burden and required evidence to decide what may start.

A model score, available agent, free context window, generated patch, or scheduled episode does not by itself establish admission, permission, performed Work, or release. The result admits only the exact bounded Work whose identity, conditions, evidence, access, authority, and start limit obtain; it identifies deferred and returned items with their conditions for reconsideration, and gives the grounds for any rejection. Security, software assurance, provider capability, agenthood, and release authorization remain direct specialist returns.

OPS.5:6 - Bias-Annotation

Bias or pressureHow it distorts admissionCountermeasure
visibility and rank biasThe top visible item appears authorized and ready.Test identity, evidence, permission, authority, and start conditions separately.
sunk-commitment pressureEarlier planning or public promise is used to force admission.Recover the actual commitment parties, conditions, authority, and current status.
utilization pressureEvery available person, rig, tool, or model is filled immediately.State the bounded receiving result and explicit-start limit; preserve deliberate non-start.
automation biasA model recommendation or generated artifact is treated as admission or Work.Identify the admission decision and any authorized starter. For a claim of performed Work or a later result, check the evidence for that claim.
urgency leakageAge or consequence language becomes automatic admission order.Leave priority and commitment revision to OPS.7; use only the current admission criteria here.
silent-rejection pressureDeferred or rejected demand disappears from the account.Preserve identity, disposition, reason, retry or return, and residual demand.
source-school anchoringA familiar board, backlog, buffer, or WIP rule supplies the whole Method.Adopt only the bounded mechanism that helps establish the decision or its conditions and keep its limits explicit.

OPS.5:7 - Conformance Checklist

  • The exact operating System, receiving result or commitment, configuration, and horizon are named.
  • Every considered demand item has an identity and proposed receiving use.
  • Matching OPS.2, OPS.3, and OPS.4 inputs are reused when current and relevant to admission or its grounds.
  • Admission criteria and non-negotiable conditions include relevant evidence, authority, permissions, access, specialist returns, and currentness.
  • The explicit-start limit is bounded to this use and is not presented as a universal queue, capacity, or constraint policy.
  • C.11 is used only for several real live alternatives on a stable comparison basis.
  • Every item is admitted, deferred, rejected, or returned with reason, conditions, horizon, and any review or return required by that disposition.
  • The authorized starter is named only where that relation is established.
  • Residual demand remains visible.
  • Admission is not claimed as started or completed Work.
  • Wider Operations and specialist questions return to their direct owners.

OPS.5:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternFailureRepair
top card means startRank substitutes for authority and permission.Record admission, permission, starter, and start conditions separately.
everything is “in progress”Hidden starts erase residual demand and overload the operation.Apply an explicit-start limit and give every item a disposition.
availability implies capacityA free slot, worker, rig, tool, or model is treated as a complete capability and access result.Recover the exact performer, resource relation, capability, permission, and configuration.
choose-first option setAn artificial score replaces mandatory conditions or direct rules.Use the direct branch; compare only genuine admissible alternatives.
admission by artifactTicket creation, assignment, plan, model output, or code generation becomes “Work started”.Establish whether Work occurred from independent performance evidence; decide admission and permission before the prospective start.
rejection without returnDemand silently disappears or repeatedly re-enters.Keep the reason, residual identity, owner, and retry condition.
local rule claims the systemOne start limit becomes a universal WIP, queue, capacity, or constraint Method.Bound the result and return wider policy questions.

OPS.5:9 - Consequences

The operation gains a usable distinction between demand and current starts. Participants can see what entered, what did not, why, under whose authority, for which horizon, and what should be reviewed. Hidden starts and silent residual demand become easier to challenge.

The cost is explicit identity, evidence, conditions, authority, and disposition work. Some demand remains visibly deferred or returned rather than cosmetically “active”.

OPS.5:10 - Rationale

Admission is valuable because it protects the boundary between possible demand and authorized current Work. Combining it with queue design, performed Work, or service assurance would make a locally usable decision depend on much wider results and would hide exactly where permission and evidence are needed.

The four dispositions prevent the false binary “start or lose”. Direct rules remain direct, genuine alternatives can be compared, and residual demand stays available for reconsideration or specialist return. The pattern therefore closes the smallest decision that lets a continuing operation limit starts while leaving unresolved queue, constraint, capacity, interacting-structure, and whole-service questions for their own decisions.

OPS.5:11 - SoTA-Echoing

The question is which prepared work may start now. The serious comparator is competent policy-governed pull. The Kanban Guide 2025.5 already provides explicit workflow policies and active-work control; TameFlow’s preparation account adds useful-package readiness and distinguishes optional from committed demand. OPS adopts these contributions.

Apply both approaches to section 5.1. Using a capable pull policy, the coordinator can identify the free slot, preserve the WIP bound and admit I73-D under the authorized exception. E18 then starts the work. The possible residual is narrower: the fixture readiness required for R42-T9 differs from the safety decision required for release, and the operating coordinator cannot manufacture the latter. Sections 4.3–4.6 distinguish those consuming uses, apply the existing bound and return S19 to its owner while retaining permissible work. If the incumbent’s policies and records already do this, they are the adequate admission arrangement.

The addition costs a check of current prerequisites and permission, an exact return for a missing condition, and follow-up on deferred demand. Where eligibility rarely changes and one authority already covers the operation, a separate per-item OPS form costs more without altering starts. Reuse the existing policy and item record; do not duplicate its queue history. Where multiple authorities or prerequisites differ by action, that bounded work can prevent a ready-looking item from acquiring a permission it lacks.

FPF C.11 supplies comparison among genuine admissible alternatives; it neither sets the bound nor grants permission. Reinertsen’s historical queue and economic mechanisms inform policy questions returned to OPS.8–OPS.10. No universal WIP value, service guarantee or proof of completed Work is imported. Reopen when the unit or counting rule, readiness, authority or protected capacity changes, or when the incumbent supplies the same dispositions with less total work.

OPS.5:12 - Relations

  • Use the coordination form selected through OPS.2 when admission or its grounds depend on that form. OPS.3 supplies exact operating subjects and direct relations. OPS.4 supplies current claims, evidence, permissions, commitments, uncertainty, and gaps. None of those results admits demand by itself.
  • C.11 governs comparison only when several live admissible alternatives require choice. A.10 governs evidence reliance; A.15.8 governs performance-configuration and recovery questions when they become the actual blocker.
  • OPS.6 consumes the applicable admission and independently supported current permission for the same matter and conditions; an admission account may carry both results.
  • OPS.7 separately governs current priority or bounded commitment revision. OPS.8–OPS.13 retain queue, buffer, constraint, capacity, interacting-structure, and wider commitment questions.
  • Clinical, safety, legal, privacy, security, finance, product release, capability, and other specialist practices retain their subjects, evidence, permission, authority, and conclusions.
  • Practitioners may enter OPS.5 directly when matching current inputs already exist, repeat it as demand changes, or stop after its result.

OPS.5:End

OPS.6 - Continue Cases and Handle Exceptions

Status: Stable

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.

OPS.6:1 - Problem Frame

Continuing cases do not simply advance because a standard sequence exists. New observations, dependency failures, changed permissions, resource relations, specialist decisions, or unexpected outcomes can make yesterday’s next action unsafe, impossible, or irrelevant. The operation still needs a bounded way to continue without replacing the applicable clinical, engineering, legal, safety, security, or other domain Method.

Select the next permissible Work from the current situation. Report what progressed only when the performed Work and its result are supported. When a prerequisite is missing, identify the condition that limits continuation.

OPS.6:2 - Problem

A selected workflow transition can be mistaken for performed Work or an evidenced change in the case. A case-file state, agent loop, plan update, model recommendation, or “done” ticket appears to settle the case even when no authorized performer acted or the resulting subject state is unknown.

The opposite failure treats every exception as improvisation. Practitioners bypass mandatory domain branches, create an ungoverned OptionSet, or keep analyzing without a responsible performer, stop, evidence expectation, or return. Cases then drift between records while obligations and commitments remain unresolved.

OPS.6:3 - Forces

ForceTension
responsiveness versus currentnessCases need timely continuation, but stale facts or permission can make the selected action inapplicable or harmful.
domain Method versus local exceptionThe applicable Method constrains permissible Work, yet current facts may require recognition, adaptation, comparison, probe, or return.
chooser versus performerThe System that decides may not perform; collapsing them hides assignment, capability, permission, and responsibility.
action versus evidenceSelecting a good action is useful, but it does not show that Work occurred or the case changed.
recordability versus subject truthFiles and transitions support coordination, but they represent rather than constitute the case subject and state.
automation speed versus authorityAutomated episodes can run quickly, but tool access and output do not establish permission, software assurance, release, or accountable continuation.
progress pressure versus honest blockerA visible “next state” is attractive, while naming an unmet condition may be the only truthful result.

OPS.6:4 - Solution

OPS.6:4.1 - Confirm the case and matching permission

Name the exact case subject, current configuration and horizon, and the demand or commitment being served. Recover the applicable admission and the required current permission for the same matter and conditions. A valid OPS.5 result may carry both; admission by itself does not establish permission. If the required permission is absent, expired, or contradicted, return that blocker to the authority or source that can resolve it; do not select Work or claim progression under a merely similar item, earlier approval, queue rank, or general mandate.

OPS.6:4.2 - Establish the current conditions for continuation

Recover the current qualified case state, applicable domain Method, obligations and operating commitments, the evidence for continuing and the conditions under which it is still current, relevant permissions and authority, and the condition that made continuation uncertain. Follow the claims that can change the next action, the conditions for relying on it or the conclusion the recipient needs. Reuse unaffected case claims within their established conditions.

OPS.6:4.3 - Separate decision, performance, records, and state

Name the deciding System, responsible performer, required permission or authority, available actions, Work proposed or selected for performance, records used or changed, and the state claims the result may support. Do not infer one relation from another. If performer capability, assignment, access, permission, or authority is missing, return that exact condition.

OPS.6:4.4 - Use the least elaborate adequate steering branch

Apply the direct mandatory branch when a current rule and facts determine the next permissible Work. Use recognition when one current situation clearly matches a governed action. Adapt within the applicable domain Method when a bounded variation is authorized. Use C.11 only when several admissible live actions genuinely require comparison. Select a bounded probe when its expected result could improve the decision or its grounds enough to warrant the burden. When no permissible action is available, report the stop and its basis. Seek another candidate or a missing contribution through the relevant practice if it can give the recipient a useful continuation.

OPS.6:4.5 - Specify the executable continuation contract

State the selected next Work, responsible performer, permission and effective conditions, stop or fallback, expected evidence, and the return to continuing operation. Name the observable change that would invalidate the action and require refresh. An existing plan, instruction, prompt, ticket-transition record, or model recommendation can carry this contract if it states these terms and identifies the required authorization.

OPS.6:4.6 - Admit performance and update state separately

After the Work, recover direct performance evidence, the result, any change to the subject, and any failure or limit, and the claim each observation supports. Update the case-state claim only when the relevant Work and resulting evidence are independently adequate. If Work did not occur or evidence is insufficient, retain only earlier claims whose support still holds and return the unmet condition. A contradicted or expired claim becomes unsupported or unknown; it is not restored merely because a new result is missing. Never use a record update, successful invocation, generated artifact, or selected action as automatic progression evidence.

OPS.6:4.7 - Return one usable result

Return either:

  • an evidenced progressed case state, its evidence and limits, fulfilled or still-open obligations, and next return; or
  • the unmet condition, direct owner or source of the needed result, safe fallback or stop, and exact retry condition.

Return a required priority, commitment or policy decision to its Operations owner, and a specialist decision to the practice that can supply it. The continuation result does not inherit their authority.

OPS.6:5 - Archetypal Grounding — Three Continuing-Case Replays

OPS.6:5.1 - PumpWorks field incident

Continue the constructed matter in OPS.5:5.1. At 09:05, incident I73 remains unresolved on installation P4. A field report describes intermittent pressure readings; neither their cause nor correction is known. The incident lead has authorized engineer E18 to inspect the identified captured logs until 11:00. The permission allows reading and diagnosis, not altering the deployed controller, declaring safety or releasing R42.

The applicable diagnostic procedure says: compare the captured sensor and controller timestamps; if the discrepancy persists in the captured interval, retain the discrepancy claim and request live verification; if identity fails or the data are corrupt, stop and return to the log owner. This direct rule is sufficient—no alternative-ranking exercise is needed. The incident lead chooses the bounded continuation; E18 performs it. The expected evidence is the identified input, execution trace, comparison result and its time interval.

The supplied observations are: E18 performed the comparison from 09:05 to 09:25; the retained trace identifies the P4 capture and comparison; a timestamp mismatch occurs in that capture; no live verification or controller change was performed. The defensible update is “discrepancy established in the captured interval; live cause and present field condition unresolved.” It is progress in diagnosis, not restoration of the installation. E18 returns the trace and this limited claim to the incident lead, closes I73-D at a safe stop and requests observational live verification in the 10:00–11:00 contact window. At 09:30 the field owner confirms access and the required permission for that bounded observation, without authorizing a setting change.

At 09:50 the field contact withdraws availability. The lead cannot start live verification under the earlier access assumption. The result becomes a returned access-and-permission condition, with the field owner as recipient and confirmed contact plus matching permission as the retry condition. Offline analysis of the already authorized capture remains allowed. The separate R42-T9 lab procedure, fixture check and performer are unaffected and remain in use; its result at 10:10 can support only its laboratory criterion. The operation does not erase the captured discrepancy or assert a current safe field state from the lack of a new report.

The next participant receives the bounded diagnostic result, the live-verification blocker, still-permitted work and the next useful contact action. For a priority or promise decision, use those facts through OPS.7 and identify who has the authority for each proposed change to priority or the promise.

OPS.6:5.2 - Public-hospital clinical case

One admitted clinical case continues from the exact patient and clinical-case subjects, current observations, applicable clinical and operating Methods, authorized practitioners, bed and resource relations, service obligations, and current consent, privacy, safety, and statutory conditions. A qualified clinical System retains medical decisions.

Use the authorized clinical result and applicable operating criteria to identify the next permitted Work, its responsible performer, stop or fallback, and the evidence needed to update the case-state claim. Missing consent, clinical evidence, bed relation, competence, medical-safety return, or statutory permission remains an unmet condition, not an Operations workaround. A record closure, bed-board move, or elapsed wait does not establish treatment, patient change, or clinical resolution.

OPS.6:5.3 - AI-assisted user issue

An admitted user issue encounters a changed trace, tool result, provider condition, model input, candidate change, or harness state. The operation refreshes evidence and applies the software domain Method and current established authority. It distinguishes the human or other deciding System, the responsible performer, agent episode, tool invocation, candidate change, test evidence, issue record, and release decision.

The continuation contract may authorize one bounded diagnostic, test, or repair Work with context and tool limits, stop, fallback, expected evidence and the responsible recipient, including a human reviewer when the case requires one. Report issue or candidate progression only after performance evidence supports it. A successful episode, green local test, visible trace, automated loop, or generated patch does not by itself establish issue progression, an integrated change, software assurance, a security result, or release permission.

OPS.6:6 - Bias-Annotation

Bias or pressureHow it distorts continuationCountermeasure
workflow-state biasA configured transition becomes the case truth.Recover the exact case subject, performance evidence, and qualified state separately.
action biasSelecting any next step feels better than returning a blocker.Use direct mandatory and recognition branches first; return when no permissible action exists.
automation biasA successful agent episode or model output is treated as progress.Separate invocation, Work, artifact, evidence, integration, and case-state claims.
plan-completion biasUpdating a plan or checklist appears to satisfy the obligation.Name the actual Work, responsible performer, result, and evidence expected.
stale-permission biasEarlier permission is reused after conditions changed.Match matter, conditions, configuration, horizon, and authority before selection.
expert-shadowing biasOperations quietly substitutes for clinical, safety, legal, or engineering judgement.Use a qualified specialist result or ask its provider for the needed answer. Make the coordination decision within the operating authority.
exception novelty biasEvery surprising event is treated as unprecedented improvisation.Reuse the applicable domain Method and choose the least elaborate adequate branch.

OPS.6:7 - Conformance Checklist

  • The exact case subject, configuration, horizon, and served demand or commitment are named.
  • The required current permission is supported for the same matter and conditions; admission alone is not treated as that permission.
  • Current case state, domain Method, obligations, commitments, evidence, and exception are recovered.
  • For Work selected to proceed, identify the authorized chooser and the capable, assigned performer. If either is missing, identify the condition that prevents action. Use evidence of performance and its effect for claims about them.
  • Direct mandatory or recognition branches are used when adequate.
  • C.11 is used only when several admissible live actions genuinely require comparison.
  • The continuation contract names Work, performer, conditions, stop or fallback, expected evidence, refresh, and return.
  • Case progression is reported only after independently supported Work and adequate resulting evidence.
  • The result is either evidenced progression or an exact unmet-condition return with owner, fallback or stop, and retry.
  • Specialist and wider Operations results remain with their owners.

OPS.6:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternFailureRepair
workflow transition equals progressA representation substitutes for changed case state.Require independently supported Work and resulting evidence.
selected action equals WorkA choice or instruction becomes a performance claim.Name performer and admit the dated Work separately.
agent ran, therefore case advancedInvocation and output hide authority, integration, and subject evidence.Preserve episode, Work, artifact, test, integration, decision, and state distinctions.
generic exception handlerOne fallback overrides domain Methods and specialist returns.Recover the applicable Method and exact unmet condition.
chooser-performer collapseDecision authority, assignment, capability, and performance become one relation.Name and support each relation independently.
stale authorization carryoverPermission survives changed conditions by default.Revalidate exact matter, configuration, horizon, and effective conditions.
endless analysisNo responsible performer, stop, evidence expectation, or return is stated.Produce the executable continuation contract or a blocker return.

OPS.6:9 - Consequences

The operation gains a defensible continuation move for exceptional and changing cases. Practitioners can tell what may happen next, who should perform it, what evidence will count, when to stop, and whether the case truly progressed or remains blocked.

Checking performance and the subject’s state takes time and may require evidence from another participant. When that evidence is missing, the recipient can act on the specific limitation without mistaking a record change for progress.

OPS.6:10 - Rationale

Case continuation sits between permission and evidence. If it collapses into admission, selection appears to perform Work. If it collapses into priority or commitment management, elapsed time or consequence pressure can bypass the applicable domain Method. Keeping the continuation contract and the later state update separate makes exceptions usable without inventing a lifecycle.

The two-result form is deliberate. An exact unmet condition with owner, safe fallback, and retry can be the complete useful Operations result. It prevents administrative state changes from hiding missing permission, capability, evidence, or specialist conclusions.

OPS.6:11 - SoTA-Echoing

The decision is how to continue a case after new facts while reporting a defensible result. A strong incumbent combines authorized case planning with outcome-aware execution. CMMN 1.1, §4.1 and §5.4.9 supplies runtime discretion, procedural subwork and planning authorization. Current DCR robot documentation distinguishes effect success, failure and timeout and the associated continuation. OPS adopts these mechanisms.

In I73, such an arrangement can authorize log inspection, execute a diagnostic activity and route a failed or unavailable live verification. If its case contract already states the capture identity, evidence interval, external subject claim and receiving authority, it produces the same adequate continuation as OPS.6. A second contract would only add synchronization work. The residual arises when an engine’s successful diagnostic activity is used as evidence that the physical installation is now restored. Sections 4.5–4.7 bind the operation’s observation to its warranted subject-state claim: the capture shows a discrepancy; present field condition remains unresolved. Loss of contact stops the dependent action without invalidating independent laboratory work.

That addition costs the domain mapping from execution outcome to observation and subject claim, a check of current permission, and a return the next participant can use. Use a sufficient direct procedure and its existing evidence. Additional logging is warranted when the receiving decision needs it and the cost or delay is acceptable within the applicable requirements.

FPF A.15.7 supplies situation-responsive steering and C.11 the conditional comparison branch. DEMO helps distinguish production and coordination; software-runtime sources inform bounded automation and stopping. Their execution semantics, source-local roles and software evidence do not grant external domain authority. Reopen when the incumbent already preserves the same physical-subject and permission distinctions more cheaply, or changed evidence, permission or execution semantics defeats the current continuation.

OPS.6:12 - Relations

  • OPS.5 supplies admission and may carry independently grounded start permission for the same matter and effective conditions.
  • A.15.7 governs the general situation-responsive steering Method. A.3.1.MR separately governs candidate reusable Method recovery from several performances or other direct evidence.
  • C.11 governs comparison only where several admissible live actions require choice. A.10 governs evidence reliance; A.15.8 governs the performance configuration or recovery dependency when that is current.
  • For an OPS.7 decision, use the evidenced progression or unmet condition when it bears on a priority, commitment or the grounds for retaining either. Establish who can revise priority and who can revise the commitment when those decisions arise.
  • OPS.8–OPS.13 retain wider queue, capacity, interacting-structure, and commitment-account questions.
  • Clinical, medical-safety, consent, privacy, legal, software assurance, security, release, provider, capability, and other specialist practices retain their decisions and evidence.
  • Practitioners may enter OPS.6 directly with matching valid permission for an admitted case, repeat it as facts change, stop at a blocker, or return to another current pattern.

OPS.6:End