OPS.4 - Keep Current Operating State Recoverable Across Participants

OPS.4:0 - Use This When

Use this pattern when people must coordinate continuing Work but act from stale, partial, conflicting, differently authorized, or differently grained accounts of the same operating subjects. Typical cues are “we need one source of truth”, a control room with no claim provenance, a board that hides field state, a case handoff that loses the next decision, or a dashboard whose users cannot tell what they may change.

The first useful move is to create or repair one participant-usable account for one decision:

For subjects S and commitments C, current claims are Q at horizons T, supported by E with provenance and uncertainty P; participants may read or change ...; disagreements and gaps are G; next decisions or permissible Work are N; refresh or expiry occurs under R.

Aligned attention does not require identical screens or consensus. It requires that participants can recover the subjects, qualified claims, evidence, permissions, disagreements, and next decision relevant to their Work.

Recognition is cheap: enter when a participant cannot resume, decide, or explain a material disagreement from the maintained account. Assurance is claim-specific: world state, evidence, authority, permission, Work, safety, stability, causal effect, and release or acceptance decisions keep their own governing patterns.

Do not use OPS.4 to build a generic dashboard, mandate transparency, create one shared mental model, replace specialist records, or declare state true because it is visible. If the current problem is a Work-performance configuration or recovery dependency after interruption or support loss, use A.15.8 for that general question and keep the operation-specific state and commitments here.

OPS.4:0.1 - Working Distinctions

OPS.4:1 - Problem Frame

Continuing operation needs a present account because the operation outlives one meeting, screen, shift, or model session. Claims arrive at different rates from field observations, cases, tests, providers, plans, queues, and specialist decisions. Different participants need different slices and hold different authority.

The aim is therefore not one display or total agreement. It is recoverable correspondence between exact subjects, qualified claims, evidence, permissions, disagreements, and the next decisions each participant must make.

OPS.4:2 - Problem

Visibility without claim discipline amplifies error. A fresh dashboard can repeat stale field state, a green board can hide an unresolved service commitment, and an integrated twin can merge observations with predictions and planned states. Participants appear aligned until a decision exposes different referents, time horizons, or authority.

The opposite failure stores every record and overwhelms users. Important gaps, conflicts, and expiry conditions disappear in detail, so people reconstruct state from memory or private channels.

OPS.4:3 - Forces

OPS.4:4 - Solution

Maintain the smallest decision-specific account that lets named participants recover exact subjects, current qualified claims, commitments, evidence, uncertainty, permissions, disagreements, next decisions, and refresh conditions. Present several views when needed, but keep claim and subject correspondence explicit.

OPS.4:4.1 - Pattern-Use Unfolding

1. Name participants and decisions. State who must resume, coordinate, hold, release, escalate, or perform next Work; name the horizon and useful stop for each action.
2. Import exact subjects and relations. Use the OPS.3 operating-subject account. Do not let a dashboard row, case file, queue position, or control diagram replace the subject or obtaining relation.
3. Select only decision-changing claims. For each subject or commitment, state the current claim, effective scheme, conditions, time or horizon, and action it can change.
4. Attach evidence and provenance. Name source, observation or result, carrier, transformation, version, evidence reach, and uncertainty needed for reliance. Keep prediction, plan, observation, and decision claims distinct.
5. Expose conflict and absence. Preserve incompatible claims, missing observations, stale evidence, unknown authority, and unresolved specialist returns. Do not average them into false agreement.
6. Recover permissions and authority. State who may read, write, annotate, accept, hold, release, or change each relied-on claim or decision. Keep assignment, capability, responsibility, permission, and authority separate.
7. State next decisions and permissible Work. Name what is enabled, blocked, awaiting evidence, or returned to a specialist; include the condition and participant that can advance it.
8. Construct participant views. Select the smallest representation for each action. Preserve subject identity and claim correspondence; show what the view omits and where claims conflict, and provide a return to the owning account. Do not require one screen.
9. Keep control views separate. A selected FPF control view may expose observer, controller, plant, supervisor, observation, actuation, feedback, and rates. The account carries qualified operating claims about those subjects and relations; the view or loop picture establishes neither current state, feedback closure, rate adequacy, stability, safety, authority, nor an Operations Method.
10. Test interruption and handoff when current. Use A.15.8 for the general Work or WorkPlan performance-configuration question. Ask a representative next participant to recover the bounded question, current claims, evidence, disagreements, permissions, next Work, and stop without private memory.
11. Refresh, expire, and reopen. State update sources, expected cadence or event, expiry rule, supersession and conflict handling, and the observation that reopens only the affected claim, view, or decision.

