Proposals — the GAP register
A GAP (GAA Proposal) is the written unit of change to the Standard.
Anyone may author a GAP. Acceptance rides the Institute's existing change-governance path — steward review against the charter's principles, the outcome recorded with reasons on the proposal of record. Standing in this process is earned by the conduct of the proposal — the problem stated first, the change grounded in implementation evidence — not granted by any status. The register below is complete: it currently holds the steward's own proposals, recorded in the same format any author would use, and labeled as steward-authored.
The GAP format
One page per proposal, six fields, nothing optional:
| Field | Contents |
|---|---|
| Number | GAP-<n>, assigned in submission order, never reused. |
| Title | One line naming the change, not the motivation. |
| Status | One of Draft · Accepted · Superseded · Withdrawn. |
| Motivation | The problem first: what the specification fails to say, says wrongly, or says ambiguously. |
| Specification delta | Exactly what changes, cited by requirement ID (GAA-*)
or section where IDs do not yet exist. |
| Disposition record | Who ruled, when, and where the outcome is sealed — a chain id an independent party can re-derive, and the commit that carried the change. |
The register
| Number | Title | Status | Author |
|---|---|---|---|
| GAP-1 | Stable requirement IDs and uniform numbering (the canonical itemized edition) | Accepted | steward |
| GAP-2 | Descriptor schema: converge served descriptors on the six required fields; never fork the schema | Accepted | steward |
| GAP-3 | An explicit data-appetite declaration in the discovery descriptor | Accepted | steward |
Every disposition below cites a real sealed record. The chain ids re-derive keyless from the governed ledger's public verify endpoint — each GAP page carries its own verify chip, so the claim is checkable where it is made.