fpf.tools
Library / Operations Management Principles Framework
Jump to passage
In this reading
Source · lines 1042–1077

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:05:20 UTC

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

Result positionRequired content
use boundaryParticipants, actions or decisions, horizons, first useful result, and truthful stops.
subjects and commitmentsExact OPS.3 subjects and direct relations; commitment parties, content, conditions, status, and authority.
current claimsClaim content, effective scheme, time/horizon, conditions, uncertainty, and receiving action.
evidence and provenanceSources, observations/results, carriers, transformations, versions, reach, and missing evidence.
permissions and authorityRead, write, annotate, accept, hold, release, and change relations with their scope and basis.
disagreement and gapsConflicting or missing claims, affected decisions, specialist returns, and non-admissible compression.
next decisions and WorkEnabled, blocked, awaiting, or returned actions; required condition and responsible participant.
participant viewsSelected claims, subject correspondence, explicit scope of omitted material, conflict cues, return route, and access limits.
refresh and recoveryUpdate or expiry conditions, handoff/recovery observation when current, and smallest reopen rule.

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.