Review the stance register's second row; record why T04 cannot proceed

TWO FINDINGS, BOTH FROM READING OTHER REPOSITORIES RATHER THAN OURS.

The §13.1 stance register has a second row. secrets-engine published
pep-stance.yaml -- total over catalog stage plus unknown, runtime-read
and pinned to SHIPPED_STANCE by test. SCOPE.md claimed ops-warden's was
the estate's only published map and that the register's single row was
itself the finding; that is no longer true and is corrected.

docs/stance-register-review.md is the first exercise of the
aggregate-divergence capability flex-auth claimed on 2026-08-29 and then
recorded as unexercised because one row cannot diverge from anything.
Three findings:

The two maps take opposite stances on unknown -- ops-warden fail_open by
versioned build profile under ADR-0009, secrets-engine fail_closed. Both
conformant, neither a defect, and they disagree about the one case nobody
planned for. Reported as an observation for gate-house's register, not as
a request that either repository change: a PDP does not set a consumer's
stance, and §9.3's two-owner split is our own finding.

The rows are not comparable. ops-warden scopes by security-zone,
secrets-engine by catalog-stage. §6.4 permits both, but the register
cannot then answer what the estate's stance is for a z2 workload. Worth
recording before a third row arrives.

secrets-engine's map defines fail_closed in terms of a durable
ActionAuthorization record, which GH-DEC-2026-005 shelved. The stance is
unaffected -- only the artifact name is stale -- but the file is read at
runtime and pinned by test, so the stale name outlives a comment.

SEPARATELY, T04 IS BLOCKED AND THE REASON IS STRUCTURAL. The task assumed
the ops-warden/tenant-engine/user-engine pattern, where the pin's
default-deny NetworkPolicy admits one approved consumer workload.
secrets-engine has no Kubernetes deployment at all -- it is a CLI. There
is no pod selector to write, and inventing one would repeat the error
corrected in T02. Three possible shapes recorded in the workplan and
raised with them; callerAuth, not the NetworkPolicy, becomes the real
boundary if an operator CLI is the caller, so the FLEX-WP-0016 precedent
does not transfer unexamined.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JTbVXpEiXA7mNJVpDnEPcB

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 412054@bnt-lap001
Assistant-Session: 3968fae1-8d59-4209-9bd6-c22594b8ab19

SCOPE.md

@@ -135,8 +135,15 @@ call itself. `ADR-0009` retires `policy.enabled` and the global `policy.fail_clo
 outright and replaces them with a total per-zone stance map in the consumer PEP
 (`ops-warden/pep-stance.yaml`): open for `z0`-`z2` and `unknown`, closed for
 `z3-critical`. That map is the reference shape for `security-layer-model_v0.7`
-§6.4 obligation 3, and it is the estate's only published one — §13.1's register
-has one row, which the standard records as itself the finding.
+§6.4 obligation 3. It is no longer the only published one: `secrets-engine`
+published `pep-stance.yaml` (total over catalog stage plus `unknown`, runtime-read
+and test-pinned), so §13.1's register now has **two rows** rather than the one the
+standard recorded as itself the finding. flex-auth reviewed the pair in
+`docs/stance-register-review.md` — the first exercise of the aggregate-divergence
+capability it claimed on 2026-08-29 — and found that the two maps take opposite
+stances on `unknown` (`fail_open` vs `fail_closed`) and scope on different axes
+(security-zone vs catalog-stage), which makes the rows conformant but not
+comparable.
 
 flex-auth reviewed the zone model as the PDP on 2026-08-19 and holds one
 boundary: zone **membership** compiles into