Apply GH-DEC-2026-017: INTENT.md governs, the sidecar is derived, no version

Verified against gate-house's own committed files before editing, not the inbox
message: GH-DEC-2026-017 in decisions/decisions.md at gate-house@def0af2,
amendments A9-A13 in docs/amendments/v0.8-section-11-declaration-amendments.md,
and sections 3, 4 and 11 of net-kingdom's security-layer-model_v0.8.md. The
ruling and docs/layer-declaration-precedence.md's secondary account agreed.

INTENT.md's frontmatter is the declaration; layer.yaml is a derived artifact,
now marked derived: true / derived_from: INTENT.md, and it does not govern.

standard_version is removed from BOTH forms. The ruling's general form is that a
layer declaration must not carry a standard version, and INTENT.md is the
declaration, so removing it from the sidecar alone would have left the field in
the only file that actually declares. INTENT.md's version-pinned `standard:`
path is de-versioned for the same reason: a pinned path reads as a validity
condition. The version ops-warden assented at stays with the assent, ADR-0010.

NO LAYER VALUE IS CHANGED. INTENT.md still says Staff and layer.yaml still says
staff. Section 3's vocabulary is closed, four tokens, and case-insensitive: the
two forms were never in disagreement about a layer, and the ruling asked nobody
to re-spell anything. The comment marking the divergence is rewritten from
"unruled, do not touch" to "ruled, folding case is the checker's job".

check_layer_conformance.py would have rejected the conforming declaration this
ruling produces -- it listed standard_version as a required key. It now reads
INTENT.md as the governing form, ASCII-folds before comparing, validates both
values against the closed four-token vocabulary (Taxonomy included; omitting it
is the defect A9 records against the estate's other validator), requires the
derived marking, rejects a returning standard_version in either file, and
reports a post-fold disagreement between the forms as a finding rather than
resolving it away by precedence.

The test asserts the fold, not equality. An equality assertion here would be
this repository quietly performing the re-spelling the ruling declined to order;
the fold still fails on a real layer divergence.

pep-stance.yaml is untouched. A stance map is not a layer declaration, and the
sidecar schema beyond the derived marking and the version is explicitly not
ruled.

layer.yaml is the form seven repositories copied, so the adopter change set is
written out in wiki/playbooks/netkingdom-layer-declaration.md -- including the
trap that an adopter which also copied the checker turns a conforming
declaration into MALFORMED exit 2 by removing the field alone. No other
repository is edited here.

Still open: where the removed version lives. A12 says the derived conformance
record "already MUST" carry it; ops-warden has a re-runnable checker that emits
nothing durable. Asked of gate-house in message 4220413a, unanswered, and left
open rather than answered by choosing. Nothing above depends on it.

Carries WARDEN-WP-0034-T06 to done.

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

INTENT.md

@@ -1,11 +1,20 @@
 ---
+# 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: PDP | PIP | Evidence | Lifecycle
 pep_shaped: true              # §6.4 — issuing a certificate is a protected side effect
-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 that does not change when the
+# standard is revised, so a version in the declaration reads as a validity
+# condition it is not. Version-scoped state belongs in the derived conformance
+# record. The version ops-warden assented at is recorded with the assent
+# (ADR-0010), which is where a version-at-a-boundary belongs.
+standard: net-kingdom/canon/standards/security-layer-model
 companion: net-kingdom/SECURITY-COMPANION.md
-declaration: layer.yaml
+declaration: layer.yaml       # derived form; this frontmatter governs
 pep_stance: pep-stance.yaml
 assent: docs/adr/ADR-0010
 ---