From 70b7244442e2aeed6240fb5a318ddbb26113314b Mon Sep 17 00:00:00 2001 From: tegwick Date: Fri, 28 Aug 2026 20:33:43 +0200 Subject: [PATCH 1/3] Note NetKingdom layering review in INTENT Records this repository's layer in the NetKingdom IT-security layer model (Taxonomy / Tooling / Engines / Staff) and what should change in this INTENT as a result. Links to the review that established the model: gate-house/history/2026-08-28-security-layer-model-and-gate-house-recut.md The note flags pending adaptation only; the body is unchanged. Co-Authored-By: Claude Opus 5 Assistant: claude-code Assistant-Model: opus Assistant-Process: 2564823@bnt-lap001 Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9 --- INTENT.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/INTENT.md b/INTENT.md index 97f93ea..18f9784 100644 --- a/INTENT.md +++ b/INTENT.md @@ -1,5 +1,20 @@ # INTENT +> **NetKingdom layering review — 2026-08-28.** This repository's role was reviewed +> against the NetKingdom IT-security layer model: **Taxonomy → Tooling → Engines → +> Staff**, layered by determinism and by the kind of artifact each layer produces. +> Findings and the argument behind them: +> `gate-house/history/2026-08-28-security-layer-model-and-gate-house-recut.md`. +> The model as currently stated is `gate-house/INTENT.md` § "Where Gate House Sits"; +> it is ruled to become a `net-kingdom/canon/standards/` standard, not yet written. +> +> The layer rule that binds every repository: **Staff never touches tooling +> directly. It acts only through engine APIs.** +> +> **This repository is Engine — deterministic API for a modeled concept.** Add the layer label. The existing boundary contract (`net-kingdom/canon/standards/user-engine-boundary-contract_v0.1.md`) holds unchanged. Worth making explicit that user-engine supplies subject context as input to the authorization decision and never renders one. +> +> *This note records what should change. The body below is not yet adapted.* + > This file captures why this repository exists, the direction it is moving > toward, and the kind of system it is meant to become. It is intentionally > aspirational and stable, not a description of current implementation. From 7ea90b8fda6daaaaca6e2a7a2737c6719bba2963 Mon Sep 17 00:00:00 2001 From: tegwick Date: Fri, 28 Aug 2026 21:21:07 +0200 Subject: [PATCH 2/3] Point layering note at the published standard The layer model is now published as net-kingdom/canon/standards/security-layer-model_v0.1.md (proposed) and ratified by gate-house GH-DEC-2026-001. The note previously said the standard was not yet written. Co-Authored-By: Claude Opus 5 Assistant: claude-code Assistant-Model: opus Assistant-Process: 2564823@bnt-lap001 Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9 --- INTENT.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/INTENT.md b/INTENT.md index 18f9784..b3d4165 100644 --- a/INTENT.md +++ b/INTENT.md @@ -5,8 +5,8 @@ > Staff**, layered by determinism and by the kind of artifact each layer produces. > Findings and the argument behind them: > `gate-house/history/2026-08-28-security-layer-model-and-gate-house-recut.md`. -> The model as currently stated is `gate-house/INTENT.md` § "Where Gate House Sits"; -> it is ruled to become a `net-kingdom/canon/standards/` standard, not yet written. +> The model is `net-kingdom/canon/standards/security-layer-model_v0.1.md` (proposed), +> ratified by `gate-house/decisions/decisions.md` GH-DEC-2026-001. > > The layer rule that binds every repository: **Staff never touches tooling > directly. It acts only through engine APIs.** From c5b55036d3e0ece73ffdb70e0431fa45ee437b04 Mon Sep 17 00:00:00 2001 From: repo-manager Date: Fri, 28 Aug 2026 23:02:12 +0200 Subject: [PATCH 3/3] repo.work.create_intake USER-IN-0001 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit correlation_id: 6fa20b48-a3c2-4a5e-807b-80660896608e reason: Request own-voice layer declaration under §11 source: repo-manager Assistant: claude-code Assistant-Model: opus Assistant-Process: 2564823@bnt-lap001 Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9 --- intakes/intakes.md | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 intakes/intakes.md diff --git a/intakes/intakes.md b/intakes/intakes.md new file mode 100644 index 0000000..47a3db3 --- /dev/null +++ b/intakes/intakes.md @@ -0,0 +1,36 @@ +# Intake records + +## USER-IN-0001 — Declaration requested: state this repository's layer in INTENT.md (security layer model §11) + +```yaml +id: USER-IN-0001 +kind: intake +title: 'Declaration requested: state this repository''s layer in INTENT.md (security + layer model §11)' +status: open +origin: cross-repo +origin_ref: net-kingdom security-layer-model_v0.4 §11 +priority: low +owner: user-engine +requested_by: gate-house +proposed_layer: Engine +description: 'A conformance sweep on 2026-08-28 found this repository has no layer + declaration of its own. It carries a layering review note gate-house wrote into + the top of its INTENT.md on 2026-08-24, and that note names a layer — but the words + are gate-house''s, sitting above a line admitting the body is unadapted. Section + 11 has since been amended to say so explicitly: a layer stated about a repository + by another repository is not a declaration; only the repository''s own file, in + its own voice, conforms. Seven of fifteen estate-authored repositories have declared; + this is one of the eight that have not, and the standard does not claim adoption + on the basis of notes gate-house wrote. REQUESTED: state the layer in INTENT.md + in your own voice, or contest it. PROPOSED LAYER: Engine. Users, accounts, memberships. + Your boundary contract (net-kingdom/canon/standards/user-engine-boundary-contract_v0.1.md) + holds unchanged; the only addition is making explicit that subject context is an + input to the authorization decision and never a decision. Contesting is a real option + and costs nothing — the three repositories that reviewed this model each returned + a correction, two of which changed the standard. If the proposed layer is wrong + for what this repository actually does, that is more useful to us than a label added + to close a checkbox. Standard: net-kingdom/canon/standards/security-layer-model_v0.4.md.' +created: '2026-08-28T21:02:12.760565Z' +updated: '2026-08-28T21:02:12.760565Z' +```