Clarify workload secret posture stewardship

workplans/WARDEN-WP-0015-secret-lifecycle-tiering.md

@@ -58,7 +58,8 @@ own process (inbox/PR), not a unilateral write from here.
 **Depends on / relates to:** WARDEN-WP-0014 (the `warden access` proxy is the
 posture-aware fetch surface; its caller-identity/transit guardrails are prod-compatible).
 
-**Status:** `proposed` — awaiting Bernd's review before implementation.
+**Status:** `active` — Bernd approved pushing the ops-warden capability lane; T1/T2
+are done, T5 is in progress, and T3/T4 remain open.
 
 ---
 
@@ -187,19 +188,24 @@ state_hub_task_id: "e556fd2e-4e39-4c7d-bd94-b4330e4bef45"
 
 ```task
 id: WARDEN-WP-0015-T05
-status: todo
+status: progress
 priority: medium
 state_hub_task_id: "298c9b09-4a5a-41bf-a3bd-6c572385236b"
 ```
 
-- [ ] `INTENT.md`: ops-warden stewards **security-policy conformance** of the
+- [x] `INTENT.md`: ops-warden stewards **security-policy conformance** of the
       infrastructure (authoring the two-axis posture standard + conformance checks + dev
       doubles), scoped to author+check — **not** enforcement or custody.
-- [ ] SCOPE: add the posture policy + conformance surface; note the net-kingdom /
+- [x] SCOPE: add the posture policy + conformance surface; note the net-kingdom /
       info-tech-canon homes; bump the maturity vector where warranted.
 - [ ] Track the info-tech-canon contribution (generic `WorkloadMaturityLevel`) and the
       net-kingdom requirements landing to closure.
-- [ ] `history/2026-06-27-workload-security-posture-charter.md` — decision record.
+- [x] `history/2026-06-27-workload-security-posture-charter.md` — decision record.
+
+2026-06-27 progress: updated `INTENT.md` / `SCOPE.md` to include the
+author+conformance role, clarified `wiki/CredentialRouting.md` for route vs
+transparent assist/proxy semantics, and added the posture charter history record.
+Canon landing/tracking remains open.
 
 ---