A reviewer's access to a run or a proposal is checked against their own domain and permission-tag scope—not a blanket "see everything" grant.
Not how you work.
What you're accountable for.
A personalised view of what a named reviewer is accountable for approving is in development. The underlying data is already real and already enforced: reviewer roles, domain scope and a live review queue exist today—what's in progress is presenting that as a personal, browsable graph rather than a queue you work through one item at a time.
REAL TODAYReviewer roles
Reviewer roles
are already enforced.
Open drift alerts, conflict reviews and skill-draft proposals already route to the right reviewer today.
A personalised graph view of that accountability, instead of a filtered queue.
In progress.
Not shipped today.
There is no personal-graph visualisation in production yet. Reviewer scoping and the review queue behind it are already real.
See the real provenance path →