Apply GH-DEC-2026-017: INTENT.md governs, layer.yaml is derived, no version
Verified against gate-house's committed ruling (decisions/decisions.md, GH-DEC-2026-017) and amendments A9-A13, then ops-warden's reference change set (a70f559, wiki/playbooks/netkingdom-layer-declaration.md). They agree. layer.yaml: standard_version removed; derived: true and derived_from: INTENT.md added; declared_by kept. INTENT.md frontmatter never carried standard_version, but its standard: value was a version-pinned path; it is de-versioned as the reference instance did. No layer value is re-spelled: INTENT.md still says Engine and layer.yaml still says engine. The checker changes in the same commit because it listed standard_version as a required key: removing the field alone would have made a conforming declaration exit 2 MALFORMED. It now reads INTENT.md as the governing form, requires the derived marking, rejects a returning standard_version in either form, checks both layer values against the closed four-token vocabulary (Taxonomy included) after an ASCII fold, and reports a post-fold disagreement between the forms as a finding rather than resolving it by precedence. Tests assert the fold, not per-file spelling, and cover fold agreement, a real disagreement, the closed vocabulary and a returning version. Full suite 430 passed. role:, pep-stance.yaml and schema_version are untouched (not ruled). Still open: where the removed version lives in a derived conformance record; asked of gate-house by ops-warden (4220413a), followed rather than chosen here. Closes the SECRETS-WP-0008 note that waited on 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:
parent
2b4cff04c5
commit
8a48cb05df
5 changed files with 226 additions and 22 deletions
11
INTENT.md
11
INTENT.md
|
|
@ -1,9 +1,16 @@
|
|||
---
|
||||
# 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 `Engine` here and `engine` there
|
||||
# are the same value and neither is re-spelled (GH-DEC-2026-017 §2).
|
||||
layer: Engine
|
||||
role: Lifecycle
|
||||
standard: net-kingdom/canon/standards/security-layer-model_v0.7.md
|
||||
# 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. Version-scoped state belongs in the derived conformance record.
|
||||
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
|
||||
declared_at: "2026-08-29"
|
||||
---
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue