coulomb/fin-hub
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
fin-hub/workplans/FIN-WP-0003-fabric-authority-boundary.md
tegwick 655c5e6b0c docs: renumber fabric boundary workplan to FIN-WP-0003 
FIN-WP-0002 was already proposed in custodian inbox for client-billing
gap assessment; avoid id collision with State Hub retirement stream S7.
2026-08-09 21:41:20 +02:00

1.4 KiB
Raw Blame History

id type title domain repo status owner topic_slug created updated parent_project parent_workplan related
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

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

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

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

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)