Corrections and evidence

The correction workflow retains the prior revision, records a correction run and compensating step, creates a successor revision and raises a verification follow-up. The Automation Owner can change the path forward while the Audit Reader still sees what previously ran and why a correction was needed. State history keeps the actor, source revision, operation key and reason for recorded changes.

Evidence documents give a reviewer supporting material for a definition. Their title, date, external reference, attachment and verifier help the team explain a decision later. The review decision itself holds the source revision, reviewer, decision, date and reason. Keep these records linked to the definition rather than copying a narrative into a disconnected note.

• Earlier revision. Preserve the version and run trace that produced the original result.
• Successor. Prepare a new revision and validation path for the changed instructions.
• Verification. Assign a follow-up with a due date, status and resolution to a named person.

Decide what counts as a correction requiring a compensating action and who may start it. Agree what evidence the follow-up assignee must inspect: the earlier result, the compensating step, the successor revision and the outside receipt where applicable. Define when a follow-up can be completed and how an unresolved external outcome is escalated to the Operations Operator.

For the pilot, choose a completed execution with a simple, checkable result. Create a successor revision through the correction workflow. Compare the original and correction runs, then ask the assignee to document the resolution. The Reviewer should be able to inspect both revisions without assuming the new one retroactively changed the first decision.

An automation sent an accepted action using an earlier mapping version. The team learns that the source value was interpreted incorrectly. The Automation Owner invokes correction, which retains the original revision, records a compensating step and creates a successor. The Integration Steward checks the mapping change, while the Operations Operator compares the provider receipt with the correction run. The follow-up stays open until an assigned person verifies the outcome.

If the provider has not confirmed the compensation, keep the follow-up open and the run available for reconciliation. Do not close the task solely because a successor definition exists. Once the outside result and state history agree, record the resolution and completion date.

• Open correction follow-ups — Find assigned work awaiting verification.
• My follow-ups — Check the due date and resolution for your own correction tasks.
• Completed review decisions — Compare the decision on each affected revision.

Use correction and verification to examine the earlier run, successor and follow-up together.