Apply GH-DEC-2026-017: INTENT.md governs, layer.yaml is derived, no version
Remove standard_version from layer.yaml and the INTENT.md frontmatter (A12), mark layer.yaml derived: true / derived_from: INTENT.md (A11), and change the conformance checker and its tests in the same commit so the conforming declaration does not fail as malformed. The checker now requires the INTENT.md layer: key, rejects standard_version in either form, checks the layer against the closed four-token vocabulary (A9), and reports a layer/role disagreement between the two forms after an ASCII case-fold. Nothing is re-spelled: INTENT.md keeps Engine/PIP and layer.yaml keeps engine/pip. pep-stance.yaml and pip-claims.yaml keep their standard_version; neither is a layer declaration. 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:
parent
d132db064f
commit
d846eba65c
4 changed files with 103 additions and 15 deletions
|
|
@ -4,7 +4,6 @@ updated: "2026-08-29"
|
|||
layer: Engine
|
||||
role: PIP
|
||||
standard: netkingdom-security-layer-model
|
||||
standard_version: "0.7"
|
||||
companion: net-kingdom/SECURITY-COMPANION.md
|
||||
---
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue