Apply GH-DEC-2026-020: the checker states its version and scope, and reads content
scripts/check_layer_conformance.py now prints, on every run (success and failure), the standard text it checks against (VALIDATED_AGAINST: security-layer-model_v0.8.md @ net-kingdom f9e1611 with gate-house A9, A11, A12 r2 @ 104f3fc) and its scope. A12 detection widens from the key name standard_version to any *_version key (companion_version included), a versioned standard/companion path, or a bare vN.N token in any key or value of INTENT.md frontmatter or layer.yaml. schema_version and comments are not reached; pep-stance.yaml and pip-claims.yaml are not read for A12 and keep their version fields (GH-DEC-2026-020 §3). The widened check found one value the key-name check could not: the state-hub-work-records note in layer.yaml cited "the v0.7 scope rule". It is reworded to "the standard's scope rule"; no layer or role value changes. Tests fail if a versioned standard: path, a companion_version or a bare version token returns, and if a run stops stating its version and scope. 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
00e203c447
commit
8322f0587e
3 changed files with 155 additions and 12 deletions
|
|
@ -85,5 +85,5 @@ non_tooling_clients:
|
|||
operation: "HTTP to the Custodian State Hub for work records"
|
||||
write: true
|
||||
note: >-
|
||||
Outside §5 by the v0.7 scope rule. Recorded, not policed. Carries no
|
||||
Outside §5 by the standard's scope rule. Recorded, not policed. Carries no
|
||||
tenant-fact authority and no secret payload.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue