Who reviews what comes from who owns what
Org roles decide what someone may do. Responsibilities decide who is asked: engineering managers and architects (optionally for an area) per product, and code owners per asset. They route reviews, triage and notifications; they never grant permissions.
Each product picks a workflow: Open (the default; reviews are optional) or Guided (reviewers are suggested from responsibilities, and activating unapproved work asks for confirmation).
Review the plan before effort is spent
A PR review comes after the work is done. A plan review lets code owners stop a misdirected change before any tokens or people are spent on it. Suggested reviewers come from the plan’s target assets and the product’s responsibilities.
- Approvals are pinned to a revision. Changing the plan’s scope, specs or description asks reviewers to look again.
- Agents can request reviews and comment, but only people approve.
Approve a version, not a moving target
Reviewers approve, request changes or comment on a specific spec version. A later revision marks earlier approvals outdated, and approvers and plan owners are told. Required reviewers must approve before the review completes.
Feedback anchored to the text
Select text in a spec to comment on it, ask a question or suggest a change. Threads can be resolved, @mentions notify people, and anchors survive later revisions (or say when the quoted text changed). Viewers can comment too.
