Review decisions and status

Approve, reject, or record a non-substantive result at the exact reviewed revision.

A review decision records a person's judgment about a particular saved proposal and its captured evidence. Read the payload and every selected source before choosing an action.

Approval

Approval requires a verified human decision and complete capture of the linked source set. It binds the exact payload, links, and capture receipts at the reviewed revision. An Assistant-generated statement that a review was approved is not a substitute for the human decision control.

Approval does not certify the independent accuracy of the source, OCR, citation interpretation, or business conclusion. It records that the person accepted that proposal on that evidence basis.

Rejection and non-substantive results

Use rejection when the proposal should not be accepted. Where the App offers a non-substantive decision, use it for the domain meaning described by that App rather than treating it as a general replacement for reviewing the source. The action is still recorded in history.

The App owns domain-specific interpretation: the platform records the decision and basis but does not invent a universal legal or business meaning for it.

What resets status

Editing the payload, changing source links, or capturing evidence returns the review to pending. Those actions change what is being reviewed. Adding a note preserves the existing status because a note is commentary rather than a replacement basis.

A later edit therefore requires a new decision. Do not assume an earlier approval continues to cover a newly changed value.

Conflicts

A decision checks the expected revision. If another action changed the review, reload the current state and inspect it before deciding again. For a lost response, inspect the saved event and status before resubmitting.

See editing and notes, history, and uncertain requests.