prj-state-hub-retirement/architecture/child-workplan-map_v0.1.md

id	type	title	status	version	created	updated	workplan_task	parent_workplan	related
SHR-ARCH-MAP-0001	architecture	Child workplan map — State Hub retirement	active	0.1	2026-08-09	2026-08-09	SHR-WP-0001-T05	SHR-WP-0001	architecture/information-model_v0.1.md architecture/hub-extension-architecture_v0.1.md inventory/state-hub-disposition.yaml GOAL.md

Child workplan map v0.1

Purpose

Record one local implementation owner and workplan per stream for State Hub retirement, with dependencies and project gates. Task lists stay in child repos; this project only links stable IDs (SCOPE work-record rule).

Parent foundation: SHR-WP-0001. Architecture freeze inputs: SHR-ARCH-IA-0001, SHR-ARCH-HUB-0001, SHR-INV-0001.

---

Stream overview

Stream	Repo	Workplan	Status	Role
S1 Repo Manager foundation	repo-manager	RMGR-WP-0001	proposed	Extract repo registry, consistency, work-record index
S2 hub-core runtime + contract	hub-core	HUB-WP-0004	proposed	Consolidate runtime, ship extension contract Tier 1
S3 core-hub absorption	core-hub	CORE-WP-0010	proposed	Absorb /api/v2 into hub-core; archive core-hub
S4 State Hub strangler	state-hub	STATE-WP-0079	proposed	Compatibility adapters; disposition execution; freeze growth
S5 activity-core ports	activity-core	ACTIVITY-WP-0029	proposed	Schedule/sink alignment to hub ports
S6 ops-hub extension	ops-hub	OPS-WP-0003	proposed	Manifest + extension contract conformance
S7 fin-hub fabric boundary	fin-hub + railiance-fabric	FIN-WP-0003	finished	Specialized Fabric authority; executable parity gate; hub projection deferred
S8 Project gates (evidence)	prj-state-hub-retirement	SHR-WP-0001-T06	todo	Baseline counts + retirement gates

Secondary / support (no new WP required yet):

Concern	Repo	Existing / note
Work-record canon	the-custodian	work-record-types_v0.1.md; project-repo flavor done
Issue projection boundary	issue-core	ISSUE-WP-0004 finished — monitor only
Connectivity	ops-bridge	Transport only; retarget at cutover (no WP)
Client billing gaps	fin-hub	FIN-WP-0002 reserved by custodian inbox (not this project) — see the-custodian/docs/fin-hub-client-billing-gap.md

---

Dependency graph

