Governance

Roles, how a change is proposed, how a decision is recorded, and how an objection is heard.

1. OverviewThis document is the public governance process required by `VERSIONING.md` §3.4 condition 6 before any release from 1.1 onward can publish: who decides, how a change is proposed, how an objection is heard, and how a decision is recorded.
2. §1ScopeThis document governs the standards track: everything `CONTRIBUTING.md` places in its high-ceremony tier — standards/ (every release directory and the current draft) and the frozen historical locations spec/ and lexicons/;
3. §2RolesThe truth, stated plainly: there is one maintainer today — .github/CODEOWNERS's catch-all, * @trentdavis78 — with authority over the entire repository, standards track included.
4. §3How a change is proposedAny change starts as a GitHub issue or a pull request — the same entry points CONTRIBUTING.md describes for the reference pipeline.
5. §4How a decision is made and recordedWho decides: the maintainers named under .github/CODEOWNERS — today, one person.
6. §5How an objection is heardWhere to raise one: a public GitHub issue labeled objection.
7. §6External review periodsThis implements VERSIONING.md §3.4 condition 5.
8. §7Amending this documentThis document is standards-track material and amends under its own process: proposed by issue or PR, a normative change to what it commits the project to (§3.1) goes through an ADR, decided by the maintainers named in .github/CODEOWNERS (§4
9. §8What this document does not claim
10. See also