§2 Roles

The truth, stated plainly: there is one maintainer today — .github/CODEOWNERS's catch-all, * @trentdavis78 — with authority over the entire repository, standards track included. That file is the roster of record; this document keeps no second copy that could drift out of sync. Every decision below is currently one person's decision, made in public, in the venues §4 names. That is a description of fact, not an aspiration to a committee that does not exist.

2.1 Adding a maintainer

A maintainer is added by (1) a pull request adding them to .github/CODEOWNERS (path-scoped if their ownership is partial, the catch-all if it is not) and (2) a decision by the existing maintainers — today, the sole maintainer — recorded as an ADR under §3.2's convention, stating who, the scope of their authority, and the date. The CODEOWNERS PR merges only after the ADR is Accepted, not before: the ADR is what makes it a decision of record, and the CODEOWNERS diff is a mechanical consequence of that decision, not the decision itself.

2.2 Removing a maintainer

Voluntary removal is a pull request removing the person from .github/CODEOWNERS, effective on merge — no vote is needed for someone to step down. Removal for cause follows the same ADR process as §2.1, decided by the remaining maintainers, stating the reason.

This process has no mechanism for removing a sole remaining maintainer for cause — there is no other maintainer to decide it. That is stated honestly rather than papered over with an escalation path to a body that does not exist.