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

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:10:10 UTC

OPS.4:5 - Archetypal Grounding — PumpWorks Current Operating Account

The weekly release decision uses a small account rather than one status board:

Account claimEvidence, uncertainty, and authorityNext decision or Work
FieldIncident-I73 may affect controller behavior at FieldPumpInstallation-P4.Field-engineer report and telemetry record are current to different times; lab reproduction is absent; service-impact extent is disputed. Field service may update observations but cannot accept product safety.Continue bounded diagnosis, obtain lab evidence, and keep release effect unresolved.
ReleaseCandidate-R42 passed tests T1–T8; T9 remains blocked by rig access.Signed test results identify candidate and fixture versions; the test-rig booking is current but does not prove a completed test. Release authority remains separate.Await exact rig access and T9; no release from card status.
SafetyQuestion-S19 has no current specialist decision.The issue record contains a question and evidence request, not a safety verdict. Only the named safety authority can return the needed result.Hold the affected release use or narrow its scope under the current authority rule.
ProviderChange-P8 changes model-artifact access after the current window.Contract and technical-access records disagree on effective date.Resolve the access relation or choose the supported incumbent route.
Weekly evidenced-release commitment is at risk.Incident, test, provider, and release claims have different horizons and authority. The account displays the relation without collapsing them into one status.Release, hold, rollback, narrow, or renegotiate only through the corresponding authority and evidence.

The product-side control view separately represents FieldTelemetryObserver-O4, DeployedController-C17, plant FieldPumpInstallation-P4, FieldModeSupervisor-S1, and their direct relations where supported. The operating-supervision view represents reports from PumpWorks-ControlServiceOps and constraints returned by ReleaseSupervisorTeam-S2. Qualify each timing claim needed for the decision: the rates at issue are sub-second product control, minute-to-hour field observation, daily incident triage, weekly release, and slower provider change.

For a shift or model-session handoff, the next participant must recover the operating question, five subject claims above, evidence versions, unresolved conflicts, permissions, next permissible Work, and stop. If recovery requires private memory or an unrecorded chat, A.15.8 returns the exact missing carrier, update/use relation, cue, or support condition. OPS.4 then repairs the operation-specific account claim or view.

Reopen only the affected claim when new telemetry arrives, T9 completes, safety authority returns a decision, provider access changes, a commitment is renegotiated, or a participant view can no longer support its action.

OPS.4:5.1 - Recover after a late observation

At 10:10 a participant receives a field report observed at 09:00. Its stated currentness window ended at 10:00. It cannot replace a 10:05 observation merely because it arrived later. The incident lead keeps the report as evidence about 09:00, marks the present field condition unknown where no current observation exists, and asks the field owner for a refresh. T1–T8’s laboratory evidence remains valid for its separate tested configuration and claim.

The next coordinator cannot open the raw field source. The handoff therefore includes the qualified claim, observation and receipt times, the source owner’s reachable confirmation route and the unverified present condition. The receiver acknowledges that the live-field decision is blocked; read access to the shared document does not resolve it. If the maintained incident document already carries these facts and this handoff, it is the OPS.4 account—no parallel register is required.