A review queue with authority

Give reviewers evidence, reasons, time, and an auditable decision state.

DIRECT ANSWER

A human review queue is an operating component, not a disclaimer. It needs assigned work, source evidence, observable rejection reasons, escalation, service limits, and the authority to stop or reverse the workflow.

SYSTEM FLOW

Make every boundary visible.

01proposal
02queue
03assign
04inspect
05decide
06escalate
07audit

DESIGN DECISIONS

Three decisions carry the architecture.

Show the source and change

Present the input, retrieved evidence, generated proposal, and exact difference from the current record.

Use reason codes

Capture missing evidence, unsupported claim, prohibited data, wrong scope, duplicate, and escalation explicitly.

Measure review capacity

Track queue age, reviewer minutes, correction patterns, and unassigned work before increasing volume.

FAILURE MODES

What breaks the boundary.

Reviewers approve without seeing sources
Queue growth silently turns review into a rubber stamp
The person who finds a problem cannot pause the system

VERIFICATION

Evidence before release.

Missing-source rejection
Escalation path test
Capacity threshold alert
Stop-authority rehearsal