OPS.16:4 - Solution
Build one status-preserving evidence chain from the operating question to the supported decision. In the pre-admission branch, a current account revision, retention, comparison or stop can finish under A.3.1.MR without another question, trial plan or performed trial. If a trial is selected, state the change hypothesis and alternatives, establish its actual conditions, keep planned and actual Work distinct, type observations and qualify their reach through the current owners. Return only the decision supported by the evidence and actual authority.
OPS.16:4.1 - Fix the operating question and status branch
Name the operating System, Work family or service, current difficulty, receiving decision, decision maker, horizon, and protected conditions. Then select the branch from evidence already available; the desired outcome does not select it.
| Starting branch | Required identity | First decision-facing statement |
|---|---|---|
| admitted Method | Exact U.Method, exact relied-on Method version or separately classified U.MethodDescription, current operating use, maintained claim, and evidence window | What local adopt, revise, branch, stop, or further observation decision could this evidence support? |
| pre-admission candidate | Exact A.3.1.MR candidate-account episteme for the provisionally distinguished reusable way, source support, real rivals, gaps, use limits and explicit non-admission; a distinguishing question only when it changes use | Which identity-test, account-revision, comparison, stop or selected further-observation result can this basis support? |
A candidate label such as “v2”, a checklist, a repeated local habit, or a repository entry does not move the second row into the first. Independently apply A.3.1 to admit a Method and A.3.2 to classify a separate description episteme. If those results are unavailable, retain the candidate branch.
OPS.16:4.2 - State a bounded change hypothesis and alternatives
Write the hypothesis in operating terms: for the named use and interval, changing the specified action or condition is expected to alter a named operating result without violating stated protections. Name the observation that could defeat the hypothesis and the decision it would change.
Use OPS.11.1 when the question requires reconstructing the current and proposed networks of transformations, resources and enabling conditions. State which operation, input, output, release rule, resource assignment or receiving commitment changes. Preserve the distinction between changing the operating route, changing the reusable way described, and establishing changed relations or capabilities in the organization. A change in one does not establish the other two.
Keep materially different, status-preserved alternatives in view:
- continue the current admitted Method or current observed practice for its supported use;
- use a revised admitted Method where its identity and description are already established;
- retain or test a candidate account without calling it a Method;
- branch an admitted Method by a real applicability or semantic difference;
- stop the proposed change or seek another observation.
Use OPS.17 when serious candidates must be recovered or compared. Consume an OPS.19 result only when its cross-scale decision changes feasible trial Work or a protected trial condition. A trial need not compare every named alternative; it must preserve the alternatives that can still change the receiving decision.
OPS.16:4.3 - Establish the conditions for running the trial
Recover the service, reliability, human-condition, access, permission, support, recovery, and resource conditions on which the trial relies. State the basis, interval and responsible party for each condition. Use existing resource, schedule and service results from OPS.10–OPS.13 or OPS.19 where they establish the required arrangement. Count existing assignments, trial work, learning and support against the same actual resources.
Obtain ordinary access, support and work allocations from their existing providers under the current arrangements. Use an organization-change result when the proposal needs to change the contribution, responsibility or authority arrangement itself, rather than use it for another case. Granting already-permitted tool access can be an administration service; transferring responsibility for accepting a result needs the corresponding organizational and professional decisions. Use a sufficient authorized result directly; OCE supplies design or coordination where that question remains unresolved, and OCE.11 coordinates the organization change with continuing service when needed. Unchanged job titles do not make a proposed arrangement effective. Obtain any missing capability or practice support from its appropriate development or introduction method.
A conditional WorkPlan can name a missing arrangement and the decision needed to establish it. Before starting the dependent trial Work, confirm that its allocation, permitted overlap, service protection, support, recovery and hand-back conditions hold for the required interval. A prospective plan does not establish their availability. If a condition is missing, keep the affected trial Work closed, as an OPS.19 decision may require, and state what can still proceed.
OPS.16:4.4 - Write a prospective trial WorkPlan
Plan the smallest trial whose observations can change the receiving decision. Name intended tasks, proposed performers, admitted constituent Methods expected to be enacted, supports, protected conditions, observations, burdens, stop rules, hand-back, and later receiving uses. Keep the plan prospective and identify the interval during which its premises must remain current.
A compact plan can use these positions:
| Position | What to state |
|---|---|
| status-preserved subject | Exact admitted Method and relied-on description, or exact candidate account and its missing admission basis |
| operating question | Current use, proposed change, comparison, decision maker, and decision-changing observation |
| intended Work | Tasks, proposed performers, expected admitted constituent Methods, containing System, and temporal window |
| conditions and stops | Authority, permission, support, service, recovery, human protection, fallback, and hand-back |
| observations | Direct subjects, measures or descriptions, collection point, burden, and later receiving use |
| return | Decision branches, unsupported stronger uses, next observation, and reopen condition |
This is a writing aid rather than a new trial object. A.15.2 governs the WorkPlan. The plan is neither performed Work nor evidence that the candidate whole or changed Method was enacted.
OPS.16:4.5 - Admit actual trial Work and direct results separately
After the trial interval, identify only Work that actually occurred. For each Work occurrence, recover the actual performer, temporal extent, containing System, enacted admitted Methods, and departures under A.15.1. Identify each direct result through its relevant domain owner. Keep later service Work, recovery Work, observation Work, and decision Work as separate wholes where their identities require it.
Never record the candidate reusable way or its candidate account as enacted. In the pre-admission branch, actual Work may enact independently admitted constituent Methods and may supply observations relevant to the candidate account. It does not enact the candidate whole.
A completed task also does not prove a Method change. A changed board, prompt, tool, description, support arrangement, or local departure changes Method identity only when reusable Method semantics change under A.3.1. Keep the changed object and direct relation instead when they do not.
OPS.16:4.6 - Type observations by subject and receiving use
Separate every observation that can change the decision. Do not combine them into a single improvement score.
| Observation position | Direct subject and use | Unsupported stronger reading to avoid |
|---|---|---|
| operating result | The named Work or operating System result for the selected interval | The changed Method caused a general improvement. |
| service or reliability | Eligible service events, accepted results, loss, recovery, or reliability condition | One completed case establishes broad reliability. |
| human condition | Affected participants, exposure, recovery, load, or support | Reported completion means burden was acceptable. |
| queue or constraint | Waiting, eligibility, admission, resource use, blockage, or displacement on its own population | Local utilization proves total-flow gain. |
| financial consequence | Incremental payment, receipt, cost, contribution, or horizon-specific consequence | A favorable accounting value authorizes the change. |
| side effect | A separately identified beneficial or harmful consequence | An observed side effect explains the whole result. |
| burden | Time, attention, coordination, training, observation, or apparatus required | Small trial effort proves affordable sustained use. |
| missing evidence | The absent observation, affected decision, and next way to obtain or stop | Absence may be filled by a nearby proxy. |
| Method or description claim | The exact reusable semantic or description claim that observations support or contradict | Every tool, wording, support, or local-use change creates a Method variant. |
Use OPS.15 when the observation population or event correspondence is not yet trustworthy. Use OPS.18 when the evidence calls for a quality or reliability control decision. Those results retain their own subjects and authority.
OPS.16:4.7 - Qualify the evidence through its current owners
Ask only the specialist questions that the receiving decision needs. Current ME.11 supplies representative and discriminating trial evidence; ME.12 examines coherence; ME.13 examines situational fit or transfer; ME.14 examines practical worth; ME.15 maintains Method lineage and variant claims; and ME.16 separates target, introduction strategy, actual Work, observations, and bounded revision. Reuse their current results instead of recreating them inside Operations.
Use A.10 for evidence reliance, C.16 for measurement validity, and C.27.TA for the temporal window. Use C.27 when the receiving use requires a temporal-claim adequacy check, and the C.28 causal-use result when the decision relies on a causal claim. Return temporal order, association or direct occurrence evidence at its supported strength, keeping the limits needed by the decision in the existing operating return. A favorable occurrence automatically establishes none of coherence, transfer, practical worth, sustained effectiveness, or causality.
Increase assurance effort only where it can change the decision. The extra identity and evidence distinctions are worthwhile when they prevent an unsupported start, branch, or stop. If a simpler observation settles the same bounded choice under the same protections, use it and leave stronger claims unresolved.
OPS.16:4.8 - Compare alternatives under authority and protected conditions
Compare the current, revised, branched, stopped, and still-uncertain alternatives that remain feasible. Use the same operating use, interval, result definition, and protected conditions. Carry uncertainty as an explicit interval, scenario, or missing claim. Preserve alternatives that remain non-dominated for materially different uses or conditions.
Identify the Agent authorized to make the local operating decision and the predicate, scope, and basis of that authority. Clinical, safety, release, financial, employment, security, and other specialist decisions remain with their owners. Expertise, sponsorship, assignment, access, and a tool recommendation do not transfer authority.
A favorable result cannot make an infeasible alternative feasible. Stop or narrow the trial when permission, qualified support, fallback, recovery, evidence validity, or another protected condition is absent.
OPS.16:4.9 - Return a status-preserving operating decision
Use the branch selected in section 4.1.
| Branch | Permitted return | Required boundary |
|---|---|---|
| admitted Method | adopt, revise, branch, stop, or further observation | Bind the decision to the exact admitted Method and relied-on version or description, named operating use, conditions, evidence window, and authority. |
| pre-admission candidate | continue to the separate A.3.1 identity test; revise or retain competing candidate accounts; stop; or seek further observation | Keep the candidate reusable way inside its candidate-account episteme. Return no Method adoption, Method branch, or U.MethodDescription claim. |
For either branch, return the exact operating use, supported evidence, unsupported stronger use, protected conditions, decision maker and relevant repertoire, lineage or reopen consequence. Include a next observation only for a selected further inquiry; a completed candidate-account revision or stop needs none. When the decision consumes a returned value from a governed operation application, A.6.1 binds that exact value and C.2.1 identifies its separate result episteme. Do not turn it into a generic Work result or produced entity. Keep the decision and any Method-lineage update separate from trial Work.
An adopt or branch return makes an admitted Method available only for the named operating use and conditions. It does not establish organization-wide adoption, cultural selection or retention, causal superiority, a new capability, or authorization elsewhere. Send a result to OPS.20 only as an admitted local Method variant with its exact relied-on description and bounded evidence, or as a status-preserved candidate-account or observed-practice variation.
OPS.16:4.10 - Keep the return short enough to decide from
A useful return lets the responsible practitioner answer four questions quickly: which admitted Method or candidate account was considered; which available sources support the result and, if a trial is claimed, what actual Work and observations occurred; what current account or decision is supported; and what remains unsupported or reopens the decision. Attach detailed evidence through its owning account rather than restating it.
What changes in practice: the team stops saying “we tried the new process and it worked.” It preserves Method or candidate-account status and source limits, finishes a supported current account, and separates a selected trial’s plan, actual Work and observations. Service and authority limits remain binding in every branch.