Record enforced caller proof and published approval release

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0726e-5232-73f2-aaca-2c05ceb62efb

workplans/GLAS-WP-0012-first-local-profile-production-proof.md

@@ -319,3 +319,10 @@ Tenant decision update (2026-09-06): operator approved `tenant:platform` for the
 approval dependency chain as the platform management/services tenant. See
 `docs/platform-tenant-decision.md`. The choice blocker is resolved; exact owner
 configuration alignment and verification remain part of T02 before readiness.
+
+
+Later deployment progress (2026-09-06): KeyCape/approval source tenant alignment
+verified, approval release published and pinned, audit T03 complete, dedicated
+PDP revision 3 enforces adopted short-lived caller identity. See GLAS-WP-0015
+and its evidence receipts. T02 remains wait until remaining owner admission and
+runtime gates are verified; no real model run or readiness promotion.

workplans/GLAS-WP-0015-production-dependency-coordination.md

@@ -112,3 +112,50 @@ administration and services tenant (landlord zone). Recorded in
 approval store and lifecycle request must agree exactly. No alias or implicit
 cross-tenant authorization. Existing owner threads receive the approved change;
 T03 remains progress pending implementation evidence and other dependencies.
+
+
+## Later owner review and production progress — 2026-09-06
+
+Reviewed and marked read the five replies below; cross-checked the owner source
+revisions. Tenant source alignment accepted at KeyCape 7a6666d and approval
+6d18f62; no live tenant-registration claim. Audit evidence-kind prerequisite
+complete at 15e5436; exact sender scope/redaction confirmation requested.
+
+- approval-engine: `cfff917f-d6e1-4f5e-a396-e0e43ebb97e6`
+- secrets-engine: `b9c4641b-3227-47a2-84de-a696a219fd8e`
+- flex-auth: `e272f234-7ba2-458b-a6df-9c2664e4ad76`
+- audit-core: `4ae48d3d-a6fd-4f26-aaa7-c5f55a93ab75`
+- key-cape: `893e17a1-ac96-465c-ad22-af88204275cd`
+
+Published approval-engine d7a9fe5 candidate 0.1.0 and verified the registry
+index digest 73333f5ceb55e48192e3095cb2e2a741cdc6ff0be2f18128301072b4a6b6eb9d.
+Both owner deployment image references pinned; client dry-run passes. Production
+service remains undeployed until KeyCape and audit credential admission.
+
+FLEX-WP-0023 now owns the workstation path. Created the exact bound caller SA
+without role bindings and with automount disabled. Ten-minute audience-scoped
+TokenRequest identity passed warn adoption with zero warnings. Helm revision 3
+now enforces caller authentication; positive request passes, missing token and
+wrong audience return 401, wrong principal returns 403. Real expiry proof passed (expired 401, then fresh 200); see docs/evidence/GLAS-WP-0015-caller-auth-2026-09-06.json for outcomes.
+Other three consumer Deployment specs unchanged. Caller provenance/signatures
+remain live owner work (FLEX-WP-0023-T04 / FLEX-WP-0024).
+
+Five follow-ups delivered, receipts in
+`docs/production-owner-review-followups-2026-09-06.json`. GLAS-WP-0012 remains
+blocked on credential custody/adoption, approval deployment and Claude runtime
+pin/startup. No Anthropic key read or real model run. Profiles remain two blocked
+and one unverified; no readiness promotion.
+
+
+Also reviewed and marked read approval scan follow-up
+`89e21fcb-fbf8-43c0-9138-5da7f4dc0d67`; its publication blocker was resolved in
+this session. The published pin is committed in approval-engine `b51d174`.
+Independently ran approval-engine tests/test_auth.py: 23 passed. Glas fetched
+origin with no ahead/behind drift before edits; the readiness catalog validated.
+
+
+Final caller proof completed: FLEX-WP-0023-T01/T02/T03 done, including actual
+issued-token expiry and fresh-token recovery. Temporary forward removed and
+proof process exited. Final owner receipt deliveries recorded in
+`docs/production-caller-access-receipts-2026-09-06.json`. This establishes the
+operator path; consumer adoption and native action authorization remain open.