Declare net-kingdom's own layer and record positions on the v0.8 hold and §11 amendments.
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s

INTENT.md frontmatter carries layer: Taxonomy (no version), stated in
net-kingdom's own voice per GH-DEC-2026-017/020, closing net-kingdom's part
of GH-DEC-2026-019 condition 3. A9, A10, A11, A13 approved; A12 r2 assent
deferred to the operator. No canon text edited; v0.8 not flipped.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
This commit is contained in:
tegwick 2026-09-21 12:36:10 +02:00
parent 033b77f6ee
commit 0b10b4b589
2 changed files with 49 additions and 0 deletions

View file

@ -1,3 +1,7 @@
---
layer: Taxonomy
---
# INTENT
> **NetKingdom layering review — 2026-08-28.** This repository's role was reviewed
@ -15,6 +19,22 @@
>
> *This note records what should change. The body below is not yet adapted.*
> **Layer declaration — 2026-09-21, in net-kingdom's own voice.** net-kingdom declares
> its layer as **Taxonomy** (`layer:` in the frontmatter above; this `INTENT.md` governs,
> per GH-DEC-2026-017, and no derived declaration file exists). The declaration carries
> no standard version by design. It is stated here by net-kingdom itself; the standard's
> §3.1 and §4 rows naming net-kingdom as Taxonomy were statements *about* this repository
> and, per §11, were not a declaration. Our reading agrees with them: this repository's
> product is the canon of record — standards, contracts, schemas and their publication.
>
> **Boundary observation, not a second layer.** The repository also carries runtime and
> operational material — `identity-provisioner/` (a containerised service), `sso-mfa/k8s/`,
> `local-identity/`, and bootstrap/conformance validators under `tools/`. Validators and
> reference profiles that check canon sit with Taxonomy; the deployable identity-provisioner
> and sso-mfa manifests are Tooling/Engine-shaped residue from the bootstrap era. They do
> not change the declared layer, and are recorded here so the next boundary review does not
> have to rediscover them. Relocating them is a separate, owner-planned question.
> This file captures **why this repository exists**,
> the **direction it is moving toward**, and
> the **kind of system it is meant to become**.