feat(RMASTER-WP-0026): declare Taxonomy layer and consume NetKingdom §20

Add layer.yaml, RMASTER-ADR-0009, the consumption contract, and a tracked
non-answer for the five §20.3 questions. Split admission, exposure, and
authorization without renaming schema fields. Finish the workplan.

Assistant: grok
Assistant-Session: 01a04c9f-cd6b-7741-bce0-f1d9d1b3c3bc

SCOPE.md

@@ -23,16 +23,17 @@ running deployable under rapp coverage (`ADR-0007`); human acts, credentials,
 broker actions, and non-deployable infrastructure resources remain outside
 that meaning.
 
-This repository now **declares** itself Taxonomy of Railiance workload
-operations in `INTENT.md` frontmatter (`layer: Taxonomy`, NetKingdom
-security-layer-model v0.7). It is not a row in the NetKingdom §4 catalog.
-The machine-readable `layer.yaml` form, a total non-Tooling-client account,
-and a framework consumption contract for §20.2 are not yet evidenced here.
+This repository **declares** itself Taxonomy of Railiance workload
+operations in `INTENT.md` frontmatter and `layer.yaml` (`layer: Taxonomy`,
+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`.
 
 The current implementation includes:
 
-- eight accepted framework ADRs covering repository families, rail composition,
-  production admission, the rapp declaration contract, and exposure posture;
+- nine 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/`;
 - JSON Schemas for rail, rapp, and reef declarations plus a family-declaration
   validator and fixtures;
@@ -86,7 +87,8 @@ not own every implementation implied by them.
 - PEP stance maps and unreachable-engine behaviour of implementation
   repositories; this repo is not PEP-shaped
 - A guessed mapping of rail, rapp, reef, or ownership onto Taxonomy,
-  Tooling, Engine, or Staff — statute §20.3 is unsettled
+  Tooling, Engine, or Staff — statute §20.3 is tracked unanswered in
+  `docs/netkingdom-axis-layer-open-questions.md`
 - Automatic containment or production observation; both are estate-wide
   zeros, not this repository's gaps to close
 
@@ -107,9 +109,9 @@ not own every implementation implied by them.
 
 The policy publication corpus from this repo is `docs/adr/*.md`. Workplans,
 evidence, runbooks, schemas, and general documentation are not policy merely
-because they are useful. `policy-nexus` currently discovers all eight ADRs, but
-they remain `metadata-pending` until source lifecycle metadata and explicit
-publication addressing are completed.
+because they are useful. `policy-nexus` currently discovers the earlier eight
+ADRs as `metadata-pending`; ADR-0009 is an additional source record awaiting
+the same publication addressing.
 
 ---
 
@@ -146,20 +148,23 @@ publication addressing are completed.
 - Status: maintained and evolving
 - Architecture baseline: four repository axes are materialized and governed by
   accepted ADRs and contracts
-- Layer declaration: `INTENT.md` frontmatter declares `layer: Taxonomy`
-  against security-layer-model v0.7; `layer.yaml` and a conformance check are
-  not yet present
-- Security consumption: ADR-0001 through ADR-0008 do not yet encode the
-  §20.2 rules (one PDP, approvals as claims, credentials after a decision,
-  evidence bound, PEP-shape of implementation runtimes)
-- Admission (ADR-0006) and exposure (ADR-0008) are live Railiance axes and
-  are not yet demarcated in-repo from authorization decisions
+- 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
+- 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
+  bound, PEP-shape of implementation runtimes)
+- Admission (ADR-0006), exposure (ADR-0008), and authorization
+  (`access-engine` via ADR-0009) are demarcated in-repo
+- Axis-to-layer mapping: five statute §20.3 questions are tracked unanswered
+  in `docs/netkingdom-axis-layer-open-questions.md`; next review 2026-11-29
 - Validation: rail/rapp/reef schemas and declaration checks are implemented
 - Active cross-repo work: OpenBao migration closeout remains partially blocked;
   public-listener retraction is in progress while destructive source cleanup
   retains separate approval and disaster-recovery gates
 - Publication: ADR discovery exists in `policy-nexus`; publication metadata and
-  stable addressing remain an open alignment gap
+  stable addressing remain an open alignment gap, now including ADR-0009
 
 ---
 
@@ -208,9 +213,13 @@ Intentional deviations and omissions:
 - Start with: `README.md`, `INTENT.md`, `SCOPE.md`
 - Architecture entry points: `docs/repository-axes.md`,
   `docs/reef-substrate-model.md`, `docs/adr/`
+- NetKingdom interaction: `layer.yaml`,
+  `docs/netkingdom-security-consumption-contract.md`,
+  `docs/netkingdom-axis-layer-open-questions.md`,
+  `docs/adr/ADR-0009-netkingdom-security-layer-interaction.md`
 - NetKingdom alignment review:
   `history/260829-demand-netkingdom-security-layer-alignment.md`
-- Machine-readable contracts: `schemas/`,
+- Machine-readable contracts: `schemas/`, `layer.yaml`,
   `tools/validate-family-declarations.py`
 - Active and historical coordination: `workplans/`, `WORK-RECORDS.md`
 
@@ -243,12 +252,11 @@ keywords: [schema, validation, declaration, rail, rapp, reef]
 
 ## Gap to Intent
 
-The remaining alignment work is to complete downstream ADR publication, cleanly
-archive completed work without breaking State Hub conventions, retain a
-repeatable canon-consumer review packet as the architecture evolves, and close
-the NetKingdom security-layer gap recorded in
-`history/260829-demand-netkingdom-security-layer-alignment.md` and tracked by
-`RMASTER-WP-0026`: a machine-readable layer declaration, a §20.2 consumption
-contract, a vocabulary split between admission/exposure and authorization, and
-assented answers to the five unsettled axis-to-layer questions. Do not invent
-the mapping, host a PDP, or take PEP shape in this repository.
+The remaining alignment work is to complete downstream ADR publication
+(including ADR-0009), cleanly archive completed work without breaking State
+Hub conventions, and retain a repeatable canon-consumer review packet as the
+architecture evolves. The NetKingdom security-layer declaration, §20 assent,
+consumption contract, and admission/exposure/authorization split are now
+evidenced. The five axis-to-layer questions remain tracked unanswered until
+their named reviewers assent; they are not a silent deficit of this
+repository. Do not invent the mapping, host a PDP, or take PEP shape here.