Adding an entry, and who decides

A registration is a standards-track change and follows `GOVERNANCE.md`: proposed as a GitHub issue or pull request (§3), decided by the maintainers (§4), and recorded where §4's table says — the ADR, the checklist, CHANGELOG.md, COMPATIBILITY.md. A registration that opens a value space, or that changes what a token means, is normative under §3.1 and requires an ADR before it is implemented.

Mechanically, an addition is: a new snapshots/<n+1>/ directory carrying the whole registry (every earlier entry, plus the new one), its digest computed and recorded in this README's table, and one new entry appended to HISTORY.md. Editing snapshots/1/ is never how an entry is added.

Maintainers are the owners named in `.github/CODEOWNERS` — today one person, as GOVERNANCE.md §2 states plainly. That file is the roster of record; this document keeps no second copy of it to drift out of sync.

Appeals. A refused registration is an objection, and it is heard through GOVERNANCE.md §5: a public GitHub issue labeled objection, or the private route in `SECURITY.md` where the substance is sensitive. Every objection gets a written disposition — accepted, accepted-with-changes, or rejected-with-reasons, with the reasons written down — recorded in the ADR the objection concerns. There is no time-based auto-dismissal: an objection stays open until it has a disposition.