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

id	type	title	domain	repo	status	owner	topic_slug	flavor	created	updated	state_hub_workstream_id
RMASTER-WP-0027	workplan	Hold the Taxonomy layer declaration through the gate-house vocabulary ruling	financials	railiance-master	finished	claude	layer-vocabulary-ruling	planning	2026-09-21	2026-09-21	353baba4-02d0-567d-9a0f-0f0419dcd607

RMASTER-WP-0027 - Hold the Taxonomy layer declaration through the gate-house vocabulary ruling

Goal

State and hold this repository's position that layer: Taxonomy is a value §3 of the NetKingdom security layer model enumerates, through gate-house's ruling on whether §3's vocabulary is closed, and act on the ruling once it lands.

Position: docs/adr/ADR-0010-taxonomy-is-an-enumerated-layer.md. Source: the-custodian/docs/assessments/2026-09-21-layer-declaration-boundaries.md (custodian estate sweep), derived from flex-auth FLEX-WP-0030. Statute: net-kingdom/canon/standards/security-layer-model_v0.8.md §3, §3.1, §11.

Boundaries

• Do not change the declared value in INTENT.md or layer.yaml before the ruling. The declaration is the evidence of what this repository holds itself to be.
• Do not rule on §3, §11 or the vocabulary. That is gate-house's.
• Do not speak for informed-decision on surface. Different question, other owner.
• Do not touch standard_version here; B4 is a separate open question.
• Do not modify any repository other than this one.

T01 - Record the position

id: RMASTER-WP-0027-T01
status: done
priority: high
state_hub_task_id: "0acb84f8-7342-596c-90ba-6ea595f66d65"

Establish from this repository's own documents and history what Taxonomy denotes, why it was chosen over Staff, Engine and Tooling, and whether the term is used consistently with gate-house and info-tech-canon. Record the result as a framework ADR.

Done when: an accepted ADR states the position with the canon and estate citations behind it.

Completed 2026-09-21 as ADR-0010. §3 enumerates four layers with Taxonomy as §3.1 in every version v0.1–v0.8; §4 assigns the value to info-tech-canon and net-kingdom; §7 and §17 both carry it; gate-house's own INTENT.md uses it. Our casing matches §3's table.

T02 - Send the position to gate-house

id: RMASTER-WP-0027-T02
status: done
priority: high
state_hub_task_id: "634385f3-67f7-56fa-b8bb-9d00f99f973b"

Send ADR-0010 to gate-house via the State Hub as input to the §3 vocabulary ruling, noting that the custodian's estate sweep is where this surfaced and that it was not a finding against this repository.

Done when: the message is sent and cites the ADR and the canon sections.

Completed 2026-09-21.

T03 - Act on the ruling

id: RMASTER-WP-0027-T03
status: done
priority: medium
state_hub_task_id: "3216fb63-5265-58cb-9ce5-ea7401bbb597"

Wait on gate-house's ruling on question 3 of the custodian's table (is §3's vocabulary closed).

• If the vocabulary is open and Taxonomy is declarable — nothing changes here. Record the confirmation in ADR-0010 notes and close.
• If gate-house rules the §11 declaration vocabulary closed at three despite §3.1 — change the value in INTENT.md and layer.yaml in one commit, keeping the two files equal per RMASTER-WP-0026-T01, and amend ADR-0010 by revision rather than by silent edit.

Also pick up questions 1 (precedence), 2 (case sensitivity) and 6 (may a declaration carry a standard version) if the same ruling settles them; 6 is the only one that changes a file here, since our two files already agree and our 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.