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

---
id: GLAS-WP-0015
type: workplan
title: "Drive owner returns for the first production Glas profile"
domain: infotech
repo: glas-harness
status: active
owner: codex
topic_slug: production-dependency-coordination
created: "2026-09-06"
updated: "2026-09-06"
state_hub_workstream_id: "94c02b1f-66ed-588d-bdd7-7158107b85fb"
---

# Production dependency coordination

GLAS-WP-0012 remains the real-profile acceptance workplan. This plan owns only
concrete handoffs and receipt tracking from Glas; it does not duplicate owner
implementation tasks or authorize credential access. User requested driving
the dependencies from this repo after the policy-service production rollout.

## Prepare exact owner requests

```task
id: GLAS-WP-0015-T01
status: done
priority: high
state_hub_task_id: "ddc1a421-079c-52ad-bc0e-591010942205"
```

Reviewed KEY-WP-0013, its existing provisioning packet, AUDIT-WP-0009-T09,
APPROVAL-WP-0002, FLEX-WP-0021, SECRETS-WP-0009 and SAND-WP-0015. Prepared
seven concrete requests in docs/production-dependency-handoffs.md. Includes
live PDP coordinates, custody paths, tenant mismatch, audit startup critical
path, independent image/runtime preparation, and proof project binding mismatch.

## Deliver and track owner handoffs

```task
id: GLAS-WP-0015-T02
status: done
priority: high
state_hub_task_id: "8903d552-4039-5b80-b589-3743f7751e5f"
```

Completed 2026-09-06 after explicit user authorization. Sent one deduplicated
root message to each of the seven owners; State Hub returned 201 and actual
message IDs, recorded in docs/production-handoff-receipts.json. Replies must
use the root message ID as thread_id. The first attempt with a newly invented
thread UUID was rejected before delivery; it was corrected, not counted as sent.
A delivered message is not owner acceptance or implementation evidence.

## Review owner returns against the acceptance gates

```task
id: GLAS-WP-0015-T03
status: progress
priority: high
state_hub_task_id: "68fcc1b4-537b-5f5e-afb5-063c44e5e4db"
```

Track tenant agreement, client custody/identity, audit onboarding, approval
release, native activation and runtime binding against the linked owner tasks.
Check revisions and positive/negative evidence; feed verified returns into
GLAS-WP-0012-T02. Keep unfulfilled owner work live, and do not close this plan
while actionable requests lack an owning record or acknowledged disposition.

## Delivery receipts

| Owner | Root message / reply thread |
|---|---|
| key-cape | `356f6977-d361-4e3b-83ab-b2c7f4759286` |
| railiance-platform | `1b88b600-7b5d-4e3f-9999-8b8fec54b1ef` |
| audit-core | `85c68e66-46e3-4d30-a72f-4e104e2bbe5c` |
| approval-engine | `1e45cc7f-f1f5-40a8-b3f9-f1f8d78ece5c` |
| secrets-engine | `7ab6d325-11a2-4f94-9736-b17335054e3c` |
| flex-auth | `16172bc0-2935-40fe-8b5b-847132ecb689` |
| sand-boxer | `481b18b6-54ae-44bc-bb31-ffd130d6d8ad` |

## Owner acknowledgements and verified progress

- secrets-engine: `ac6674c7-f737-4437-8287-f39962ed7031` (reviewed and marked read).
- flex-auth: `b3228e3d-d002-4782-95f1-366a6b11475d` (reviewed and marked read).
- approval-engine: `d96200ef-5dd4-4cec-9bf7-abb29e2af780` (reviewed and marked read).
- audit-core: `995a2799-d7a7-477a-b38d-fcef61392067` (reviewed and marked read).
- sand-boxer: `202429d3-8937-433b-9fac-4ea418f04e58` (reviewed and marked read).
- key-cape: `9957e19d-e095-4e9d-9db8-ab0c468ceadd` (reviewed and marked read).

Six owners acknowledged; platform custody reply remains outstanding.
Verified sand-boxer 23d0c2b source profile and exact project binding. No
production readiness follows from the unpinned Claude executable.

Flex-auth v1 failed to enforce tenant. Deployed the owner v2 correction from
CI main-d98323b at digest
sha256:db1c4f7e621c7ea119489a321d7db0e05da09afc17be5f69d873b2b3c7f60cfc,
Helm revision 2. Six live fixtures pass including wrong_tenant denial; other
consumer Deployment specs unchanged. Receipt file:
docs/evidence/GLAS-WP-0015-policy-v2-2026-09-06.json. Do not roll back to the
known over-permissive v1; if v2 cannot operate, stop this consumer release.

Operator tenant choice is pending. Follow-ups request live tracking of the
workstation caller path, independent Claude packaging, audit T03 then T09,
and correct v2 adoption. T03 remains progress until owner prerequisites are
verified; no real credential or model run has occurred.