fin-hub/workplans/FIN-WP-0003-fabric-authority-boundary.md

1.6 KiB

id type title domain repo status owner topic_slug created updated parent_project parent_workplan related state_hub_workstream_id
FIN-WP-0003 workplan Fabric authority boundary for State Hub retirement financials fin-hub proposed codex financials 2026-08-09 2026-08-09 prj-state-hub-retirement SHR-WP-0001
FIN-WP-0001
SHR-INV-0001
STATE-WP-0079
1f6698f4-65b9-4e3b-bdf5-b079341e4581

Fabric authority boundary for State Hub retirement

Goal

Keep fabric graph data authority in fin-hub (or its specialized engine), define any hub-core projection, and support State Hub fabric route disposition (move → fin-hub).

Confirm authority and APIs

id: FIN-WP-0003-T01
status: todo
priority: high
state_hub_task_id: "4471c006-5740-4241-8c81-251134c82f0d"

Document which fabric entities/APIs are authoritative here vs State Hub read models; publish consumer contract for migration.

Migration path from State Hub fabric routes

id: FIN-WP-0003-T02
status: todo
priority: high
state_hub_task_id: "76c7ed79-8614-4e42-9e4c-f50bf789b584"

With STATE-WP-0079, plan cutover for fabric ingest/read routes and dashboard consumers; row-count and provenance checks.

Optional hub projection

id: FIN-WP-0003-T03
status: todo
priority: low
state_hub_task_id: "ae36e4e7-c39d-4027-bc49-e7abb52fb9e1"

If orientation needs a hub-core projection, define port usage without copying authority tables into hub-core.

Acceptance

  • Authority boundary documented
  • Migration path agreed with State Hub strangler
  • Projection decision recorded (implement or explicitly defer)