Site Administrator Workflow
Administrators classify every PR and coordinate its named reviewers. Repository admin permission determines administrative authority.
/review classify <new|major|minor|editorial|dev|code> <doc_location|->
/review author <login>
/review assign <peer|lead|editor|director> <login>
/review complete <stage>
/review waive <stage> [reason]
/review restart <stage>
/review ready
Use /review author to record additional authors not represented by the PR creator. Assign exactly one authoritative reviewer to each human stage. Non-admin authors and reviewers must be different people across stages; administrators may act in any role. Use complete only for an actually completed administrator-controlled stage, including AI technical editing. Use waive for an explicit exception; its reason is optional and the outcome remains distinct from approval.
Completed and waived stages persist until an administrator intentionally restarts one. New commits alone do not reset a stage. Replies and thread resolution are useful collaboration practices, not automated gates. The controller maintains one low-noise summary and sends actionable handoffs without recurring reminders.
New-document publication
After the Content PR merges to main and automatically deploys as a draft:
/review start-director <doc_location> <version|unversioned> <login>
/review cancel
/review retarget <doc_location> <version|unversioned>
The first command creates a separate Director Review PR using a stable synthetic baseline and assigns one Director. Director approval or an administrator waiver creates the Publication PR automatically. Verify that the Publication PR contains only the selected document, source, related assets, manual attribution updates, and draft removal. It is an administrator delivery step, not another Director round.
Only administrators merge to main and approve the protected production environment. Production builds automatically from main; never publish an author or Director branch. If publication conflicts with intervening document changes, reconcile with /review retarget without resetting completed review. If deployment fails, preserve review state and the stable Director preview, correct the problem through main, and retry.
Activation credentials, GitHub App identity, branch rulesets, required-check sources, and environment settings are documented in the repository-root activation checklist.