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

65 lines
2.2 KiB
Markdown
Raw Normal View History

---
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: wait
priority: high
state_hub_task_id: "8903d552-4039-5b80-b589-3743f7751e5f"
```
Requests are prepared but not sent. Obtain explicit authorization to send
State Hub coordination messages, then send deduplicated threaded handoffs to
named owners and record actual receipt ids. Never mark delivery from file
creation alone. A sent message is not accepted work or implementation evidence.
## Review owner returns against the acceptance gates
```task
id: GLAS-WP-0015-T03
status: wait
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.