Design Pattern · September 2026
Operational truth
Trace an operational claim to independent evidence and distinguish intended, reported, recorded, inferred, observed, and verified state.
Under the pillar Operational Truth™, Risk, Liability, and Outcomes
Inputs
A material operational claim, source systems, events, timestamps, actors, derived records, and known conflicts.
Method
Trace claim, derived evidence, source event, source system, actor or device, and time. Record authority, freshness, conflict rules, and missing events.
Output
A queryable evidence chain and the gap between reported and observed state.
Boundary
A complete record can still be false. Operational Truth™ does not prove causality.
Stop
Stop delegation when the state needed for safe action cannot be established economically.
Put this to work
Operational truth application record
Apply Operational truth to a real piece of work and record what happened.
- For
- Operators redesigning a team, service, or AI workforce.
- What you keep
- A operational truth application record you can review, revise, and send.
- What counts as sound
- Names a real setting
- Shows the work before and after
- Records exceptions
- Uses an observable result
- Ends with keep, revise, or stop
Do not infer that a task can move merely because it can be described.
Nothing entered here is stored or sent. Review the prompt before sharing confidential, personal, patient, or privileged information.
Review the prompt
You can leave any field blank. The prompt will mark it as not provided.
If the record survives your review, send the question, evidence, unknowns, and requested next step.