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

Verified against gate-house's committed files before editing: GH-DEC-2026-017
in decisions/decisions.md and amendments A9-A13 in
docs/amendments/v0.8-section-11-declaration-amendments.md, then ops-warden's
reference change set (wiki/playbooks/netkingdom-layer-declaration.md and its
applied instance, ops-warden a70f559). Ruling and playbook agree.

layer.yaml: standard_version removed; marked derived: true / derived_from:
INTENT.md; header rewritten to say it does not govern and that a post-fold
disagreement between the forms is a finding. The Framework comment is
de-versioned for the same reason.

INTENT.md: the frontmatter layer: key is the declaration. It carried no
standard_version key, but its standard: path pinned _v0.7.md; de-versioned as
the reference instance did, since a pinned path reads as a validity condition.
Prose citing v0.7 as the accepted statute is left as is.

NO LAYER VALUE IS CHANGED. INTENT.md says Engine, layer.yaml says engine; the
section 3 vocabulary is closed and compared after an ASCII fold, so they agree.

No conformance checker exists in this repository, and no test reads
standard_version, so nothing else had to change with the field. Test suite:
156 passed. companion_version and schema_version are left untouched; the
ruling does not cover them.

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,7 +1,11 @@
 ---
+# THE layer declaration (§11, GH-DEC-2026-017 §1). layer.yaml is derived from
+# this frontmatter and must agree with it after an ASCII case fold; it does not
+# govern. No standard version here (GH-DEC-2026-017 §5 / A12): the declared
+# layer is a standing property, so the standard is named without a version pin.
 layer: Engine
 role: PIP
-standard: net-kingdom/canon/standards/security-layer-model_v0.7.md
+standard: net-kingdom/canon/standards/security-layer-model
 companion: net-kingdom/SECURITY-COMPANION.md
 ---
 

layer.yaml

@@ -1,6 +1,17 @@
-# approval-engine — NetKingdom security layer declaration
+# approval-engine — 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, never
+# resolved away by precedence.
+#
+# INTENT.md says `Engine`, this file says `engine`. The §3 vocabulary is closed
+# (Taxonomy, Tooling, Engine, Staff) and compared after an ASCII case fold
+# (GH-DEC-2026-017 §2-§3, A9), so these are the same value. Neither is
+# re-spelled; folding case is the checker's job.
+#
+# Framework: net-kingdom/canon/standards/security-layer-model
 # Companion: net-kingdom/SECURITY-COMPANION.md v0.2
 # Voice:     INTENT.md (this repository's own, per §11 "who must declare")
 #
@@ -10,7 +21,15 @@
 
 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, here or in INTENT.md: GH-DEC-2026-017 §5 / A12 —
+# a layer declaration MUST NOT carry a standard version. The declared layer is
+# a standing property; version-scoped state belongs in the derived conformance
+# record. Do not add it back.
 companion_version: "0.2"
 repository: approval-engine
 layer: engine