Part II — Recover Operating Subjects and Maintain Current State
OPS.3 - Distinguish Operating Subjects, Cases, Queues, Resources, and Records
Status: Stable
OPS.3:0 - Use This When
Use this pattern when one card, ticket, order, object identifier, case file, event row, or status label is being asked to stand for several different things. Enter when the subject of a measure or the item waiting in a queue is unclear, an incident record is treated as the incident, a resource is treated as its availability, or two views cannot agree because they identify their subjects differently.
The first useful move is to resolve one decision-bearing subject and the claim needed about it. An existing account or a short explanation can carry this result:
Subject
Shas identity conditionI. The decision-bearing claimQaboutSand its relationsRis qualified for time or horizonTand supported byE. State a formal kind, represented view, governing rule or missing condition when the receiving use depends on it.
Repeat for distinctions that can change the decision or the grounds for a conclusion the user needs. Stop with an account of the relevant subjects and their relations.
Use the method when a record label, metric denominator, queue item, or “work object” has several plausible referents. Assurance is claim-specific: entity kinds, Work, relations, commitments, state, evidence, event occurrence, control participation, resource availability, and representation each retain their FPF or specialist tests.
Use an existing subject pattern or an adequate subject account when it answers the identity or relation question. Add the Operations correspondence needed for this decision. For example, a ticket number may identify the record while the field installation and the incident have separate identities.
OPS.3:0.1 - Working Distinctions
| Name used here | Meaning |
|---|---|
| operating subject | The entity or relation the operating question concerns. It may be, for example, a case subject, material, a service or an account whose identity or state matters to the decision. |
| case | One bounded continuing Work situation organized around a named subject, commitments, current facts, evidence, authority, permissible next Work, and closure conditions. The case is neither its file nor every Work item within it. |
| Work occurrence | Actual dated Work admitted through its governing pattern. A ticket, plan, or event record does not establish that Work occurred. |
| Work item | A bounded item admitted to a selected workflow or coordination account with stated start, finish, subject/result relation, and receiving use. |
| queue membership | An obtaining relation placing one eligible item in one named waiting or service order under a policy and time window. A column or list is a representation. |
| buffer membership | An obtaining relation to a bounded protective or coordination reserve with purpose, policy, extent, and receiving use. It is not inferred from spare inventory or a board column. |
| resource relation | A relation that matters to the provision or use of a resource. For planned work, identify what is available, accessible or allocated under the stated conditions. For a claim about performed Work, identify the support it received or the resource it consumed. |
| event | An occurrence or change under its subject rule and time boundary. An event record or timestamp is evidence about it, not the event by identity. |
| record or trace | A claim-bearing episteme about subjects, Work, events, relations, or decisions, recorded on an identified carrier. Its claims have stated sources and scope limits. |
| state claim | A qualified claim about one subject at a stated time or horizon with provenance, uncertainty and conditions; include authority where the claimed state or receiving action depends on it. A status label is one possible representation. |
| control participant meaning | Observer, controller, plant or supervisor as the participant meaning in an actual control relation. Qualify a selected control structure when that claim is needed. The label does not establish that the relation obtains. |
| operating-subject account | The smallest relation-specific set of identities, direct relations, records, state claims, and any limits the decision maker needs to know. |
OPS.3:1 - Problem Frame
Operational tools summarize subjects, events and states so participants can coordinate their work. That compression is useful until one row is read as the customer, order, case, Work, queue position, resource claim, event history, and current state at once. Object-centric and case-responsive approaches repair parts of this problem, but their own records and identifiers still need receiving-use limits.
The practitioner needs a small account that restores identity and obtaining relations before measures and policies are applied. The account can use several records and views while keeping the world-side subjects and claim-bearing epistemes distinct.
OPS.3:2 - Problem
When identities collapse, flow measures acquire false denominators, cases close while the conditions they were meant to resolve persist, queue policies compare unlike items, resources are double-counted, and events are reconstructed into Work that may never have occurred. A record update can then masquerade as an operational change.
An unnecessarily broad modeling effort can delay the current decision while still omitting the few direct relations it needs. Tool categories require the same check against the subjects and relations they claim to represent.
OPS.3:3 - Forces
| Force | Tension |
|---|---|
| Coordination shorthand | One ticket or identifier is affordable, while it can hide several subjects and relations. |
| Measurement | Stable units enable comparison, while identity changes and joins can silently change the measured population. |
| Several records | Logs, trackers, files, and physical observations can complement one another, while their claims may conflict. |
| Runtime change | Cases and subjects evolve, while records arrive late or use stale identity rules. |
| Resource scarcity | Capacity decisions need resource relations, while people and machines must not be reduced to scalar capacity. |
| Minimality | The operation needs decisive distinctions now, while a complete domain model is expensive and brittle. |
OPS.3:4 - Solution
Use or develop a small operating-subject account that preserves the identities, relations, times and evidence the decision needs. Identify how each relevant record or view represents its subject. Start from the subjects and views already selected through OPS.1 or OPS.2.
OPS.3:4.1 - Pattern-Use Unfolding
- Name the receiving decision and suspected compression. Identify the subjects or relations that may have been treated as the same, the measure, queue, case continuation, commitment, control question, or account use that depends on that identity assumption, and what fails if the assumption is false.
- Select the primary subject. Identify the entity or relation the action or conclusion depends on, and how to recognize it across time. Use its subject pattern when the answer depends on its kind.
- Separate case, Work, and Work item. Name the case subject and closure conditions; admit actual Work independently; define each coordination Work item by start, finish, subject/result relation, and receiving use.
- Recover queue and buffer relations. Name eligible item, queue or buffer, membership interval, order or protective purpose, policy, resource/service relation, and evidence. If the decision uses a position shown in a view, establish which of those relations it represents.
- Recover resources through exact relations. Distinguish the System, capability, material, information, access condition, or time from availability, access, allocation, support, consumption, or other obtaining relation. Preserve authority and human-condition questions.
- Separate events, records, and state claims. Identify the occurrence or changed subject and the records supporting it. For a consequential time, distinguish occurrence, observation, receipt and later correction; recover the clock and field meaning actually used. A later upload does not move the occurrence or reset its waiting time. State the supported claim and its uncertainty. Event order alone does not establish performed Work.
- Recover commitments and direct relations. Use
A.6.RELor the direct governor for each relied-on relation. Keep promise, obligation, fulfilment, responsibility, authority, assignment, and evidence distinct. - Apply the control branch only when selected. Preserve actual Systems or holons and direct observation, actuation, reference, supervision, and feedback relations. Treat observer, controller, plant, and supervisor as relation-specific meanings. Use
B.2.5only when both observation/report and returned influence/constraint sides obtain. - Reconcile records by subject and claim, not by row. When a relation or timestamp is disputed, identify the source that can settle that particular meaning and who or what is authorized to correct the account. Preserve the original observation and explain the correction. Recompute only the state, elapsed time, queue membership or other decision that used the defective relation. Keep an unresolved association unusable for that inference; do not guess a replacement. Retain independently supported claims and ongoing work. A correction to a record does not itself change permission or undo performed Work.
- Stop at the smallest sufficient account. Return the subjects, relations, state claims and support needed by the decision, with any unresolved condition. Use OPS.4 when participants need to maintain or share the current account; otherwise the resolved identity or relation can finish this use. Identify revision conditions when the result will be reused. Leave unrelated objects outside.
OPS.3:4.2 - Carry the Result
Preserve the content needed by the selected question. Use the existing record or explain the result directly; create or maintain a record only when coordination, later reliance or another governing requirement needs it.
| Result position | Content when relevant to the receiving use |
|---|---|
| use boundary | User, decision, horizon, suspected compression, and useful stop. |
| subjects and identity | Identified primary and related subjects, relevant kinds or predicates, identity conditions and any unresolved referents. |
| cases and Work | Case subject and closure; actual Work basis; Work-item start/finish, subject/result relation, and receiving use. |
| queue, buffer, and resource relations | Participants, membership or access interval, purpose/policy, order or extent, direct relation, and evidence. |
| events and records | Occurrences, claim-bearing records and carriers, source, scope, time, uncertainty, and any inference limits that matter to the decision. |
| state and commitments | Qualified state claims, commitment relations, provenance, any applicable authority, conflicts that matter, and the conditions under which the claims remain current. |
| control relations, when the control branch is selected | The actual participants and decision-bearing observation, actuation, reference or supervision relations. Omit this row for an account that makes no control claim. |
| continuation | Any unresolved condition or needed account maintenance; revision conditions for a result that will be reused. |
OPS.3:4.3 - What Changes in Practice
Measures, queues, and dashboards acquire named subjects and relation semantics. A card move updates the record. Separately establish any change in the subject or relation that the updated record represents. Teams can keep several tools while knowing which claim each can support and where a missing identity or relation blocks action.
OPS.3:5 - Archetypal Grounding — PumpWorks Subject Account
The weekly release decision initially sees four cards and a rig calendar. To decide what can be relied on, distinguish the cards and calendar from the following subjects and relations:
| Visible item | Recovered subject or relation | Record boundary |
|---|---|---|
ReleaseCandidate-R42 card | A release-candidate subject and its candidate contents, required evidence results, release Work items, and receiving release decision. | The card and commit identifiers are records; moving the card does not change deployed field state or satisfy the release commitment. |
FieldIncident-I73 ticket | A case organized around FieldPumpInstallation-P4, reported symptoms, service commitments, evidence, authority, permissible next Work, and closure conditions. | Ticket closure does not establish restored field condition or fulfilled service. |
SafetyQuestion-S19 issue | A question episteme, related evidence needs, specialist safety decision, and any Work items created to obtain that result. | A red label is neither a safety state nor authority to accept risk. |
ProviderChange-P8 epic | A time-bounded change subject with provider relations, access conditions, project WorkPlan content, affected release cases, and decisions. | The epic does not make the provider part of PumpWorks or prove performed migration Work. |
| test-rig booking row | Queue membership of an exact eligible request for resource relation to TestRig-2, with interval, order/policy, access condition, and status evidence. | The booking row records planned access. Establish request eligibility, allocation authority, performed test Work, and test completion separately. |
Distinguish the records for this decision: ticket, trace, source commit, build result, test result, service log, field-engineer report, telemetry record, and release decision each support bounded claims. A multi-object event record may relate one event to several subjects, but it does not identify those subjects with one case or prove the represented Work.
Consider a later, constructed PumpWorks reconciliation. An imported test event L17 has been associated with both R41 and R42 because their records share a release folder. The board consequently removes R42’s test request from the ready queue and reports “tested at 10:20.” That conclusion assumes that L17 tested R42, and that 10:20 is test completion rather than receipt of the message.
The lab’s signed execution record identifies the tested build as R41 and completion at 09:50; the intake trace identifies 10:20 as message receipt. The lab engineer confirms those meanings, and the authorized record maintainer replaces the false R42 association with the supported R41 association while retaining the original import and the correction’s basis. R42’s completion claim is withdrawn. After confirming that R42’s independently established inputs and permission still hold, the scheduler restores its waiting eligibility and the priority justified by the current queue rule and original waiting history. Correction time does not restart its age or revoke work already permitted or performed on other requests. L17 supports the stated R41 test result, not R41’s wider release or field condition.
S19’s unresolved safety question, I73’s field observations and the independently permitted work on them remain as they were. The correction reaches OPS.4’s R42 state and OPS.8’s test population because those uses consumed the bad link; it does not invalidate the entire operating account. If the execution record cannot identify the tested build, neither R41 nor R42 acquires test completion from L17. Ask the lab which build the record covers, or identify that missing fact in the result. Other work can proceed where its independent conditions and permissions hold. This small reconciliation is sufficient when those are the only affected uses; a full data-model migration would add cost without changing the decision.
For the product-side control view, FieldPumpInstallation-P4, FieldTelemetryObserver-O4, DeployedController-C17, and FieldModeSupervisor-S1 retain their relation-specific meanings. For operating supervision, ReleaseSupervisorTeam-S2 is an admitted acting System only where supported and the two-sided report/constraint relation to PumpWorks-ControlServiceOps is recorded only if both sides obtain. The diagram, participants, relations, state claims, and operating account remain distinct.
When participants need a shared or maintained account, use these subjects, records, current claims and any relevant conflicts, permissions or update conditions in OPS.4. Reopen only the affected identity or relation when a release candidate is superseded, an incident splits or merges under an explicit rule, a queue membership changes, a record source becomes stale, or a claimed control relation loses one side.
OPS.3:6 - Bias-Annotation
| Recurring bias | Likely drift | Repair |
|---|---|---|
| card-identity bias | Card, case, Work item, and subject become one thing. | State separate identities and direct relations. |
| case-file bias | The file becomes the continuing case. | Name the subject, commitments, current facts, permissible Work, and closure conditions. |
| queue-container bias | A column or list is treated as an obtaining queue. | Recover membership, order/service relation, policy, interval, and evidence. |
| resource-scalar bias | A person, machine, or capability is reduced to available hours. | Preserve the subject and access, support, allocation or use relation on which the decision relies. |
| event-log realism | A log is treated as complete performed Work. | Preserve source limits and admit Work independently. |
| object-centric collapse | Multi-object linkage is read as one universal case or process. | Keep subjects, event relations, records, views, and receiving uses distinct. |
| control-role reification | Observer, controller, plant, or supervisor labels become permanent kinds. | Recover participant meanings in exact obtaining relations. |
OPS.3:7 - Conformance Checklist
- The account begins from one receiving decision and a named suspected compression.
- Each decision-bearing subject has an identity condition and direct subject governor when needed.
- Case, actual Work, Work item, queue membership, buffer membership, resource, event, record, and state claim remain distinct.
- Work items state start, finish, subject/result relation, and receiving use.
- Queue, buffer, and resource claims name exact participants, purpose or policy, interval, and obtaining relation.
- A relied-on record preserves its source, subject, claim scope, time and uncertainty, and any inference limit material to the receiving use.
- Direct relations use current governors; a representation or co-occurrence creates none.
- Control participants and two-sided feedback are recorded only where actual relations obtain.
- The result is the smallest account sufficient for the decision, with any unresolved condition and the revision conditions needed for reuse.
OPS.3:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Repair |
|---|---|
| “One issue equals one unit of value.” | Name the represented subject, Work item, result relation, identity rule, and receiving decision. |
| “The customer is in the queue.” | State whether the queued participant is a request, case, Work item, physical subject, or another identified entity. |
| “The resource is 80% utilized.” | Identify the resource subject, availability/allocation/use relation, time window, Work, and decision. |
| “The event log shows the process.” | State the logged events, object relations, source coverage, reconstruction rule, and missing Work evidence. |
| “Status Done means fulfilled.” | Recover the commitment, supplied result, acceptance or fulfilment evidence, and authority separately. |
| “The dashboard closes the feedback loop.” | Recover both in-life relation sides and keep the display, claims, rates, and proof separate. |
OPS.3:9 - Consequences
Identifying the units and their evidence gives practitioners a basis for measurement, policy and reconciliation across views. It also localizes repairs: a stale record source, changed identity rule, missing relation, or uncertain state claim can reopen without rebuilding the whole operating account.
The cost is refusing convenient conflations. Some metrics and historical analyses become unusable because their unit identity or source coverage cannot be recovered. That loss is explicit rather than hidden in a precise-looking chart.
OPS.3:10 - Rationale
Identify the subjects and relations on which the operating decision or required conclusion depends. Use the available observations, confirmations and records to establish them. A small account can suffice when it shows which conclusion is supported, how any cited record represents its subject, and what limit still matters.
OPS.3:11 - SoTA-Echoing
The question is which subjects, relations and times must be recovered before the responsible practitioner can rely on the records for an operating decision. A capable object-centric account already relates events to several objects, retains histories and distinguishes relation meanings. OPS adapts that contribution.
OCEL supplies an exchange model for that account. The 2026 object-centric process management manifesto, particularly §2.3 and §3, distinguishes execution data from their representations and identifies changing relations as a limitation of OCEL 2.0. The 2026 object-centric data-quality study, “Relationship-based quality issues” and its practitioner cases, shows why a well-formed multi-object log can still have wrong or insufficiently qualified links and changing timestamp meanings. These findings motivate checking object links and timestamp meanings in steps 6 and 9 of OPS.3:4.1 and in OPS.3:5. Whether the correction improves a particular operating decision requires evidence from its use there.
In the L17 choice, a competent data-quality procedure that already checks the build, timestamp meaning, correction provenance and affected consumers is sufficient. Use it unchanged. Where it repairs the log but leaves the operating consequence undecided, OPS adds the narrow return: withdraw the unsupported R42 completion, recompute only dependent membership and age, and retain the independently supported work. The extra cost is consulting the responsible source and following the faulty relation into the decisions that relied on it. Recreating every object or copying all histories into a second account is unnecessary. An unresolved relation can block one inference without blocking the rest of the operation.
Current FPF A.6.REL governs the direct relations relied on; distinguish relation occurrences only when the receiving use must tell repeated occurrences apart. C.2.1 governs claim-bearing accounts and B.2.5 the selected two-sided supervision relation. Subject-specific identity and specialist evidence remain with their direct governors. CMMN 1.1, DCR and DEMO’s bounded commitment/coordination account retain their case-planning and relation contributions; none makes record closure proof of physical completion. Integrated network descriptions can retain unlike coupled relations without identifying their subjects.
Reopen this choice when the record’s meaning, relation history, clock, consumer or correction authority changes, or when the incumbent supplies the same bounded correction and operating return at lower effort. For a larger data migration, use the appropriate data-engineering method.
OPS.3:12 - Relations
OPS.1supplies operating scope, subject candidates, commitments, units, and evidence questions.OPS.2supplies selected views, grains, correspondences, and conditional control questions.A.6.RELand direct subject patterns govern obtaining relations and identities;C.2.1governs claim-bearing accounts;B.2.5andC.30.LCAgovern the conditional control relation/view boundary.- For ongoing coordination through
OPS.4, use the identified subjects, relations, records, state claims and provenance, together with any conflicts, permission conditions or material gaps. OPS.8,OPS.9,OPS.10,OPS.11,OPS.12, andOPS.18later consume the exact subjects and relations whose queue, constraint, capacity, interaction, human-condition, or quality claim is current.- Data engineering, process mining, product engineering, safety, finance, law, medicine, and other specialists retain their schemas, inference Methods, evidence, and authority.
OPS.3:End
OPS.4 - Keep Current Operating State Recoverable Across Participants
Status: Stable
OPS.4:0 - Use This When
Use this pattern when participants 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 use or repair the account needed by one participant decision:
For subjects
Sand commitmentsC, current claimsQat horizonsThave supportE, with the provenance and uncertainty needed by this decision. Preserve any consequential disagreement, missing condition, access or decision authority, next action and condition for updating the account.
Participants can coordinate from different screens and can retain a material disagreement. Each needs the subjects, claims, evidence, permissions and next decisions relevant to its 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
| Name used here | Meaning |
|---|---|
| current operating account | A participant-usable set of qualified claims tied to exact operating subjects, commitments, evidence, permissions, decisions, and refresh conditions. It is neither the operating System nor a universal database. |
| subject-state claim | A claim about one subject or relation at a stated time or horizon, with the scheme, conditions, provenance and uncertainty needed to use it; authority is a separate condition where the claim or action depends on it. |
| currentness | The condition under which a claim remains usable for a named decision and horizon. Recent timestamps alone do not establish it. |
| provenance | The source, observation, transformation, record, and responsibility facts needed to judge the claim’s receiving use. Provenance does not make the claim true by itself. |
| uncertainty | Missing, estimated, conflicting, stale, or bounded information that could change a decision, a claim the participants need to support or the conditions for relying on it. |
| disagreement | Two or more recoverable claims, interpretations, or decisions that cannot yet be used as one result. Visibility of disagreement is compatible with aligned attention. |
| permission and change authority | Separately supported relations governing who may read, write, approve, hold, release, or otherwise use account content. Visibility, responsibility, assignment, and capability imply none of one another. |
| next decision or permissible Work | The decision or Work option currently enabled, blocked, or awaiting a named condition. The account does not perform or authorize it by display. |
| participant view | A use-bounded representation of selected account claims for one participant action. Several views may coexist when subject and claim correspondence remain recoverable. |
| control representation | A view, loop diagram, dashboard, or control-room display representing selected control structures, relations, rates, or account claims. It establishes none of those facts by appearance. |
| attention-maintenance result | A usable current account and the views its participants need, with material gaps, update conditions and next decisions identified where applicable. |
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.
Participants can coordinate when they can relate claims, evidence and permissions to the same subjects and recover what each decision requires. Preserve a material disagreement and its grounds wherever the participants’ accounts differ.
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 participants may have to reconstruct the state from memory or information unavailable to the next shift.
OPS.4:3 - Forces
| Force | Tension |
|---|---|
| Speed | Participants need a quick current view, while rushed aggregation can erase provenance and uncertainty. |
| Several horizons | Field control, incident response, release, provider change, and finance update at unlike rates. |
| Several participants | Participants need different views and permissions, while divergence can hide conflicting claims. |
| Continuing Work | Handoffs and interruptions require recoverability, while an account cannot guarantee capability or performance. |
| Disagreement | Teams want one answer, while preserving a qualified conflict can be safer than premature consensus. |
| Representation | Dashboards and control rooms improve attention, while appearance can be mistaken for state, authority, or proof. |
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
- 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.
- 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.
- Select claims that matter to the receiving work. For each subject or commitment, state the claim, its effective scheme, conditions, time or horizon, and what decision or conclusion depends on it.
- Attach evidence and provenance. Preserve the source and support needed for the claim and receiving use, including the observation or result, carrier, transformation, version, reach and uncertainty where they affect reliance. Reuse that basis from the current account. Keep prediction, plan, observation and decision claims distinct.
- Show material disagreements and gaps. Where claims conflict, preserve their grounds and the decision they affect. Identify any missing observation or specialist result, stale evidence or uncertainty about authority that limits the decision.
- Recover applicable permissions and authority. For a restricted access, account change or operating decision, establish who may act, on what and under which conditions. Preserve the existing basis when current. Keep assignment, capability, responsibility, permission and authority separate. A factual observation can support a state claim without itself granting permission to alter that state or a commitment.
- 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.
- Use a suitable view for each participant. Use a sufficient current representation or develop the one the action needs. 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.
- Qualify a selected control view. Relate its depicted observation and intervention to the actual participants, evidence and authority. Obtain stronger control claims, such as stability or rate adequacy, from their direct analysis; the picture cannot supply them.
- Test interruption and handoff when current. Use
A.15.8for 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. - Keep the account current for its use. Identify the source or event that changes a relied-on claim and how affected participants will receive the update. Specify cadence, expiry, supersession or conflict handling where the claim or its use requires them. Reopen only the affected claim, view or decision.
OPS.4:4.2 - Maintain the Usable Account
Reuse existing specialist records and participant views. Keep the content below to the extent needed for the selected decisions, access conditions and continuing use.
| Result position | Content for the receiving use |
|---|---|
| use boundary | Participants, actions or decisions, horizons, first useful result, and truthful stops. |
| subjects and commitments | Exact OPS.3 subjects and direct relations; commitment parties, content, conditions, status, and authority. |
| current claims | Claim content, effective scheme, time/horizon, conditions, uncertainty, and receiving action. |
| evidence and provenance | Sources, observations/results, carriers, transformations, versions, reach and any missing evidence. |
| permissions and authority | Applicable access, account-change and operating-decision relations, with their scope and basis. |
| disagreement and gaps | Any conflicting or missing claims, the decisions they limit, and the specialist results or separate interpretations needed. |
| next decisions and Work | Enabled, blocked, awaiting, or returned actions; required condition and responsible participant. |
| participant views | Selected claims, subject correspondence, explicit scope of omitted material, conflict cues, return route, and access limits. |
| refresh and recovery | Update or expiry conditions, handoff/recovery observation when current, and smallest reopen rule. |
OPS.4:4.3 - What Changes in Practice
Each participant can recover the subjects, claims, evidence, permissions and next action needed for its decision. If participants disagree or a fact is missing, the account shows which action or conclusion that limits. A change to a record can then be distinguished from a change to the state it describes.
OPS.4:5 - Archetypal Grounding — PumpWorks Current Operating Account
The weekly release decision uses a small account rather than one status board:
| Account claim | Evidence, uncertainty, and authority | Next 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.
OPS.4:6 - Bias-Annotation
| Recurring bias | Likely drift | Repair |
|---|---|---|
| single-source-of-truth bias | One database or screen is treated as the world and final authority. | Preserve exact claims, provenance, conflicts, permissions, and receiving decisions. |
| visibility-as-alignment bias | Everyone can see the board, so coordination is assumed. | Test whether each participant can recover the next decision and any material disagreement. |
| consensus bias | Conflicting qualified claims are forced into one status. | Keep disagreement explicit with evidence reach and resolution condition. |
| freshness bias | The newest timestamp is assumed current for every horizon. | State claim-specific currentness and expiry for the receiving use. |
| access-authority bias | The ability to edit or view is treated as authority to decide. | Recover permission and decision authority separately. |
| representation-as-control bias | A loop or control room is treated as feedback closure or operating Method. | Recover actual relations and keep view, account, rates, and stronger claims distinct. |
| memory-repair bias | People or models are told to remember more after handoff failure. | Use A.15.8 to recover the missing state, carrier, update/use relation, cue, or support condition. |
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.
- Any selected control view returns to the actual observation/intervention relations and to the direct support for its stronger claims.
- Participants can recover updates that affect their use; applicable expiry, supersession, conflict and recovery conditions are retained.
OPS.4:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Repair |
|---|---|
| “Build one dashboard for everyone.” | Start from participant actions and select claims and views for each, with correspondence and return. |
| “Green means done.” | Recover the subject state, commitment, evidence, acceptance or fulfilment result, and authority. |
| “Latest update wins.” | Apply claim-specific currentness, source reach, conflict, and supersession rules. |
| “Make everyone agree.” | Preserve qualified disagreement and name the evidence or authority needed for resolution. |
| “If it is editable, the team owns it.” | Separate access, permission, responsibility, assignment, and decision authority. |
| “The control room closes the loop.” | Recover the in-life relation sides and rate claims; treat the display as a representation. |
| “The handoff failed because attention was low.” | Identify the missing subject claim, carrier, update/use relation, cue, permission, or stop. |
OPS.4:9 - Consequences
An accessible, current account lets the next participant recover the state of the work and the conditions for proceeding across shifts, tools, teams or interruptions. A participant can identify a permitted next action or report the specific condition that still blocks it. Different views can preserve the same subject identity and any material disagreement.
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. Seeing the same display is insufficient if the next participant cannot recover the meaning of a claim or its authority. Where claims disagree, both can still be available for the decision. 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 question is whether the next participant can act from a current, qualified operating account. A competent incumbent is SRE incident practice with separated responsibilities, a maintained live incident document, communications and an acknowledged handoff. Google SRE, “Managing Incidents” develops those mechanisms, including a usable document when the affected service cannot host it. OPS adopts this arrangement.
At PumpWorks, a good incident document can already identify I73, its commander, current actions and next handoff. When that account also distinguishes field-observation time from receipt time, laboratory evidence from current installation state, and release authority from document access, it suffices. Sections 4.1–4.3 ask for those distinctions where a recipient’s action or what the recipient can justify depends on them. The residual in section 5.1 is concrete: an expired field claim cannot supply the current evidence required for a live intervention, yet the laboratory results remain usable. A receiver lacking raw-source access needs an effective confirmation or an explicit blocker, not a second copy labelled current.
The extra work is qualifying the few decision-bearing claims, maintaining their different expiry conditions, and testing that the recipient can recover them. Frequent rechecking can itself consume scarce attention and delay response. Use the shortest refresh and handoff arrangement that preserves the decision, keep a qualified unknown instead of fabricating certainty, and reuse the incumbent’s document and roles. If those provisions already exist, adding an OPS template would be pure maintenance burden.
FPF C.2.1, A.15.8, A.10 and C.27.TA supply account, recovery, evidence and temporal distinctions. OCEL and object-centric methods help retain different event-object histories, but the use of a log for a current-state claim depends on its meaning, coverage and time. Control relations matter only for an actual observation-and-intervention question. DORA and agent-runtime sources remain bounded software-use comparisons, not a general theory of attention. Reopen this selection when a stronger existing account gives the same recoverable decisions more cheaply, or a failed handoff exposes an omitted claim, permission or source-access condition.
OPS.4:12 - Relations
OPS.3can supply identified subjects, relations, records, state claims and provenance, with any relevant conflicts, permissions or gaps.OPS.2supplies selected participant and control views plus correspondence obligations.C.2.1governs the claim-bearing account episteme;A.10governs evidence reliance;A.15.8governs the general Work/WorkPlan performance-configuration and recovery question.C.30.LCA,B.2.5,C.27.TA,C.27, andA.3.3govern the conditional control structure, relation, and rate/dynamics claims. OPS.4 retains operation-specific commitments, state, intervention, authority/evidence, and consequences.OPS.5later consumes current eligible demand, commitments, and uncertainty for admission.OPS.6consumes case state and permissible next Work.OPS.15andOPS.18remain 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.