2.7 KiB
2.7 KiB
FOS Hub Bootstrap Sequence Status
Updated: 2026-06-27
Purpose
Track CUST-WP-0051-T07: sequence CUST-WP-0025 so FOS Hub bootstrap can resume from current repo reality rather than the older mega-hub/Keycloak assumptions.
Current Decision
Do not restart FOS bootstrap at the old NK-WP-0001 Keycloak path. That workplan is archived and superseded. The active identity baseline is:
NK-WP-0002local identity: complete; usable for bootstrap/dev OIDC.NK-WP-0012IAM Profile v0.2: finished; canonical NetKingdom-owned profile and conformance suite.- KeyCape/Authelia/LLDAP stack from the superseding NetKingdom path: current lightweight identity mode.
NK-WP-0011expanded-mode Keycloak: proposed enterprise federation lane, not a blocker for ops-hub bootstrap.
Sequence Board
| Area | Current state | Pickup action |
|---|---|---|
| Identity | Old CUST-WP-0025-T01 pointed at archived NK-WP-0001; local identity and IAM Profile v0.2 are done. |
Keep T01 cancelled, T02 done, and make T03 the remaining identity gate: a protected FastAPI fixture using IAM Profile v0.2 against local-identity or KeyCape. |
| Hub extraction/dev-hub | CUST-WP-0025-T05 through T12 are done: hub-core exists, State Hub imports hub-core, and MCP naming moved to dev-hub. |
Treat Phase 2 as complete. Do not spend pickup energy here unless consistency drift appears. |
| Ops hub | The ops-hub repo exists as an Inter-Hub Operations extension. OPS-WP-0001 is finished; OPS-WP-0002 has T01-T03 done and waits on authenticated bootstrap/runtime key. |
Finish the Inter-Hub evidence lane first: align the activity-core mapping with the live ops vocabulary, run attended bootstrap, store runtime key by approved route, then send the first governed ops event. |
| Old ops-hub scaffold tasks | CUST-WP-0025-T13-T19 still describe a standalone hub-core/FastAPI/MCP scaffold. Current implementation direction is Inter-Hub extension-first. |
Reconcile these tasks after the Inter-Hub evidence lane closes: either rewrite them to extension-owned implementation tasks or explicitly defer the standalone hub-core service. |
| Fin hub/business | CUST-WP-0025-T20-T26 are all todo and depend on a proven multi-hub pattern. |
Defer until ops-hub has a working first signal and the identity integration gate is proven. |
Stable Pickup Order
- Close the identity drift: T01 cancelled, T02 done, T03 remains as the one real identity integration test.
- Finish
CUST-WP-0051-T03/ ops-hub Inter-Hub evidence alignment before expanding ops-hub models/tools. - Reconcile
CUST-WP-0025-T13-T19againstOPS-WP-0002once the first ops event lands. - Start fin-hub/business work only after ops-hub proves the extension pattern end-to-end.