Review and Remediation

Validation opens a pending review decision for an exact integration revision. The Independent Reviewer examines the mapping version, connector context, validation trace and supporting evidence. They approve, return or reject that revision with a reason. The Integration Owner can then enable approved work or revise what was returned. The decision record keeps the reviewer and source revision visible after execution.

A failed or uncertain sync needs a separate operating response. Follow-up actions give the Remediation Owner a title, due date, assigned person, status and resolution. The operator can connect that action to the definition and bring in the run, attempt and per-scope output that explain the issue. Closing the action is a recorded resolution, not a change to the historical receipt.

• Independent review. The decision belongs to the exact revision and a named reviewer, separate from the definition owner.
• Evidence. Documents can support a mapping or sync outcome and record who verified them.
• Assigned resolution. Follow-up actions track unresolved work through completion while retaining the earlier failure.

State history records each definition transition with a revision, actor, operation key and reason. It gives the Audit Reader a chronology beside the decision and evidence. The team can explain why a revision was enabled, why a correction was made and who accepted the final resolution.

Assign a reviewer who can challenge the owner’s mapping and endpoint choices. Agree what evidence is required for a new mapping version, a changed connector profile and a compensating output. Define when a Returned decision requires the owner to revise and validate again. For failures, agree when an operator creates a follow-up, who receives it and what proof closes it. Keep the status of a follow-up separate from the status of the definition it concerns.

The review path should include a real rehearsal. Use a revision that passes validation, then one with an incorrect transform. Check that the reviewer can return the second case with a reason and that the owner can respond without overwriting the original decision.

Suppose a run was completed but the destination later reports a wrong value. The operator brings the execution, receipt and mapping version to the owner. The correction workflow retains the executed revision, records a compensating step, creates a successor revision and compensating sync output, and opens verification follow-up and review. The reviewer examines the successor against the original problem and records their decision.

The Remediation Owner closes the follow-up only after the corrected output has been checked. The Audit Reader can then follow the original status history, the correction run, the new decision and the resolution. That chain makes the handoff useful even when the people who operated the first run are no longer on shift.

• Pending Review Decisions — Exact revisions waiting for an independent decision.
• Open Follow Up — Assigned failure and correction work by due date.
• Revision History — Status transitions with actor, reason and revision.

Read review a revision and correct an executed revision. Roles explains the operating handoffs.