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

Apply GH-DEC-2026-017 to the layer declaration; close KG-IN-0007.

Browse source 
INTENT.md frontmatter governs and layer.yaml is marked derived from it.
standard_version is removed from both forms (A12). The checker and its
tests change in the same commit: they no longer require the field, they
reject it, they fold case against the four-token vocabulary (A9) instead
of comparing with plain equality, and they still fail a layer disagreement
that survives the fold (A11). Neither layer value is re-spelled.

The ruling answers kings-guard's "validated-against" reading of the field
(§5: version-scoped state belongs in the derived conformance record), so
that version now lives in the checker as VALIDATED_AGAINST and is printed
in every run's output. The standard: path in INTENT.md is unversioned to
match the reference form.

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 07:35:40 +02:00
parent 6752e5e570
commit 5120adf55a
6 changed files with 259 additions and 31 deletions
Download patch file Download diff file Expand all files Collapse all files

53
layer.yaml
View file

@ -1,6 +1,12 @@
# kings-guard — NetKingdom security layer declaration
# kings-guard — DERIVED form of the NetKingdom security layer declaration
#
# Framework: net-kingdom/canon/standards/security-layer-model_v0.7.md
# THIS FILE DOES NOT GOVERN. The declaration is the `layer:` key in INTENT.md's
# frontmatter; this file is a derived artifact under §11's derived-artifact rule
# and must agree with it (GH-DEC-2026-017 §1, amendment A11). A disagreement
# between the two forms is a finding in its own right and is reported by
# scripts/check_layer_conformance.py, never resolved away by precedence.
#
# Framework: net-kingdom/canon/standards/security-layer-model
# Assent: decisions/decisions.md KG-DEC-2026-001 (kings-guard's own voice, §11)
# Validate: python3 scripts/check_layer_conformance.py
#
@ -13,22 +19,41 @@
# 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.
# RULED, 2026-09-21 — GH-DEC-2026-017, applied here (closes KG-IN-0007):
# * Precedence: INTENT.md governs; this file is derived (§1 / A11). Hence
# `derived: true` and `derived_from: INTENT.md` below.
# * Case: §3's vocabulary is closed at four tokens {Taxonomy, Tooling, Engine,
# Staff} and comparison is ASCII case-insensitive (§2, §3 / A9). `layer:
# staff` below and `layer: Staff` in INTENT.md are THE SAME VALUE and neither
# is re-spelled. Do not "fix" either to match the other; the checker folds.
# * Version: a layer declaration MUST NOT carry a standard version (§5 / A12).
# `standard_version: "0.7"` is removed from this file and from INTENT.md.
#
# History of the unruled state (kept, not rewritten): before the ruling this
# block recorded both questions as OPEN and changed neither file, because
# picking a form would have been kings-guard authoring a ruling gate-house holds.
# It also argued that `standard_version` here meant the version this declaration
# was VALIDATED against, not an assent version, so flex-auth's B4 might not
# reach it. GH-DEC-2026-017 §5 answers that reading rather than leaving room for
# it: version-scoped state — which is what "validated against" is — belongs in
# the derived conformance record, and keeping the field "for information" was
# declined because a field that is present will be branched on. The
# validated-against version therefore now lives in the checker, as
# VALIDATED_AGAINST in scripts/check_layer_conformance.py, and is printed in
# every run's output (`make check-layer`). Assent versions still live with each
# assent in decisions/decisions.md.
# 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
standard_version: "0.7"
# §11 derived-artifact marking (GH-DEC-2026-017 §1 / A11).
derived: true
derived_from: INTENT.md
# NO `standard_version` KEY, AND DO NOT ADD ONE BACK (GH-DEC-2026-017 §5 / A12).
# Absence is enforced by scripts/check_layer_conformance.py.
repository: kings-guard
layer: staff
declared_by: decisions/decisions.md#KG-DEC-2026-001