Review queue
A single queue of paused workflow runs, missions awaiting review, and pending action proposals, with a REST API to decide each one.
Last verified
A review queue is one place where every item waiting on a human decision collects, regardless of which part of the system produced it, so a reviewer never has to check three different dashboards to find pending work.
What lands in it
Vocion's queue holds three kinds of item: workflow runs paused at an
approve step, missions awaiting a check, and pending action proposals from
trust.yaml thresholds not being met. GET /api/v1/reviews returns this
queue, filterable by kind (workflow | mission | action) and by
assignedTo (a user id, or unassigned for triage); POST /api/v1/reviews/decide takes {kind, id, action, reason?, editedInput?}
where action is approve or reject, and editedInput lets a reviewer
correct a field rather than only accept or reject as-is.
Why it matters in production
A gate that only exists as a pause in one workflow definition does not give anyone a way to see everything pending across every agent at once. A single queue with a stable API means a team can build its own review UI, a Slack digest, or an on-call rotation on top of the same underlying data, instead of polling each workflow separately.
How Vocion implements it
The routes are thin wrappers over apiListReviews and apiDecideReview in
services/writeApi.ts
(packages/core/src/app/api/v1/reviews/route.ts,
packages/core/src/app/api/v1/reviews/decide/route.ts), authenticated by a
tenant Bearer token or dashboard session. The gate itself is the approve
step type on a workflows/<slug>/workflow.yaml manifest, documented in
docs/entities/workflow.md;
the dashboard view is /dashboard/review.