SHR-WP-0001 (T01–T04 done; T05 map; T06 gates)
    │
    ├─► RMGR-WP-0001 ─────────────────────────────┐
    │         │                                   │
    │         ▼                                   │
    ├─► HUB-WP-0004 ──► CORE-WP-0010 ─────────────┤
    │         │                │                  │
    │         ├─► OPS-WP-0003  │                  │
    │         ├─► ACTIVITY-WP-0029                │
    │         └─► FIN-WP-0003                     │
    │                  │                          │
    └─► STATE-WP-0079 ◄┘  (strangler consumes     │
              │            owners' ports)         │
              ▼                                   │
         SHR-WP-0001-T06 gates ◄──────────────────┘
              │
              ▼
         Project retirement (GOAL.md)

Parallelism: RMGR-WP-0001 and HUB-WP-0004 may start in parallel after this map. CORE-WP-0010 waits on HUB-WP-0004 contract artefacts (Tier 1). STATE-WP-0079 starts after map; cutover slices wait on owner APIs. Domain hub WPs wait on HUB-WP-0004 port/schema freeze.

---

Stream detail (links only — no task copies)

S1 — RMGR-WP-0001 (repo-manager)

• Path: repo-manager/workplans/RMGR-WP-0001-foundation.md
• Outcome: Repository representation + observation/command contracts + first vertical slice; State Hub extraction dispositions for repo/consistency/work index.
• Depends on: SHR-ARCH-IA-0001, SHR-INV-0001 (repo-* capabilities)
• Unblocks: STATE-WP-0079 move of repo/work surfaces; hub-core port.repo / port.work implementations
• Predecessors: none local (new repo)

S2 — HUB-WP-0004 (hub-core)

• Path: hub-core/workplans/HUB-WP-0004-runtime-and-extension-contract.md
• Outcome: hub-core as surviving runtime+SDK; helixforge.hub-extension Tier 1 schemas; ports; absorb core-hub runtime path planning
• Depends on: SHR-ARCH-HUB-0001, finished HUB-WP-0003 (library lane)
• Unblocks: CORE-WP-0010, OPS-WP-0003, ACTIVITY-WP-0029, FIN-WP-0003, adapters
• Predecessors: HUB-WP-0002 finished, HUB-WP-0003 finished

S3 — CORE-WP-0010 (core-hub)

• Path: core-hub/workplans/CORE-WP-0010-runtime-absorption-and-archive.md
• Outcome: Production traffic on consolidated hub-core; core-hub archived read-only
• Depends on: HUB-WP-0004; finished CORE-WP-0004/0008/0009
• Unblocks: T06 core-hub archive gate; ops-hub consumer re-smoke on new host

S4 — STATE-WP-0079 (state-hub)

• Path: state-hub/workplans/STATE-WP-0079-retirement-strangler.md
• Outcome: Per-capability strangler using inventory dispositions; register CLI GOAL.md support; no new permanent authorities; eventual freeze window
• Depends on: SHR-INV-0001; progressive deps on RMGR/HUB cutovers
• Unblocks: T06 stabilization window
• Predecessors: STATE-WP-0074 finished (boundary docs); legacy meter WPs finished

S5 — ACTIVITY-WP-0029 (activity-core)

• Path: activity-core/workplans/ACTIVITY-WP-0029-hub-port-alignment.md
• Outcome: Sweeps, sinks, execution aligned to hub-core / repo-manager ports
• Depends on: HUB-WP-0004 ports; partial STATE/RMGR availability
• Predecessors: ACTIVITY-WP-0015, ACTIVITY-WP-0017 finished

S6 — OPS-WP-0003 (ops-hub)

• Path: ops-hub/workplans/OPS-WP-0003-extension-contract-alignment.md
• Outcome: Domain/aspect hub package conforming to extension contract
• Depends on: HUB-WP-0004 Tier 1; CORE-WP-0010 dual-run as needed
• Predecessors: OPS-WP-0001/0002 archived (bootstrap history)

S7 — FIN-WP-0003 (fin-hub + railiance-fabric)

• Path: fin-hub/workplans/FIN-WP-0003-fabric-authority-boundary.md
• Outcome: Fabric graph authority retained in the specialized engine; State Hub routes have explicit replacements and an executable parity gate; hub-core projection deferred
• Depends on: SHR-INV fabric-graph
• Predecessors: FIN-WP-0001 finished

S8 — SHR-WP-0001-T06 (this project)

• Baseline counts, callers, recovery, executable gates from GOAL.md
• Depends on streams having measurable handoff evidence

---

Project gates (owned here; evidence from children)

Gate ID	Statement	Evidence owners
G-ARCH	IA + extension architectures reviewable	SHR-WP-0001 T03/T04 (done)
G-MAP	Each stream has a local WP	this map + child files (T05)
G-RMGR	Repo Manager vertical slice	RMGR-WP-0001
G-HUB	Extension contract Tier 1 + runtime path	HUB-WP-0004
G-CORE	core-hub traffic on hub-core; repo archived	CORE-WP-0010
G-DISP	Inventory move/replace items on new owners	STATE-WP-0079 + owners
G-COMPAT	Consumer smokes (ops-hub, activity-core, agents)	CORE/HUB/ACTIVITY/OPS
G-FREEZE	Zero normal State Hub traffic window	STATE-WP-0079 + T06
G-RETIRE	Backup/restore/history accepted; SH stopped	T06 + STATE-WP-0079

Detailed measurable criteria: SHR-WP-0001-T06.

---

Predecessor / historical (do not re-open)

ID	Repo	Note
CUST-WP-0057	the-custodian	Three-repo ecosystem consolidation parent (historical)
HUB-WP-0003	hub-core	Library lane — finished
CORE-WP-0009	core-hub	hub-core adoption — finished
STATE-WP-0074	state-hub	Boundary alignment — finished
ISSUE-WP-0004	issue-core	Work-record alignment — finished

---

How to use this map

1. Implement only inside the child workplan’s repo.
2. Link progress back with origin_ref: SHR-WP-0001 or progress events naming the child WP id.
3. Do not duplicate child tasks into this project.
4. When a child WP finishes, hand residuals as live records; update this map’s status column in a small follow-up edit.
5. New streams require a row here and a file in the owning repo.

Acceptance (T05)

• Every T04-suggested stream has a local workplan id and path
• Dependencies and gates recorded without copying task lists
• Predecessors identified
• Child files created or confirmed present