OPS.4:4.2 - Record the Result

OPS.4:4.3 - What Changes in Practice

Participants stop asking whether everyone sees the same dashboard. They ask whether each participant can recover the exact subjects, claims, evidence, permissions, disagreements, and next action needed for that participant’s decision. A visible conflict or honest unknown becomes a usable coordination result. A record update no longer masquerades as changed world state.

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

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

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 separately represents reports from PumpWorks-ControlServiceOps and constraints returned by ReleaseSupervisorTeam-S2. The separately qualified temporal claims concern sub-second product control, minute-to-hour field observation, daily incident triage, weekly release, and slower provider change.

The OPS.4 account may cite claims about those participants, relations, and rates. The control diagram does not establish their current state, two-sided feedback, stability, safety, release authority, or the account itself. A dashboard can display the release hold and missing T9; it does not create either fact.

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:6 - Bias-Annotation

OPS.4:7 - Conformance Checklist

• The account begins from named participants, decisions/actions, horizons, and useful stops.
• Exact OPS.3 subjects, commitments, and direct relations remain recoverable in every relied-on view.
• Each current claim states content, scheme, time/horizon, conditions, evidence/provenance, uncertainty, and receiving action.
• Observation, prediction, plan, record, decision, and world-state claims remain distinct.
• Disagreements, missing observations, stale evidence, and specialist returns remain visible with their decision reach.
• Read, write, annotate, accept, hold, release, responsibility, capability, and authority relations are not inferred from one another.
• Next decisions and permissible Work name their enabling or blocking conditions.
• Participant views preserve subject and claim correspondence, make omitted scope and claim conflicts visible, and provide a return to the owning account.
• A control representation establishes none of current state, feedback closure, rate adequacy, stability, safety, authority, or Method.
• Refresh, expiry, supersession, handoff/recovery observation when current, and smallest reopen rules are explicit.

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

OPS.4:9 - Consequences

The pattern improves continuation across shifts, tools, teams, and interruptions without requiring one representation or consensus. It makes uncertainty and disagreement actionable and lets views change without losing subject identity.

The cost is explicit provenance, permission, conflict, and refresh maintenance. Some attractive dashboards become secondary because they cannot preserve the claim and authority distinctions needed by the decision.

OPS.4:10 - Rationale

Shared attention is an operating achievement when participants can coordinate from qualified claims about the same subjects and commitments. That achievement is weaker than universal agreement and stronger than common visibility. A small decision-specific account preserves the distinction, while FPF continues to govern epistemes, evidence, Work-performance recovery, structures, and control claims.

OPS.4:11 - SoTA-Echoing

The selected comparison is supported by the following bounded source roles and limits.

OPS.4:12 - Relations

• OPS.3 supplies exact subjects, direct relations, records, state claims, provenance, conflicts, permissions, and gaps. OPS.2 supplies selected participant and control views plus correspondence obligations.
• C.2.1 governs the claim-bearing account episteme; A.10 governs evidence reliance; A.15.8 governs the general Work/WorkPlan performance-configuration and recovery question.
• C.30.LCA, B.2.5, C.27.TA, C.27, and A.3.3 govern the conditional control structure, relation, and rate/dynamics claims. OPS.4 retains operation-specific commitments, state, intervention, authority/evidence, and consequences.
• OPS.5 later consumes current eligible demand, commitments, and uncertainty for admission. OPS.6 consumes case state and permissible next Work. OPS.15 and OPS.18 remain separate inspectability and operating quality/reliability decisions.
• Security, privacy, law, safety, medicine, product engineering, finance, governance, and other specialists retain their evidence, permission, authority, and decision results.

OPS.4:End