feat: complete local layer model v0.7 conformance work

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06eaf-3425-7f92-a0c2-bb4aa4faebe4

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

@@ -4,14 +4,14 @@ type: workplan
 title: "Layer model v0.7 conformance — state the deadline, bind the agent boundary, steward the estate's newest rule"
 domain: infotech
 repo: ops-warden
-status: ready
+status: active
 owner: ops-warden
 topic_slug: netkingdom
 planning_priority: P1
 depends_on_workplans:
   - WARDEN-WP-0030
 created: "2026-08-29"
-updated: "2026-08-29"
+updated: "2026-09-05"
 state_hub_workstream_id: "ae3ff76f-883d-5e2f-b6aa-144d61e8fdef"
 ---
 
@@ -36,7 +36,7 @@ completed directly; none of these qualify.
 
 ```task
 id: WARDEN-WP-0034-T01
-status: todo
+status: done
 priority: high
 state_hub_task_id: "8b3bdb9f-d2c2-5b3e-89e2-417bf3e37484"
 ```
@@ -60,9 +60,16 @@ of a revocation channel is stated rather than left to inference.
 **Not in scope:** shortening it. Whether 48h is acceptable is a joint question with
 `railiance-infra` (KRL distribution) and is T05's to raise, not this task's to decide.
 
+Completed 2026-09-04. `pep-stance.yaml` now publishes TTL expiry as the only
+revocation mechanism, explicitly records that no CRL/KRL channel exists, and
+states `adm=48h`, `agt=24h`, and `atm=8h`. The conformance test derives the
+expected map from `ActorType`/`MAX_TTL_HOURS`, so declaration and issuance
+policy cannot drift independently. The layer and stance declarations now name
+the accepted v0.7 standard.
+
 ```task
 id: WARDEN-WP-0034-T02
-status: todo
+status: done
 priority: high
 state_hub_task_id: "3318ee1a-b5d9-5d39-baf7-9c42a8bc7b55"
 ```
@@ -90,9 +97,18 @@ enforced/advisory split is written down.
 identity claim, adjacent to deciding, and `ADR-0002`/§6 both point away from it. Read
 the identity; do not adjudicate it.
 
+Completed 2026-09-04. The advisory CLI guard now prefers the exact issued
+KeyCape subject `service:codex:railiance-platform` from
+`WARDEN_POLICY_SUBJECT`, then falls back to `WARDEN_AGENT_ID`. Tests prove the
+issued subject triggers exit 7 without the legacy marker, the fallback remains,
+and an operator subject does not manufacture an agent identity. ADR-0004
+revision 2 records the enforced/advisory split: Warden reads the marker and
+does not validate a token; OpenBao's `agent-high-risk-boundary` is the real
+enforcement.
+
 ```task
 id: WARDEN-WP-0034-T03
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "a891b32c-b0a7-59f6-a5cd-977be65c09ca"
 ```
@@ -111,9 +127,16 @@ that as the finding with the distribution that shows it, and declare the deferra
 **Done when:** either a declared cadence with its derivation, or a declared deferral
 carrying the data that justifies it.
 
+Completed 2026-09-04 with an explicit measured deferral. The signatures log
+contains three issuances across the 79-day observation window, on only two
+active days: one on 2026-06-17 and two within 40 minutes on 2026-08-22. The
+unified audit carries the latter two events. `pep-stance.yaml` records the
+counts, dates, attributive classification, and reason that this sparse,
+operator-driven burst cannot support a meaningful rate threshold.
+
 ```task
 id: WARDEN-WP-0034-T04
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "94e73daa-f74d-51fd-8639-68896a4066ee"
 ```
@@ -138,9 +161,15 @@ to copy — `layer.yaml`, `pep-stance.yaml`, `check_layer_conformance.py`,
 playbook is reachable from the catalog. **Not** a restatement of the companion — a
 pointer layer, per `ADR-0001`.
 
+Completed 2026-09-04. Catalog entry `netkingdom-layer-declaration` resolves the
+exact query to `wiki/playbooks/netkingdom-layer-declaration.md`. The short
+playbook points at the accepted companion/statute, the four reference artifacts
+and checks, and the gate-house review path while explicitly leaving doctrine
+with gate-house and declaration truth with each repository.
+
 ```task
 id: WARDEN-WP-0034-T05
-status: todo
+status: wait
 priority: low
 state_hub_task_id: "7d1b3c82-9b96-5087-a53a-496212909029"
 ```
@@ -162,8 +191,24 @@ fix them (`ADR-0003`, `ADR-0005`).
 **Done when:** both are routed with reasoning, and the answers recorded either way —
 including a refusal, which is an equally good answer.
 
+Raised 2026-09-04 and waiting for answers. Ops-mason received the stance-map
+reference and classification question (message `6ddd6cc7`). Railiance-infra
+received the KRL-versus-TTL question (message `3bfa306e`). Flex-auth, as the
+current access-engine implementation, received the decision-lifetime semantics
+question (message `02c99a74`). No implementation or policy decision was assigned
+to another owner by these messages.
+
 ## Related
 
+Review 2026-09-05: reviewed the pending implementation and fixed the identity
+helper so an explicitly empty environment does not inherit the process identity.
+Regression coverage also proves an operator subject cannot override the legacy
+agent marker. Refreshed the generated high-risk path artifact after the catalog
+changes. T05 remains waiting: no corresponding reply was present in the inbox,
+and the checked owner workplans contained no resolution of these questions.
+Validation: 415 unit tests and four SSH integration tests pass; Ruff, the
+layer-conformance script, and the declaration-route CLI smoke check pass.
+
 - `history/2026-08-29-v07-scope-intent-assessment.md` — the gap analysis behind this plan
 - `history/2026-08-29-layer-model-v04-review.md`, `-v06-review.md` — the two prior reviews
 - `security-layer-model_v0.7.md` §3.4, §6.4, §9.6, §9.7, §11, §13.1