Catalog activity-core metered worker-token companion lane (SECRETS-WP-0011-T04)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 5s

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 226514@bnt-lap001
Assistant-Session: 26ba103d-05fe-45a1-9cd7-9475bf239df6
This commit is contained in:
tegwick 2026-09-23 17:49:40 +02:00
parent 0c6ffbd672
commit cd7d6922d7
2 changed files with 76 additions and 1 deletions

View file

@ -93,7 +93,7 @@ a throwaway OpenBao dev server.
id: SECRETS-WP-0011-T04
status: wait
priority: high
blocking_reason: "Needs activity-core owner assent to source ACTIVITY_CORE_WORKER_TOKEN from OpenBao (ESO) instead of a hand-generated Kubernetes Secret."
blocking_reason: "Lane cataloged. Waits on ACTIVITY-WP-0039 T02-T04: railiance-platform store policy, founder-attended seeding of the metered token, and activity-core rollout."
state_hub_task_id: "cf465065-de7a-5d9c-bc80-fee16ffef70d"
```
@ -115,3 +115,15 @@ redacts every value. Suite: 465 passed. Integration on a throwaway OpenBao: 2
passed (two lanes to one owner; the primary AppRole is denied the companion
path). Contract: `docs/exec-owner-binding.md` § Companion lanes. T04 waits on
activity-core (hub message `6e694682`).
## activity-core return — 2026-09-23
Accepted under ACTIVITY-WP-0039 (hub `053ef7c6`). activity-core `b4a7a84` adds
`ACTIVITY_CORE_WORKERS`: one token per identity, no shared token, no fallback.
The dedicated identity is `rein-aharness-metered@railiance01`, with its token at
`platform/workloads/activity-core/ops-run-workers/rein-aharness-metered-railiance01`
(field `token`), seeded fresh. Not deployed yet.
Cataloged as `activity-core-metered-worker-token` (prod, standard risk,
`companion_of: [glas-claude-agent-dev-anthropic]`, ordinary `decision`
approval). Not applied. Suite: 467 passed.