From 347e47ce8e11d33c3840fd1ca2248c63c036956d 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 0f0919e..adb4c81 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 Staff — interactive, non-deterministic; operational stewardship.** Add the layer label and the Staff invariant. Two substantive changes. (1) The **"NetKingdom Security Literacy"** section is evidence that the security curriculum had no owner; it now has one. Doctrine and curriculum move to gate-house, and this section becomes lane-specific runbooks that reference gate-house doctrine rather than restating it. The boundary is **doctrine versus runbook**. (2) The literacy and routing tables should add gate-house — currently every plane is listed and gate-house appears nowhere — routing doctrine and authority-model questions there, while continuing to route policy decisions to access-engine. Record the lane/rule demarcation as in ops-mason. +> +> *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 From 15730bb65004554f8ae889d7f46fe1124235914a Mon Sep 17 00:00:00 2001 From: tegwick Date: Fri, 28 Aug 2026 21:21:08 +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 adb4c81..caa3c68 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 467635e84b99757336ee49d7f0dbf107607d0560 Mon Sep 17 00:00:00 2001 From: repo-manager Date: Fri, 28 Aug 2026 21:30:28 +0200 Subject: [PATCH 3/3] repo.work.create_intake WARDEN-IN-0001 correlation_id: 65d40cdd-5894-440e-9c95-c6bcfe259b66 reason: Request assent for GH-DEC-2026-001 boundaries source: repo-manager Assistant: claude-code Assistant-Model: opus Assistant-Process: 2564823@bnt-lap001 Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9 --- intakes/intakes.md | 35 +++++++++++++++++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 intakes/intakes.md diff --git a/intakes/intakes.md b/intakes/intakes.md new file mode 100644 index 0000000..a7f4472 --- /dev/null +++ b/intakes/intakes.md @@ -0,0 +1,35 @@ +# Intake records + +## WARDEN-IN-0001 — Assent requested: Staff layer, doctrine vs runbook, and the access lane/rule demarcation + +```yaml +id: WARDEN-IN-0001 +kind: intake +title: 'Assent requested: Staff layer, doctrine vs runbook, and the access lane/rule + demarcation' +status: open +origin: cross-repo +origin_ref: gate-house GH-DEC-2026-001 +priority: medium +owner: ops-warden +requested_by: gate-house +standard: net-kingdom/canon/standards/security-layer-model_v0.1.md +description: 'gate-house asks ops-warden to assent to three boundary items. (1) ops-warden + is Staff, bound by the rule that Staff acts only through Engine APIs and never touches + Tooling directly (standard section 5). (2) Doctrine versus runbook: the NetKingdom + Security Literacy section in ops-warden INTENT is evidence the security curriculum + had no owner; it now has one in gate-house. Proposal is that doctrine and curriculum + move to gate-house and that section becomes lane-specific runbooks referencing gate-house + doctrine rather than restating it. ops-warden keeps the lanes it stewards and everything + operational about them. (3) The access lane/rule demarcation, normative in standard + section 8: ops-warden and ops-mason own access lanes — how a worker reaches a host; + access-engine owns access rules — whether they may. This demarcation is the condition + attached to renaming flex-auth to access-engine, so ops-warden effectively holds + a veto on that name. Also requested: add gate-house to the Security Literacy and + routing tables — currently every plane is listed and gate-house appears nowhere + — routing doctrine and authority-model questions there while continuing to route + policy decisions to access-engine. If moving the curriculum out leaves ops-warden + unable to instruct its own workers, say so; the boundary is wrong if it does.' +created: '2026-08-28T19:30:28.087109Z' +updated: '2026-08-28T19:30:28.087109Z' +```