Human review
Human review is a decision made by someone with the authority the playbook needs. A domain specialist can settle a disputed match or correct a proposed plan. An authorized approver decides whether a protected action may take effect.
Choose the right decision
Section titled “Choose the right decision”Domain judgment and authorization
Section titled “Domain judgment and authorization”The person who knows how to resolve a data discrepancy may be different from the person allowed to authorize a write. Route each decision to the right role in the destination workspace. Show the source evidence, the question, any uncertainty, and the consequence of each option. When a step requires a decision, hold its dependent work until a valid response arrives.
| Review point | Example question |
|---|---|
| Intake | Which of these two records refers to the requested organization? |
| Plan | Is this the right sequence of assignments and evidence checks? |
| Protected effect | May this exact message go to this recipient from the displayed account? |
| Definition change | Should this revised rule and its eval become the team’s next version? |
Example review note
Section titled “Example review note”This illustrative review note shows the evidence to retain.
Goal: Verify the shortlistQuestion: Do these two entries describe the same firm?Evidence: Source URL A, registry entry B, conflicting office addressesDecision: Keep separate; business registration numbers differResult: Update the draft and recheck the downstream proposalFeed a decision into the next revision
Section titled “Feed a decision into the next revision”Keep the decision with the run, evidence and definition revision. Convert recurring issues into proposed mappings, instructions, or eval cases. Have the specialist validate the change with the relevant evidence before publishing. A new revision affects later runs and their decisions. Keep the earlier result available for comparison.
See specialist review and improvement, approvals, and evals.