docs: record domain hub-core import seam
This commit is contained in:
@@ -88,6 +88,9 @@ Current implementation status:
|
||||
- 2026-06-07: T08 schema imports expanded. Hub-core's TPSC schema/report
|
||||
contract now matches State Hub, and State Hub re-exports `api.schemas.tpsc`
|
||||
from `hub_core.schemas.tpsc`.
|
||||
- 2026-06-07: T08 domain schema imports started. State Hub now imports base
|
||||
domain schemas from `hub_core.schemas.domain` while keeping dev-hub-specific
|
||||
domain detail and summary schemas local.
|
||||
|
||||
## Extract Now
|
||||
|
||||
@@ -195,8 +198,8 @@ to import it:
|
||||
|
||||
## Next Step
|
||||
|
||||
Continue T08 by replacing the next lowest-risk generic schema/router imports,
|
||||
likely policy or non-mutating router seams. Do not import hub-core SQLAlchemy
|
||||
models into State Hub until the shared metadata/migration strategy is explicit.
|
||||
Do not rename State Hub to dev-hub until T05-T08 prove the shared package
|
||||
boundary.
|
||||
Continue T08 by replacing the next lowest-risk generic schema imports. Router
|
||||
imports should wait until the model metadata/migration strategy is explicit,
|
||||
or use host-model injection rather than importing hub-core SQLAlchemy models
|
||||
directly into State Hub. Do not rename State Hub to dev-hub until T05-T08 prove
|
||||
the shared package boundary.
|
||||
|
||||
Reference in New Issue
Block a user