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

2
docs/exposure-posture-contract.md
View file

@ -15,6 +15,8 @@ those fields here except to name the objects the validator checks.
Admission (ADR-0006) answers "may this binding run in production?"
Exposure answers "who may reach the listener?" A
`production-approved` binding is still private until a grant exists.
Neither is an authorization decision. Whether an actor may perform an
action is `access-engine` (ADR-0009).
## Vocabulary