coulomb/kings-guard
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Assent to Staff placement; release control-plane vocabulary (KG-IN-0001)

Browse source 
Answers gate-house intake KG-IN-0001 / GH-DEC-2026-001 against the
NetKingdom Security Layer Model v0.1.

Assent to all three points, recorded as KG-DEC-2026-001:
- kings-guard declares layer Staff in INTENT.md;
- "control plane" released to the Engine layer across INTENT, SCOPE,
  README, AGENTS and the adjacent-system boundary;
- the posture asymmetry adopted as a repo invariant — already satisfied,
  every EffectorRequest carries an explicit authority_boundary.

Boundary corrections: key-cape and OpenBao are Tooling, so their evidence
is routed through user-engine/access-engine and secrets-engine rather
than read directly.

Finding on the invited challenge to §5: do not weaken the binding rule,
but §4 catalogs kings-guard as owning containment while no engine exposes
a containment surface — the charter is currently undischargeable. Two
rulings requested of gate-house. Three engine gaps declared in INTENT.md.

Residual handed off as KG-IN-0002 (vocabulary sweep of the architecture
spec).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UEtvmYUBP2fDtirJGWn5MW

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 4014379@bnt-lap001
Assistant-Session: 4af9e20f-1768-4afc-951b-b507784e382b
This commit is contained in:
tegwick 2026-08-28 21:47:05 +02:00
parent f78bca1586
commit 3d6025ae51
9 changed files with 457 additions and 31 deletions
Download patch file Download diff file Expand all files Collapse all files

38
intakes/intakes.md
View file

@ -7,7 +7,9 @@ id: KG-IN-0001
kind: intake
title: 'Assent requested: Staff layer placement, control-plane vocabulary, and the
posture asymmetry'
status: open
status: closed
outcome: absorbed
promoted_to: KG-DEC-2026-001
origin: cross-repo
origin_ref: gate-house GH-DEC-2026-001
priority: medium
@ -30,4 +32,38 @@ description: 'gate-house asks kings-guard to assent to its placement in the NetK
that should change the doctrine rather than be worked around.'
created: '2026-08-28T19:30:17.201213Z'
updated: '2026-08-28T19:30:17.201213Z'
closed: '2026-08-28'
resolution: 'Assent with finding. All three points assented and adopted in
INTENT.md, SCOPE.md, README.md, AGENTS.md, and docs/AdjacentSystemBoundary.md.
The invited challenge to the binding rule was taken up and answered: do not
weaken section 5 — but section 4 catalogs kings-guard as owning containment
while no engine exposes a containment surface, so the charter is currently
undischargeable. Two rulings requested of gate-house. Full record:
decisions/decisions.md KG-DEC-2026-001. Vocabulary sweep of the architecture
spec handed off as KG-IN-0002.'
```
## KG-IN-0002 — Sweep "control plane" and layer vocabulary through NetKingdomImmuneArchitecture.md
```yaml
id: KG-IN-0002
kind: intake
title: Sweep "control plane" and layer vocabulary through NetKingdomImmuneArchitecture.md
status: open
origin: residual
origin_ref: KG-DEC-2026-001
priority: low
owner: kings-guard
standard: net-kingdom/canon/standards/security-layer-model_v0.1.md
description: 'specs/NetKingdomImmuneArchitecture.md (approx. 1900 lines) predates the
NetKingdom Security Layer Model and uses "control plane" in several places —
including a "Platform Immune Control Plane" subgraph — where the layer model
reserves that vocabulary for the Engine layer. A scoping note now sits at the head
of the document so no reading takes it as a kings-guard self-description, but the
body is not adapted. Sweep it: separate the components that are engine-layer
authorities from the observation-and-judgment surface kings-guard actually owns,
and check that no part of the architecture places a decision point in Staff
(layer model section 6).'
created: '2026-08-28'
updated: '2026-08-28'
```