Validation and review

When an Automation Owner validates a selected revision, the validation workflow records an operation run and its step trace. It moves the definition to Validated, opens a pending review decision and appends state history. The owner can therefore hand the Reviewer a specific revision and a trace of what validation did, instead of a general assurance that the latest draft looked right.

The Reviewer sees the source revision, the decision, the evidence reference and the reason. Approval, return and rejection are distinct outcomes. The Reviewer makes the decision; a validation result alone does not make a business approval. Keep the person preparing the definition separate from the person deciding whether that revision can proceed.

• Validation trace. The durable run and steps show what was checked for the selected revision.
• Decision record. The pending decision becomes the reviewer’s recorded approval, return or rejection.
• History. A state change identifies its actor, revision, operation key and reason so later work can be traced.

Set the evidence expected for a review. The team may require a sample input, the intended connector and a readable account of the expected output. Decide who is eligible to review each organization’s definitions and how a returned revision goes back to its owner. Make the reviewer’s authority explicit in the access rules, because seeing a pending item does not itself grant permission to decide it.

For the first rehearsal, use a revision whose inputs and result are easy to inspect. Run validation, locate the corresponding operation and step records, then open the pending decision. Check that the reviewer sees the intended source revision before recording a decision. Keep the original validation trace when the owner revises the definition.

An owner updates a definition’s input schema for a service request. The validation workflow records its run and moves the revision to Validated. A separate Reviewer checks the schema and the step trace, then records approval with an evidence reference. The Operations Operator can use the reviewed revision for execution. If the Reviewer returns it instead, the owner records a new revision and sends that version through validation; the returned decision stays attached to the earlier review.

This case should also test disagreement. Ask the reviewer to return an unsuitable version with a reason, and confirm that a successful validation trace does not erase that decision. State history should still explain when the definition changed and who acted.

• Pending review decisions — Open the revisions waiting for a named review decision.
• Completed review decisions — Inspect the dated approval, return or rejection and its reason.
• Definitions by status — Find the definition that each decision concerns.

Use validation and review and correction and verification to examine both the first decision and later changes.