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
intakes/intakes.md
View file

@ -233,14 +233,13 @@ state_hub_intake_id: "01a0c14f-7db6-7787-aa16-a6bb06d745d2"
id: KG-IN-0007
kind: intake
title: §11 declaration-form precedence and case sensitivity
status: open
status: closed
origin: cross-repo
origin_ref: flex-auth FLEX-WP-0030 boundaries-review B1 (corrected 2026-09-21)
priority: medium
owner: kings-guard
requested_by: flex-auth
standard: net-kingdom/canon/standards/security-layer-model_v0.8.md
blocked_on: gate-house ruling on §11 precedence and §3 case sensitivity
related:
- KG-DEC-2026-004
- KG-DEC-2026-001
@ -261,6 +260,19 @@ description: >
an assent; the field means two things and the statute does not say which. When
the rulings land, align both files and the version field in one commit.
Position and argument: docs/StatuteV08Review.md F3 and F4.
resolution: >
Ruled by gate-house GH-DEC-2026-017 (amendments A9, A11, A12) and applied.
Precedence: INTENT.md governs; layer.yaml is now marked `derived: true`,
`derived_from: INTENT.md`. Case: the §3 vocabulary is closed at four tokens
and compared ASCII case-insensitively, so `Staff` and `staff` are one value
and neither file was re-spelled; the checker and tests now fold instead of
comparing with plain equality, and still fail a disagreement that survives
the fold. Version: removed from both forms. The ruling answers kings-guard's
validated-against reading rather than leaving room for it (§5: version-scoped
state belongs in the derived conformance record; keeping the field for
information was declined), so the validated-against version moved to
VALIDATED_AGAINST in scripts/check_layer_conformance.py and is printed in
every run's output. Field and checker changed in one commit.
created: '2026-09-21'
updated: '2026-09-21'
state_hub_intake_id: "01a0c14f-935d-7e08-9f2a-fffd0dba2473"