Design Pattern · September 2026
Evidence Supply Chain
Keep every consequential operational claim connected to its source, custodian, transformations, and useful life.
Under the pillar Operational Truth™, Risk, Liability, and Outcomes
Inputs
Claims, source events, systems, transformations, timestamps, custodians, access rules, and known failure history.
Method
Map provenance from the real event to every derived field and decision. Set source priority, conflict handling, freshness, authenticity checks, and retention.
Output
An evidence chain a reviewer can follow in both directions.
Boundary
Provenance shows where a claim came from. It does not make the source correct.
Stop
Stop using a claim when its source, transformation, permission, or freshness cannot be established.
Put this to work
Evidence Supply Chain application record
Apply Evidence Supply Chain to a real piece of work and record what happened.
- For
- Operators redesigning a team, service, or AI workforce.
- What you keep
- A evidence supply chain 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.