coulomb/approval-engine
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Apply GH-DEC-2026-020: remove companion_version from layer.yaml

Browse source 
A12 r2 reaches every key and value of the declaration, including the
companion's version. The standard: path in INTENT.md was already
unversioned and is unchanged. tests/test_layer_declaration.py fails if a
version key, a versioned standard path, or companion_version returns to
the INTENT.md frontmatter or layer.yaml; schema_version and comments are
not reached. One prose citation ("the v0.5 scope rule") in a rationale
value is allowlisted by exact text and reported to gate-house as open.

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:
tegwick 2026-09-21 09:37:12 +02:00
parent 39e3380447
commit 71ae259877
2 changed files with 99 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

8
layer.yaml
View file

@ -28,9 +28,11 @@ 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"
# a standing property. Do not add it back.
#
# No `companion_version` either: GH-DEC-2026-020 §2 / A12 r2 — the companion's
# version in a declaration is the same pin. tests/test_layer_declaration.py
# fails if it, or a versioned standard path, comes back.
repository: approval-engine
layer: engine
role: pip # §3.3 engine typing; §4 catalog