From 807f8db07c59410a5aab4b2a69b159e2b3bcfd02 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 fc7632b..3b84f9b 100644 --- a/INTENT.md +++ b/INTENT.md @@ -5,6 +5,21 @@ updated: "2026-07-23" # 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/tenant-engine-boundary-contract_v0.1.md`) holds unchanged. Same clarification as user-engine: tenancy context is an input to the decision, not a decision. +> +> *This note records what should change. The body below is not yet adapted.* + ## Purpose `tenant-engine` exists to be the single, canonical source of truth for what a From 56f343a0dd04b91cc7ae996befe3da15c92fa29b 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 3b84f9b..99769df 100644 --- a/INTENT.md +++ b/INTENT.md @@ -10,8 +10,8 @@ updated: "2026-07-23" > 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 b4fbcb6890b73964b82ab5505250aaf19fd1b844 Mon Sep 17 00:00:00 2001 From: repo-manager Date: Fri, 28 Aug 2026 23:03:13 +0200 Subject: [PATCH 3/3] repo.work.create_intake TEN-IN-0003 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit correlation_id: 655b8d09-09c9-415d-bdc4-c135b484cd78 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 | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 intakes/intakes.md diff --git a/intakes/intakes.md b/intakes/intakes.md new file mode 100644 index 0000000..aedc67c --- /dev/null +++ b/intakes/intakes.md @@ -0,0 +1,37 @@ +# Intake records + +## TEN-IN-0003 — Declaration requested: state this repository's layer in INTENT.md (security layer model §11) + +```yaml +id: TEN-IN-0003 +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: tenant-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 own file, in its + own voice, conforms. REQUESTED: state the layer in INTENT.md in your own voice, + or contest it. PROPOSED LAYER: Engine — tenant-as-an-entity facts. Your boundary + contract holds unchanged. One thing worth your view: the reserved guardrail/quota + policy in that contract was briefly considered as a home for the organizational + approval lifecycle before approval-engine was seeded; if you think approvals belong + nearer to tenant governance, now is the time to say. Contesting costs nothing — + the three repositories that reviewed this model each returned a correction, two + of which changed the standard. NOTE for your own records, unrelated to the request: + the State Hub holds two open intakes for tenant-engine created 2026-08-25 (audit + evidence externalization; unfiltered event-read interface) with no intakes/intakes.md + in this checkout to back them, which is an ADR-001 file-is-truth inconsistency you + may want to reconcile. Standard: net-kingdom/canon/standards/security-layer-model_v0.4.md.' +created: '2026-08-28T21:03:13.580775Z' +updated: '2026-08-28T21:03:13.580775Z' +```