coulomb/ops-warden
4
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions

Record GH-DEC-2026-017 without applying it yet
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 3s
Details

Browse source 
The precedence ruling landed mid-session: INTENT.md governs, the sidecar is
derived, section 3 folds case so nobody re-spells anything, and standard_version
comes out of the declaration. Two asks land on ops-warden because layer.yaml is
the form seven repositories copied.

Not applied here. Both asks edit this repository's security-layer declaration --
and the estate's reference shape -- on the strength of an instruction delivered
in an inbox message. The change set, and the condition that it be verified at
gate-house@def0af2 rather than from the message text, are written down so the
mandated session does not have to reconstruct 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
This commit is contained in:
tegwick 2026-09-21 02:26:33 +02:00
parent 284bfd6521
commit c186a4e135
2 changed files with 64 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

16
workplans/WARDEN-WP-0034-layer-model-v07-conformance.md
View file

@ -266,6 +266,22 @@ conformant than it is. Position recorded in
one commit, and a regression test asserts the two declarations agree so the next
divergence is caught rather than surveyed.
**Ruled the same day, and still `wait` — deliberately.** `GH-DEC-2026-017`
(message `3715e247`) landed hours later: `INTENT.md` governs, the sidecar is a
derived artifact that must be marked as such, §3's vocabulary is case-insensitive
so **nobody re-spells anything**, and `standard_version` must come out of the
declaration. Two asks land on ops-warden specifically because `layer.yaml` is the
form seven repositories copied.
This task stays `wait` rather than flipping to `progress`, because applying it
edits this repository's security-layer declaration — and the estate's reference
shape — on the strength of an instruction delivered in an inbox message. The
session that applies it should be mandated to, and should verify the decision at
`gate-house@def0af2` and amendments A9–A13 in the repository rather than from the
message text. The exact change set and its four conditions are written down in
`docs/layer-declaration-precedence.md`; the casing half of the original "done
when" above is moot rather than outstanding, since the ruling folds case.
Raised by flex-auth's corrected B1 (message `719b3e9e`, 2026-09-21), which
withdrew an earlier claim that the estate disagreed *across* repositories. The
withdrawal matters to this task: the original finding would have had ops-warden