GAP-1 — Stable requirement IDs and uniform numbering

Motivation

The specification's normative content was complete but cited by section name ("§2A", "§Receipts", "§Site-Integration") — coordinates that break on every renumbering, and that force a crosswalk or a conformance test to cite a paragraph rather than an exact requirement. The wedge of this specification is citability; a citation that a rename can invalidate is not citable.

Specification delta

• Every normative statement receives a stable requirement ID of the form GAA-<FAMILY>-<n>, deep-linkable (e.g. /standard/text#GAA-COMP-2); load-bearing declarative contract clauses receive clause anchors without altering their stated strength.
• Named sections are renumbered to one integer sequence.
• Four sections a peer specification carries are added: a consolidated §Conformance, §Security Considerations, §Registry, and split §References — with two new requirements (GAA-SEC-1, GAA-REG-1), and no others.
• A content-loss guard proves the transform pure: before/after normative-statement counts reconcile at 20 → 22 with zero statements lost and exactly the two directed additions.

Disposition record

Proposed at the steward's design seat and ruled going-forward by the founding operator on 2026-07-24; executed 2026-07-25. The executed change was carried by governed commit b98cbe0c06 in the steward's repository. (The chain id formerly cited here addressed the steward's whole commit record rather than this one act, and was withdrawn on 2026-08-28.) The result is the current revision: /standard/r1/ (frozen) and /standard/text (living), recorded on the version history.