Review Queues

Summary

Review queues are not generic inboxes. They are scoped projections of work that needs a human decision before automation can safely continue.

Problem

When every failure lands in one untyped queue, operators cannot tell whether they are approving, correcting, routing, or diagnosing. Engineering also loses the ability to reason about queue ownership.

Principle

A review queue should expose a specific decision contract and a bounded set of actions.

Platform Shape

POA presents stage and review-item views from workflow-backed state. Precon uses opportunity, solicitation, portal, and document review surfaces. In both cases the UI reads service-built projections rather than joining raw analytics tables or reinterpreting external payloads.

Source Evidence

• docs/domains/poa.md
• docs/domains/preconstruction.md
• services/workflow/reviews
• app/web/app/poa-greenfield

Related Reading

• docs/engineering/concepts/cases-issues-events.md
• docs/engineering/architecture/serving-snapshots.md