Apply GH-DEC-2026-017 to the Taxonomy layer declaration and close RMASTER-WP-0027.

INTENT.md governs; layer.yaml is marked derived from it. standard_version is
removed from both. The value Taxonomy is unchanged: the ruling closes the
vocabulary at four tokens and Taxonomy is one of them. ADR-0010 amended by
revision (accepted-2). No checker in this repository reads the declaration.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703

INTENT.md

@@ -2,7 +2,6 @@
 layer: Taxonomy
 role: null
 standard: netkingdom-security-layer-model
-standard_version: "0.7"
 companion: net-kingdom/SECURITY-COMPANION.md
 ---
 

docs/adr/ADR-0010-taxonomy-is-an-enumerated-layer.md

@@ -2,7 +2,7 @@
 id: RMASTER-ADR-0010
 title: "Taxonomy Is An Enumerated Layer, Not A Value Outside The Vocabulary"
 status: accepted
-revision: "accepted-1"
+revision: "accepted-2"
 owner: railiance-master
 last_reviewed: "2026-09-21"
 review_interval: 6m
@@ -150,3 +150,47 @@ is a decision that was taken, not an accident of a generator.
 
 Tracked in `RMASTER-WP-0027`. Sent to `gate-house` as input to the §3
 vocabulary ruling on 2026-09-21.
+
+## Revision accepted-2 (2026-09-21) — the ruling
+
+`gate-house` ruled in `GH-DEC-2026-017` (gate-house `decisions/decisions.md`;
+amendments A9, A11 and A12 in
+`gate-house/docs/amendments/v0.8-section-11-declaration-amendments.md`). The
+text above is left as accepted-1 recorded it; this section states what the
+ruling confirmed and what it changed.
+
+**Confirmed, unchanged:**
+
+- Decision 1 and 2. The §3 vocabulary is closed at **four** tokens —
+  `Taxonomy`, `Tooling`, `Engine`, `Staff` (§3 of the ruling, A9).
+  `layer: Taxonomy` is conforming and the validator carried the defect.
+  `flex-auth` has since fixed it (flex-auth `80ffe72`). The value is not
+  changed; the contingency in Decision 5 did not trigger.
+- Decision 3. `surface` was ruled apart from `Taxonomy`, as asked.
+- Scope. This repository is outside §4. The ruling (§4, A11) holds that §11
+  binds §4 repositories only, so our declaration is *declared voluntarily,
+  outside catalog scope*. It was never a §11 non-conformance, and is not one
+  now.
+
+**Changed by the ruling:**
+
+- **Precedence (Decision 4, question 1).** `INTENT.md` frontmatter governs.
+  `layer.yaml` is a derived artifact and now carries `derived: true` and
+  `derived_from: INTENT.md`. The two still agree.
+- **Case (Decision 4, question 2; the casing observation under Evidence).**
+  Comparison is ASCII case-insensitive and a lowercase declaration is
+  conforming, not tolerated. The Evidence observation that the nine
+  lower-casing sidecars "diverge from the standard's own spelling" is
+  superseded: under A9 they conform. Its underlying point — §3 writes
+  `Engines`, §4 writes `Engine` — became A9, which states the token once and
+  makes the §4 column spelling canonical. Our `Taxonomy` is canonical under
+  either reading.
+- **Standard version (Consequences, third bullet).** A layer declaration MUST
+  NOT carry a standard version (§5 of the ruling, A12). `standard_version: "0.7"`
+  is removed from `INTENT.md` frontmatter and `layer.yaml`, not re-pointed at
+  v0.8 as that bullet anticipated. Version-scoped state belongs in a derived
+  conformance record; this repository keeps none.
+
+This repository has no layer conformance checker of its own, so no checker or
+test had to change with the field. `RMASTER-WP-0027-T03` closes on this
+revision.

layer.yaml

@@ -8,6 +8,14 @@
 # declaration from a transcribed review. Form adapted from the kings-guard
 # no-contact shape offered under §11.
 #
+# This file is DERIVED. The declaration is the `layer:` key in INTENT.md
+# frontmatter, which governs (gate-house GH-DEC-2026-017 §1, amendment A11).
+# The two must agree after ASCII case-folding; a disagreement is a finding.
+# No standard version is carried here (GH-DEC-2026-017 §5, amendment A12).
+#
+# railiance-master is outside the NetKingdom §4 catalog. This declaration is
+# voluntary and outside catalog scope (GH-DEC-2026-017 §4).
+#
 # This repository produces terms, family contracts, and standards for
 # workload operations. It owns no runtime position and no state another
 # layer depends on. It is Taxonomy of Railiance operations, not a row in
@@ -18,7 +26,8 @@
 
 schema_version: "0.1"
 framework: netkingdom-security-layer-model
-standard_version: "0.7"
+derived: true
+derived_from: INTENT.md
 repository: railiance-master
 layer: Taxonomy
 declared_by: docs/adr/ADR-0009-netkingdom-security-layer-interaction.md

workplans/RMASTER-WP-0027-layer-vocabulary-ruling.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Hold the Taxonomy layer declaration through the gate-house vocabulary ruling"
 domain: financials
 repo: railiance-master
-status: active
+status: finished
 owner: claude
 topic_slug: layer-vocabulary-ruling
 flavor: planning
@@ -81,7 +81,7 @@ Completed 2026-09-21.
 
 ```task
 id: RMASTER-WP-0027-T03
-status: wait
+status: done
 priority: medium
 state_hub_task_id: "3216fb63-5265-58cb-9ce5-ea7401bbb597"
 ```
@@ -103,3 +103,13 @@ casing already matches §3.
 
 **Done when:** the ruling has landed and this repository's declaration and ADR
 reflect it.
+
+Completed 2026-09-21. `gate-house` ruled in `GH-DEC-2026-017`: the vocabulary
+is closed at four tokens and `Taxonomy` is one of them, so the value stands
+(first branch, in substance — "closed", but at four, not three). The same
+ruling settled questions 1, 2 and 6: `INTENT.md` governs and `layer.yaml` is
+now marked `derived: true`, `derived_from: INTENT.md`; comparison folds case,
+so nothing is re-spelled; `standard_version` is removed from both files.
+`ADR-0010` amended by revision to accepted-2. No checker in this repository
+reads the declaration, so none changed. The repository is outside §4 and
+declares voluntarily; it was not non-conformant.