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 22:54:38 UTC

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.