All runbooks
docsuai-explorerredacted view

Cross-Product Migration Ops Framework (WS A–F)

The cross-product migration ops framework coordinates five parallel

Updated 2026-06-25·Freshness: Reference·No secret-like patterns were observed in this view.

Cross-Product Migration Ops Framework (WS A–F)

The cross-product migration ops framework coordinates five parallel

Body

Cross-Product Migration Ops Framework (WS A–F)

Purpose

The cross-product migration ops framework coordinates five parallel workstreams (A cleanup / B cadence finalize / C beacon-v2 readiness / D cortex investigation / E switchboard fleet) plus F coordination. It was created 2026-06-20 in response to the operator directive to "get organized and get a team going on getting everything migrate ready with a full plan and roll back plan and reexecute plan." The ops dir is the canonical surface for team state.

Current State

  • Status: active.
  • Created: 2026-06-20.
  • Authority basis: operator delegation 2026-06-20 ~22:35 UTC (G2 signoff authority for the sprint, session-scoped — future sessions must re-confirm; see R9 in the punch list).
  • Ops dir (canonical): /root/ua....
  • Source proposal: /root/ua....md.

Workstreams

WS Scope Sprint gate
A Cleanup Crew engineer-beacon takedown; 757 cadence backups cleanup; cadence-shell stub deletion All G1, operator-approved 2026-06-20
B Cadence Finalization Beacon basic-auth on cadence.united-ai.ca; Phase 0 frozen contract; Phase 6 pilot plan; v5 runbook retirement B.1 G1; B.2/B.3/B.4 G0
C Beacon v2 Readiness manifest refresh; shapeshop decision; cutover rehearsal plan; signoff gate checklist All G0 this sprint; C.5 production cutover G2 future
D Cortex vNext Investigation cortex-vnext-candidate origin investigation (PRIMARY); CT124 survey; Qdrant 401; promotion options All G0; no Cortex changes authorized
E Switchboard Fleet Bring-Up docs review; Beacon self-register (G1); CT/NUC plan (G2 plan only); end-to-end verification E.2 G1; CT/NUC registration requires future G2
F Coordination STATE.md rollup; rollback registry hygiene; gate enforcement; diary completeness Always active

Key Components / Locations

  • CHARTER.md — team structure, rules, gate definitions (G0/G1/G2).
  • STATE.md — living rollup dashboard (coordinator-only writes).
  • ROLLBACK_REGISTRY.md — per-action rollback entries using the lab notation standard; action IDs <WS>.<step> are immutable.
  • WORKSTREAM-{A,B,C,D,E}.md — per-WS detail with ## State sections.
  • DECISIONS-LOG-20260620.md — decision log.
  • Diary entries at /root/uai-explorer/diary/<YYYY-MM-DD>-ws<WS>-<slug>.md.

Cross-WS Sequencing Constraints

  • WS-B B.1 (basic-auth) restarts beacon.service — sequenced AFTER WS-A A.1 to avoid race.
  • WS-B B.5 (memory-bridge real Cortex wiring) waits on WS-D promotion decision. (D.5.4 deploy occurred 2026-06-21.)
  • WS-C C.5 (production cutover) waits on operator signoff gates closed (G2).
  • WS-E E.3 (NUC node register) waits on Tailscale path verification.
  • WS-A A.4 (cortex-vnext-candidate disposition) deferred to WS-D D.1.

Relationships

  • Coordinates: uai-doc-ecosystem-product-cadence-v6, -cortex-v2, -beacon-v2, -switchboard, -cadence-v5.
  • Sibling workstream: uai-doc-... (WS-B B.3).

Status

active — all 5 WS spawned + F coordination.

See Also

  • uai-doc-...
  • uai-doc-...
  • uai-doc-ecosystem-product-cadence-v6
  • uai-doc-ecosystem-product-beacon-v2
  • uai-doc-ecosystem-product-cortex-v2
  • uai-doc-ecosystem-product-switchboard