prj-state-hub-retirement/inventory

State Hub disposition inventory

Workplan task: SHR-WP-0001-T02
Inventory ID: SHR-INV-0001
Version: 0.1.2 (authority correction, 2026-08-31)

Machine-readable disposition of State Hub surfaces for the retirement program. Every item has an initial owner and keep / move / replace / retire disposition. Values are revisable through architecture work (T03/T04) and child implementation workplans (T05).

Files

File	Contents
state-hub-disposition.yaml	Master inventory (all items)
capabilities.yaml	Capability rollup (primary owner + disposition)
routes.yaml	OpenAPI routes (live extract)
datasets.yaml	SQLAlchemy tables / compat model modules
mcp-tools.yaml	MCP tools
dashboard.yaml	Observable dashboard pages
jobs-callers-ops.yaml	Jobs, callers, ops deps, migrations

Disposition legend

Value	Meaning
keep	Still required during migration without a better home yet, or external dependency retained as-is
move	Responsibility relocates substantially intact to the named owner
replace	Capability survives under a different contract/API (not necessarily same schema)
retire	No successor runtime after evidence gates; history archived

Owner legend (initial)

Owner	Role in target architecture
hub-core	Cross-domain framework, messaging, projections, telemetry, policy integration
repo-manager	Repository representation, file-backed work-record index, consistency, governed control
activity-core	Schedulers, ops-run execution, event-triggered maintenance
ops-hub	Service catalog / operational catalogs
railiance-fabric	Specialized Fabric graph and accepted-snapshot authority
fin-hub	Financial-domain accountability and joins; no Fabric authority tables
ops-bridge	Private tunnel connectivity (transport only)
the-custodian	Kaizen agent personas and durable canon
archive	Explicitly terminated surfaces (e.g. suggestions, workstream aliases)
state-hub-until-cutover	Temporary host for migration tooling, schema history, fallback runtime
undetermined	Needs human/architecture review

Snapshot (v0.1)

Kind	Count
routes	187
datasets (+ model-compat)	44
mcp tools	88
dashboard pages	39
migrations	43
jobs	5
callers	10
ops dependencies	9
total items	425

By disposition: move 259 · replace 76 · keep 48 · retire 42

By primary owner volume: repo-manager 167 · hub-core 128 · state-hub-until-cutover 55 · archive 30 · activity-core 18 · ops-hub 13 · railiance-fabric 10 · ops-bridge 2 · the-custodian 2

Baseline counts (orientation)

From live GET /state/summary on 2026-08-09:

• topics: 14
• workplans: 868
• tasks: 5138
• decisions: 89

Full dataset row counts and recovery evidence belong to T06.

Regeneration notes

Routes were extracted from the live OpenAPI document at http://127.0.0.1:8000/openapi.json. Models, MCP tools, dashboard pages, and migrations were scanned from the state-hub checkout. Callers and jobs combine source docs (hub-ecosystem-route-audit, cron-migration, workstream-caller-inventory, cluster operating model) with the retirement GOAL.md / INTENT.md direction.

To refresh after large State Hub changes, re-run the extraction against a current checkout and OpenAPI, then re-apply capability mapping rules (or edit YAML deliberately and bump version / updated).

Open review points

1. Topics vs classification domains — topics marked replace; confirm residual need after classification spine is universal.
2. Task-flow engine — assigned activity-core / replace; confirm whether flow defs stay repo files with a thinner runtime.
3. Service catalog vs TPSC — split between ops-hub and hub-core; may consolidate under one catalog authority.
4. Dashboard home — currently replace under hub-core projection UI; may become multi-consumer or a small ops surface instead of one mega-dashboard.
5. Undetermined items — none remaining after intake/dependency mapping (v0.1.1).