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

5
docs/adr/ADR-0008-private-by-default-exposure.md
View file

@ -4,7 +4,7 @@ title: "Private-by-default Exposure"
status: accepted
revision: "accepted-1"
owner: railiance-master
last_reviewed: "2026-08-15"
last_reviewed: "2026-08-29"
review_interval: 6m
---
@ -89,6 +89,9 @@ The detailed per-family reading lives in
- ADR-0006 still answers "may this binding run in production?" This ADR
answers "who may reach the listener?" Do not merge the axes.
- Neither question is an authorization decision. Whether an actor may
perform an action is `access-engine` ([`ADR-0009`](ADR-0009-netkingdom-security-layer-interaction.md)).
`exposure: public` MUST NOT be read as permission to act.
- The three readiness enums stay distinct on purpose.
- Family schemas grow an additive `exposure` field. Rapp
`data_classification: public` is a different field and must not be