# Human reviews

Human reviews give an App a saved queue of proposals that a person can accept, correct, or reject against retained evidence. A review records the payload, linked sources, current revision, status, and change history. Generation can prepare proposals, but it never approves them.

## Start from the queue

Open the App's review experience and select a proposal. Read its full saved content, not only the editable fields the App highlights. The App can expose selected text, boolean, and date fields while preserving other payload information.

Check the source documents and their roles, then capture the selected evidence before approval. Capture preserves an independent verified copy, so later changes to the original do not silently change what you approved.

## Make a decision

Only a verified human can approve or reject. The Assistant can help prepare a review, edit a proposal, or capture evidence where permitted, but cannot impersonate your decision. Sharing an App does not automatically grant access to its owner's review ledger; the review experience has its own ownership boundary.

Approval binds the exact saved payload, source links, and capture receipts at the reviewed revision. It attests to that basis. It does not prove that the citations, interpretation, or conclusions are substantively correct.

## Changes remain visible

Edits, source relinking, and new capture actions return a review to pending so the changed basis requires review again. Notes preserve the status. History records the previous values and who acted.

If the App offers generation or dated projections, read their receipts and selected date. An approved source review and a projected domain interpretation are different things.

Begin with [sources and capture](/docs/reviews/sources-and-capture), [decisions](/docs/reviews/decisions-and-status), [editing](/docs/reviews/editing-and-notes), and [history](/docs/reviews/history-and-receipts). For document removal, use [deletion approvals](/docs/documents/deletion-approvals), which follow a separate revision-bound ticket flow.