From d76f6b76e19501a3c4b68c5b83eec4be1e2b08a0 Mon Sep 17 00:00:00 2001 From: tegwick Date: Mon, 21 Sep 2026 00:15:30 +0200 Subject: [PATCH] Raise the boundaries-review findings with their owners and record T01-T03 done. Eleven messages sent. Every finding is open until its owner answers; T04 stays in progress rather than done, because a finding is not closed by silence. Co-Authored-By: Claude Opus 5 Assistant: claude-code Assistant-Model: opus Assistant-Process: 28468@bnt-lap001 Assistant-Session: c76569b2-6056-4dad-aea4-49cd7a018f5d --- ...EX-WP-0030-boundary-declaration-cleanup.md | 39 +++++++++++++++++-- 1 file changed, 35 insertions(+), 4 deletions(-) diff --git a/workplans/FLEX-WP-0030-boundary-declaration-cleanup.md b/workplans/FLEX-WP-0030-boundary-declaration-cleanup.md index 050ff72..c4ade4e 100644 --- a/workplans/FLEX-WP-0030-boundary-declaration-cleanup.md +++ b/workplans/FLEX-WP-0030-boundary-declaration-cleanup.md @@ -42,7 +42,7 @@ is being mechanically checkable. ```task id: FLEX-WP-0030-T01 -status: todo +status: done priority: high ``` @@ -69,11 +69,19 @@ Owner: `flex-auth`. Gate: `INTENT.md` names no standard version; conformance state is version-stamped somewhere that is maintained; `go test ./internal/layer/...` passes. +2026-09-21: done. `standard_version` removed; `conformance_record` added. The +test that pinned `0.7` was **inverted rather than deleted** — `internal/layer` +now rejects a version pin in the declaration and requires `conformance_record` to +name a file that exists on disk. `StandardVersion` is kept on the struct +deliberately, documented as must-stay-empty, so a reintroduced pin fails loudly +instead of being silently ignored. Version-scoped state is in +`docs/conformance/security-layer-conformance.md`. Full suite green. + ## 2. Update SCOPE.md and assess the gaps ```task id: FLEX-WP-0030-T02 -status: todo +status: done priority: high ``` @@ -96,11 +104,16 @@ is next reviewed. Known candidates: Gate: every gap in `SCOPE.md` has an owner and a route; no gap is described only as a sentence. +2026-09-21: done. Three gaps, each with owner and route. G2 (emission guarantee) +is newly assessed and recorded as a gap rather than as conformance, because the +flattering reading has been asserted by nobody but flex-auth. Register corrected +from two rows to five. All `v0.7` references removed from `SCOPE.md`. + ## 3. Publish the boundaries review ```task id: FLEX-WP-0030-T03 -status: todo +status: done priority: high ``` @@ -118,11 +131,18 @@ Cover at minimum: `gate-house` (doctrine), `key-cape` (identity claims in), Gate: the review states, for each counterpart, whether the boundary is agreed, contested, or unstated — and does not record "unstated" as if it were "agreed". +2026-09-21: published at `docs/conformance/boundaries-review.md`, marked derived +and version-stamped. Twelve counterparts. Seven agreed, one agreed-in-substance +but undeclared (`gate-house`), one asserted from one side only (`key-cape`), one +held unilaterally and unconfirmed (`zone-engine`), two unclear (`tenant-engine` +on `CheckRequest.tenant`, `audit-core` on evidence source), one undeclared twice +over (`ops-mason`). + ## 4. Raise the conflicting and unclear boundaries for resolution ```task id: FLEX-WP-0030-T04 -status: todo +status: progress priority: high ``` @@ -213,6 +233,17 @@ Owner: `gate-house` to note; `flex-auth` to ping when `FLEX-WP-0020` lands. Gate: every finding above is sent to its named owner with what would resolve it. An unanswered finding stays open and is not closed by silence. +2026-09-21: eleven messages sent. `gate-house` (all five findings), `key-cape` +(B2, one-sided identity boundary), `audit-core` (B3, evidence source), +`ops-mason` (B2), `net-kingdom` (B5 plus the vendored-vs-authored question), +`zone-engine` (membership/stance confirmation), `tenant-engine` (the live unclear +boundary, restated with its standing), and B1 as a heads-up to the five affected +engine repos — sent as an estate property, not as a finding against any of them, +since no repository could have discovered it from inside its own checker. + +Task stays `progress`: every finding is open until its owner answers. None is +closed by silence. + ## Out of scope - Bumping flex-auth to declare v0.8. v0.8 is `status: proposed`; T01 removes the