# GA-R structural rulings (grounding audit Phase 4)

Delivery per the operator's recorded directive (register, Phase-4 directives
item 5): one draft per exchange, held until ruled; every RATIFIED ruling's
Status quotes the operator's exact utterance (GA-R5 discipline, applied to
its own drafting). Implementation of ratified rulings happens in Phase 5.
Order: GA-R3, GA-R5, GA-R1, GA-R2, GA-R6, GA-R4, GA-R7, stage-status
vocabulary A/B.

---

## GA-R3 -- D-number admission criteria

**Status: RATIFIED 2026-07-18 (operator, with amendments A1 + A2).**
Exact utterance: "Ratify with A1 and A2: Amendment A1 (sharpens 1(b)):
'(b) a Roosevelt-delta implication, tested as: a future Roosevelt build
session would need to grep this decision before touching a built surface.
Mentioning Roosevelt, or recording a Roosevelt-era preference, does not
qualify; changing what gets built or how it transfers does. Where a single
entry mixes both (D-129: an OPS plugin install plus an ARCH transfer
profile), the class follows the dominant purpose and the ARCH fragment is
split into its own entry or an amendment to the governing ARCH decision.' ;
Amendment A2 (completes rule 2): 'Operational choices whose configuration
must outlive the stage are recorded in the relevant as-built document (the
configuration-of-record authority per the GA-R1/GA-R2 division); the
runbook carries the how, the as-built carries the what-is.'"

**Ratified ruling text (as amended):**

1. A new D-number is admitted ONLY if the decision has at least one of:
   (a) architectural consequence beyond the current stage;
   (b) a Roosevelt-delta implication, tested as: a future Roosevelt build
   session would need to grep this decision before touching a built
   surface. Mentioning Roosevelt, or recording a Roosevelt-era preference,
   does not qualify; changing what gets built or how it transfers does.
   Where a single entry mixes both (D-129: an OPS plugin install plus an
   ARCH transfer profile), the class follows the dominant purpose and the
   ARCH fragment is split into its own entry or an amendment to the
   governing ARCH decision;
   (c) supersession or material amendment of an existing D-number.
2. Everything else -- tool options, service settings, plugin lists, host
   conveniences, process notes -- is an OPERATIONAL choice: it gets a
   runbook edit or (until GA-R2 lands) a changelog line, and NEVER a new
   D-number. Operational choices whose configuration must outlive the
   stage are recorded in the relevant as-built document (the
   configuration-of-record authority per the GA-R1/GA-R2 division); the
   runbook carries the how, the as-built carries the what-is.
3. Every register entry gains a mandatory one-word class tag: ARCH or OPS.
   New entries are ARCH by construction (rule 1); the tag exists so the
   back-catalog stays findable.
4. One-time review (Phase 5): D-121..D-129 are class-tagged in place. OPS
   candidates per the charter: D-126, D-127, D-128, D-129. Numbers are
   append-only and are KEPT regardless of tag. Per amendment A1, the
   D-129 ARCH fragment (the Roosevelt metal-edge transfer profile) is
   split into its own entry or an amendment to the governing ARCH
   decision during this review.
5. Doubt resolves DOWN: if admission is arguable, it is OPS -- a runbook
   line can be promoted to a D-number later; a diluted register cannot be
   un-diluted.

**Implementation (Phase 5):** class-tag sweep of the register template +
D-121..D-129 one-time review (incl. the A1 D-129 split); skill sweep
carries the admission test.

---

## GA-R5 -- Ruling gate discipline

**Status: DRAFT (delivered 2026-07-18; awaiting operator ruling).**

**Proposed ruling text:**

1. Rulings are gated like mutations: ONE decision presented and ruled per
   operator exchange. Batch adoptions ("adopt all of the above") are
   invalid; each decision gets its own exchange.
2. Every ruling's Status line quotes the operator's exact utterance and
   its date. A Status line without the quoted utterance is not a ruling.
3. Scope: D-number rulings and amendments, GA-R ratifications, SEC-row
   dispositions, and any standing policy or preference recorded on any
   surface (including memory surfaces, per GA-R7 when ratified).
4. A ruling exists only when committed: an in-session operator answer is
   written to its Status line and pushed in the same session, before any
   dependent work proceeds. An unrecorded ruling is not a ruling.
5. An ambiguous or template-form utterance (unfilled brackets,
   placeholders) rules NOTHING: the recorder stops and asks; nothing is
   inferred from it.

---

Drafts not yet delivered: GA-R1, GA-R2, GA-R6, GA-R4, GA-R7, stage-status
vocabulary A/B (in that order).