coulomb/the-custodian
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify core hub staging credential route

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-30 10:20:23 +02:00
parent cb7fd7b19d
commit 1f9ef92a66
4 changed files with 37 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/core-hub-replacement-evidence.md
View File

@@ -1,6 +1,6 @@
# Core Hub Replacement Evidence Handoff
Date: 2026-06-27
Date: 2026-06-30
Related workplans: `CUST-WP-0052`, `CUST-WP-0025`, `CUST-WP-0047`,
`CUST-WP-0049`, `CORE-WP-0008`, `CORE-WP-0004`, `CORE-WP-0005`,
@@ -103,6 +103,13 @@ and CLI evidence through the rebuild backlog.
## Remaining Gates
2026-06-30 route refinement: `warden route find` for the Core Hub
staging smoke token need matched the OpenBao-owned `openbao-api-key`
lane for operator/runtime credentials, with `key-cape-oidc-login`
available for interactive auth and `ops-bridge-tunnel` for private
endpoint access when needed. ops-warden can route or assist eligible lanes,
but it does not own, mint, or store Core Hub token values.
- Run `make deployed-smoke` or `make operator-cli CLI_ARGS="deployed-smoke ..."`
against a real Core Hub staging URL with an approved operator token.
- Import the approved Inter-Hub export bundle into a staging Core Hub database