The review queue becomes a team queue
Pending work now routes to a specific person — per-person queues, an unassigned triage lane, and snooze — so a workspace with many humans can actually divide the approvals.
The unified review queue gave every gated action — skill, workflow, mission — one
place to be approved. But it was one queue for the whole org: fine for a solo operator, wrong for a
team. This release makes it multi-user (v1.38): every pending item can be routed to a person.
Route, filter, snooze
An item carries an assignee. Route it to a teammate; pull your queue; leave the rest in the unassigned lane for triage; snooze what isn't now:
# my queue
curl -H "Authorization: Bearer $VOCION_TOKEN" \
"https://your-install/api/v1/reviews?assignedTo=<userId>"
# the unassigned / triage lane
curl -H "Authorization: Bearer $VOCION_TOKEN" \
"https://your-install/api/v1/reviews?assignedTo=unassigned"
# route an item to a teammate
curl -X POST -H "Authorization: Bearer $VOCION_TOKEN" -H "Content-Type: application/json" \
-d '{"kind":"mission","id":42,"assignedTo":"<userId>","note":"SDR follow-up"}' \
https://your-install/api/v1/reviews/assign
# snooze until later
curl -X POST -H "Authorization: Bearer $VOCION_TOKEN" -H "Content-Type: application/json" \
-d '{"kind":"workflow","id":987,"until":"2026-07-02T15:00:00Z"}' \
https://your-install/api/v1/reviews/snooze
Snoozed items drop out of the active queue until their time; assignment is idempotent, so reassigning
just moves the owner. Managing the queue is the same approve capability as deciding — the permission
model is unchanged, it just gained a who.
Why it's a foundation, not a feature
A team system is only real if work reaches the right person. This is the substrate the rest rides on: a revenue team where pipeline questions land with ops, proposal reviews with delivery, and pricing with the founder — each person's queue their own, nothing lost in a shared firehose. The policy for who owns what is workspace config; the platform now provides the mechanism.