From 69802056cd5c94a9cb18747ef888524cfe6219fb Mon Sep 17 00:00:00 2001 From: codex Date: Mon, 21 Sep 2026 11:33:17 +0200 Subject: [PATCH] Correct the VALIDATED_AGAINST count: six on v0.7, not five. Co-Authored-By: Claude Opus 5 --- docs/assessments/2026-09-21-layer-declaration-boundaries.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/assessments/2026-09-21-layer-declaration-boundaries.md b/docs/assessments/2026-09-21-layer-declaration-boundaries.md index c222ec3..a83afbf 100644 --- a/docs/assessments/2026-09-21-layer-declaration-boundaries.md +++ b/docs/assessments/2026-09-21-layer-declaration-boundaries.md @@ -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.