For ordinary development or review, read Contributing and
Quality Standards, then the repository's local
AGENTS.md, development instructions and required checks. Local requirements
remain authoritative; the organisation baseline does not lower stronger gates.
| Task | Reference |
|---|---|
| Change CI or branch protection | Workflow contract, rulesets; enforcement design when changing that boundary. |
| Prepare or operate a release | Local release guide and release trust, then the applicable Profile A or Profile B. |
| Implement bootstrap templates | Approved contract and examples. |
| Change contribution or support intake | Community inheritance and overrides; support, security and conduct define reporting boundaries. |
Current ownership and evidence live in existing issues: quality #65 and sibling verification #136; release acceptance #57, administrative readback #59, delivery #81 and onboarding #85. Onboarding acceptance remains mandatory before feature completion. UI/manual acceptance and Plugin Library deferrals remain until an explicit newer owner decision supersedes them; automated success cannot clear a manual hold.
Earlier guidance and evidence remain available through Git history for optional provenance and old-link recovery.