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

Answer gate-house's v0.8 round and record the §11 declaration-form wait.

Browse source 
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
This commit is contained in:
tegwick 2026-09-21 02:10:39 +02:00
parent 31e9963933
commit 0fb7b8df4b
4 changed files with 487 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

13
layer.yaml
View file

@ -12,6 +12,19 @@
# there are NO Tooling contacts. Not a narrow one, not a read-only one. The
# capabilities that would need them sit at zero instead. Under §11 that is
# BLOCKED-CLEAN, which MUST NOT rank below conforming.
#
# OPEN — deliberately not resolved here (KG-IN-0007, commentary F3/F4):
# * `layer: staff` below and `layer: Staff` in INTENT.md are both forms §11
# permits, and §11 does not say which governs when both are present. Two
# conforming conformance runs therefore disagree about this repository.
# Neither file is being changed until gate-house rules precedence AND
# whether the §3 vocabulary is case-sensitive; choosing here would be
# kings-guard authoring a ruling it does not own.
# * `standard_version` below names the version this declaration was VALIDATED
# against, not the version of any assent — assents live in
# decisions/decisions.md, each naming its own version. Whether a declaration
# may carry a version at all is flex-auth's B4, also unruled.
# Assent to §9.5 at v0.8 is KG-DEC-2026-004 and does not move this file.
schema_version: "0.1"
framework: netkingdom-security-layer-model