Hold layer: Taxonomy as an enumerated §3.1 value through the gate-house ruling.

The custodian's estate sweep of flex-auth's FLEX-WP-0030 boundaries review
records this repository as declaring a value outside the §3 vocabulary, on
the reading that §3 admits only {Staff, Engine, Tooling}. §3 enumerates four
layers, and Taxonomy is the first row of its table with §3.1 to itself, in
every version of the standard from v0.1 through v0.8. §4 assigns the value to
info-tech-canon and net-kingdom, §7 carries it as a fourth plane line, §17 is
titled for it, and gate-house's own INTENT.md uses it.

ADR-0010 records the position with those citations. The declaration is not
changed: it is the evidence of what this repository holds itself to be, and
changing it now would pre-empt the ruling. RMASTER-WP-0027 holds the wait and
says what to do either way.

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

SCOPE.md

@@ -29,9 +29,15 @@ NetKingdom security-layer-model v0.7). It is not a row in the NetKingdom
 §4 catalog. It is not PEP-shaped. Assent to statute §20 is
 `docs/adr/ADR-0009-netkingdom-security-layer-interaction.md`.
 
+`Taxonomy` is the value §3.1 of the standard enumerates, not a local
+coinage. Where a conformance tool admits only `{Staff, Engine, Tooling}`,
+that tool omits §3.1; the position and its citations are
+`docs/adr/ADR-0010-taxonomy-is-an-enumerated-layer.md`, held through
+`gate-house`'s ruling under `RMASTER-WP-0027`.
+
 The current implementation includes:
 
-- nine accepted framework ADRs covering repository families, rail composition,
+- ten accepted framework ADRs covering repository families, rail composition,
   production admission, the rapp declaration contract, exposure posture, and
   the NetKingdom security-layer interaction boundary;
 - framework contracts and migration guidance under `docs/`;
@@ -150,7 +156,9 @@ the same publication addressing.
   accepted ADRs and contracts
 - Layer declaration: `INTENT.md` frontmatter and `layer.yaml` declare
   `layer: Taxonomy` against security-layer-model v0.7; no Tooling contacts;
-  State Hub listed as a non-Tooling client; not PEP-shaped
+  State Hub listed as a non-Tooling client; not PEP-shaped. The two files
+  agree and match §3's own casing. Held unchanged through `gate-house`'s
+  ruling on whether §3's vocabulary is closed (ADR-0010, RMASTER-WP-0027)
 - Security consumption: ADR-0009 and
   `docs/netkingdom-security-consumption-contract.md` encode the §20.2 rules
   (one PDP, approvals as claims, credentials after a decision, evidence