diff --git a/INTENT.md b/INTENT.md index 08f0c76..6c1b36a 100644 --- a/INTENT.md +++ b/INTENT.md @@ -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**. diff --git a/history/2026-09-21-v08-hold-and-section-11-amendment-positions.md b/history/2026-09-21-v08-hold-and-section-11-amendment-positions.md new file mode 100644 index 0000000..cc82b09 --- /dev/null +++ b/history/2026-09-21-v08-hold-and-section-11-amendment-positions.md @@ -0,0 +1,29 @@ +# v0.8 hold and §11 amendment set — net-kingdom's positions (2026-09-21) + +Recorded by net-kingdom as publication owner of `canon/standards/security-layer-model_v0.8.md`. +Positions only: **no canon file was edited, nothing was applied, v0.8 was not flipped.** + +## The hold (GH-DEC-2026-019) + +Acknowledged. v0.8 stays `proposed`; v0.7 stays accepted and in force. net-kingdom will not +run the acceptance flip until all three closing conditions (GH-DEC-2026-019 §4) are met: + +1. A9–A13 drafted, circulated and dispositioned (GH-WP-0004) — open. +2. `audit-core` returns its §11 review or declines in writing — open. +3. The four undeclared §4 repositories declare or record a dated gap — net-kingdom's part is + **closed today**: `INTENT.md` frontmatter now carries `layer: Taxonomy`. + +The §13 row added after handover (GH-DEC-2026-013, net-kingdom@f9e1611) stays in v0.8. + +## Dispositions on the amendment set (gate-house docs/amendments/v0.8-section-11-declaration-amendments.md v0.2) + +| # | Disposition | Note | +| --- | --- | --- | +| A9 | approved | A closed, case-insensitive token set; `Taxonomy` included. | +| A10 | approved | Source vs custody as an explicit §4 marking; count replaced by §15 reference. | +| A11 | approved | `INTENT.md` governs; disagreement reported, not resolved away; runs state scope. net-kingdom has no derived declaration file. | +| A12 r2 | **deferred to the operator** | No finding against the text. r2 was revised today under GH-DEC-2026-020; net-kingdom defers assent to the operator, as three other repositories did. net-kingdom's own declaration already satisfies r2 (no version in any frontmatter key or value). | +| A13 | approved | Accurate resolvability note; net-kingdom will not revert to `flex-auth`. | + +Approval is of the amendment text as the canon owner. It is applied to the cut only once the +set is dispositioned by every assenting party and the hold's conditions allow it.