Independent review

Scheduling creates a pending review decision against a bot definition revision. The Bot Reviewer examines that revision, its queue and supporting evidence before recording a decision. The decision record holds the source revision, reviewer, decision date, reason and evidence reference. Its decision values distinguish Pending, Approved, Returned and Rejected. A returned revision needs correction; a rejected one retains the decision and reason for later inspection.

The reviewer should be independent of the definition owner. The scheduling workflow resolves an independent reviewer and creates the pending decision. The execution workflow then acts on an eligible reviewed definition. Keeping the review on the revision prevents a later edit from borrowing approval earned by an earlier version.

• Inbox. Pending decisions identify the revisions awaiting a person.
• Decision. Approval, return and rejection remain explicit outcomes with a reviewer and date.
• Evidence. A reference or supporting document gives the reviewer a traceable basis for the call.

Choose the team that makes the review decision and its substitute when the usual reviewer is absent. Agree what the reviewer needs to see: queue policy, source mapping, runtime version, intended source record and any supporting document. Define a clear reason format for returned or rejected work. Agree how the operator is notified to make a successor revision and how that new revision comes back for review.

For a bot that posts a daily extract, the reviewer can compare the scheduled revision with the applicable queue policy and source field mapping. If the source mapping has changed, the reviewer returns the decision with a reason. The operator changes the definition and brings forward a new revision. The old decision still explains why the earlier revision did not proceed.

Open a pending decision and identify its source definition and source revision. Check that the reviewer is a different person from the owner. Inspect the evidence reference and supporting documents. Record a test return with a concrete reason; then trace the successor revision through a new decision. In a separate test, approve a valid revision and check that the execution path refers to that approved revision.

• Review inbox — Pending decisions tied to source revisions and assigned reviewers.
• Approved revision decisions — Decisions that permit eligible execution.
• Verified evidence documents — Supporting documents linked to a definition and verifier.

See Review a revision and Execute and verify a run.