coulomb/railiance-master
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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

Browse source 
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
This commit is contained in:
codex 2026-08-29 12:52:35 +02:00
parent 2ec0b93333
commit a0c35b7438
13 changed files with 373 additions and 43 deletions
Download patch file Download diff file Expand all files Collapse all files

11
INTENT.md
View file

@ -92,9 +92,10 @@ and operated as a managed service, it is a workload like any other and is
packaged, executed, and bound through `rapp-*`, `rail-*`, and `reef-*`.
NetKingdom Security Layer Model v0.7 §20 restates these definitions; it does
not author them. Changes to that boundary require this repository's assent
for the axis definitions and `glas-harness`'s assent for the session and
tool-policy seam.
not author them. This repository's assent is
[`docs/adr/ADR-0009-netkingdom-security-layer-interaction.md`](docs/adr/ADR-0009-netkingdom-security-layer-interaction.md).
Changes to that boundary require this repository's assent for the axis
definitions and `glas-harness`'s assent for the session and tool-policy seam.
---
@ -174,6 +175,10 @@ the other side's assent. They are not implied by this file.
Admission (whether a binding may run in production) and exposure (who may
reach a listener) remain Railiance axes. They are not authorization decisions.
The consumption contract is
[`docs/netkingdom-security-consumption-contract.md`](docs/netkingdom-security-consumption-contract.md).
The five unsettled axis-to-layer questions are tracked, not answered, in
[`docs/netkingdom-axis-layer-open-questions.md`](docs/netkingdom-axis-layer-open-questions.md).
---