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

16
INTENT.md
View file

@ -2,10 +2,18 @@
# NetKingdom security layer declaration (statute §11, companion §2).
# Machine-readable form; the prose below is the same claim in our own voice.
# Full contact map and gap records: layer.yaml
# THE layer declaration (§11, GH-DEC-2026-017 §1). `layer.yaml` is derived from
# this frontmatter and must agree with it; it does not govern. Comparison of the
# §3 vocabulary is ASCII case-insensitive, so `Staff` here and `staff` there are
# the same value and neither is re-spelled (GH-DEC-2026-017 §2).
layer: Staff
role: null # Engines only
standard: net-kingdom/canon/standards/security-layer-model_v0.7.md
standard_version: "0.7"
# No `standard_version` here or in the sidecar (GH-DEC-2026-017 §5 / A12): the
# declared layer is a standing property. The version the conformance check was
# built and validated against is recorded by the checker itself
# (VALIDATED_AGAINST in scripts/check_layer_conformance.py); assent versions
# live with each assent in decisions/decisions.md.
standard: net-kingdom/canon/standards/security-layer-model
declared_by: decisions/decisions.md#KG-DEC-2026-001
declared_at: "2026-08-29"
conformance_state: blocked-clean
@ -20,7 +28,9 @@ principal_kinds: [human, agent]
> ratified by `gate-house/decisions/decisions.md` GH-DEC-2026-001; assented here
> by `decisions/decisions.md` KG-DEC-2026-001 on 2026-08-28, against v0.1.)*
>
> **The declaration is the frontmatter above plus `layer.yaml`**, checked by
> **The declaration is the frontmatter above.** `layer.yaml` is its derived
> machine-readable form (contact map and gap records), marked derived and required
> to agree with it (`GH-DEC-2026-017` §1); both are checked by
> `scripts/check_layer_conformance.py` and tested in
> `tests/test_layer_conformance.py`. Prose cannot distinguish a declaration from
> a transcribed review, so those are authoritative and this note is commentary