coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Correct the VALIDATED_AGAINST count: six on v0.7, not five.

Browse source 
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
codex 2026-09-21 11:33:17 +02:00
parent 2a13c9ef71
commit 69802056cd
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/assessments/2026-09-21-layer-declaration-boundaries.md
View file

@ -257,6 +257,6 @@ It is applied in eleven repositories. whitehat-security, which never received GH
The round produced the same failure a third time, now in the checkers: each wrote its own version detector, and they disagree. Measured:
- **Prose citations:** eight declarations carry a prose version citation, including gate-house's own. Seven carry the same inherited sentence, "Outside §5 by the v0.5 scope rule". The repositories split four ways on handling it while gate-house's ruling is pending.
- **`VALIDATED_AGAINST`:** five checkers name the v0.7 text in force; tenant-engine and flex-auth name the held v0.8.
- **`VALIDATED_AGAINST`:** six checkers name the v0.7 text in force; tenant-engine and flex-auth name the held v0.8.
ops-warden wrote one reference detector into its playbook (0f9ada0). All of this went to gate-house, with a proposed additional v0.8 flip condition.