Three gate-house messages from 2026-09-05/06 and flex-auth's 2026-09-21
correction had gone unanswered for three weeks.
Assent to §9.5 at v0.8 (KG-DEC-2026-004), scoped to the boundary at
net-kingdom@66eeaba rather than to v0.8 as a whole, so an assent round
held open over §11 does not read as §9.5 unsettled. The criteria-grounding
clause gate-house added is assented and its reversal falsifier was
attacked against the two real candidates this repository holds — an
assertion-form §3.4 check and a readiness row grounded on another
repository's decision. It did not fire.
§12 step four: the normative sentence stands, kings-guard has still
observed nothing in production and KG-WP-0005-T03 waits on the runtime
owner. Its supporting sentence has drifted in our favour and is reported
against ourselves, with narrower wording proposed.
§11 declaration form: INTENT.md says Staff, layer.yaml says staff, and
§11 does not say which governs. Neither file is changed — gate-house holds
precedence and case sensitivity. Recorded as KG-IN-0007 with the position
in layer.yaml rather than left as a silence. KG-IN-0008 declines the
catalog reading that exempts published posture from the new §11
emission-guarantee check.
Commentary: docs/StatuteV08Review.md (KG-COM-0002), marked derived per the
rule v0.8 itself adds.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
gate-house asked kings-guard to check the posture/maturity boundary,
with the concern that a second grading authority would be the same shape
of mistake as a second decision point. Its proposed line was volatile
current state against slow progression.
Answered with a proposed revision, KG-DEC-2026-002, argued in
docs/PostureMaturityBoundary.md (KG-COM-0001).
Volatility is an observation about data, not a definition. It fails at
both edges and, more importantly, describes the two things without
partitioning them — every case left to argument is a route by which a
second grading authority arrives.
The discriminator is already in the statute. §9.5 requires maturity to
return the same level from the same criteria and evidence and calls that
determinism the thing that makes it an Engine; §3.3 makes inference Staff
by construction. So: recompute against the same criteria and evidence —
must get the same answer, it is maturity and belongs in an engine; cannot
promise the same answer, it is posture and belongs in Staff.
It is one rule read from both sides. §9.5 already says a criterion that
cannot be evaluated by rule is not yet a criterion; the mirror is that a
judgment that can be evaluated by rule is not posture but a criterion in
the wrong repository.
kings-guard accepts the constraint this puts on its own side: capability
readiness is not an input to posture, since feeding a deterministic value
into a non-deterministic one would blur the boundary from our door. That
also answers the incident-dependency half of the intake.
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
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
