Reviewers and Decisions
Approval is a human decision with names attached. The governance rail runs that workflow: who reviews, what they decided, and what happens next; every step recorded.
Assign Reviewers
The package owner or an org admin assigns reviewers from the organization's members. At least one reviewer is required before submitting; the rail shows the roster and progress ("1 of 2 approved") throughout. Separation of duties applies: the review is performed by people other than the author whose work is being judged.
Submit for Review
Submitting moves the package from draft into review and puts it in front of the assigned reviewers. Reviewers see the same package the author does: the design, the Assurance results, the readiness board, and the evidence panel; nothing is summarized away from them.
The Reviewer's Two Actions
Available only when the readiness board is clear. With the required approvals in, the package becomes approved: the documents lock immutably, the approval evidence is captured, and the approval baseline is taken; the reference point drift detection watches from then on.
Sends the package back with a note explaining what must change. The package moves to changes requested: the author addresses the feedback and resubmits, starting the next review round. Reviewers see a waiting notice until the resubmission arrives.
Who Sees What
| Role | Experience |
|---|---|
| Author | Submits, resubmits after changes, watches reviewer progress |
| Reviewer | Approve / Request Changes, with the full package in view |
| Everyone else | The status and roster, read-only; reviewer names resolve for every member |
Decisions Are Recorded
Every submission, decision, and note lands in the audit trail with its actor and time; review history is part of the package's permanent record.