coulomb/the-custodian
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record repo router import seam

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-07 22:27:43 +02:00
parent 063705756e
commit bf90efee28
2 changed files with 25 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/hub-core-extraction-boundary.md
View File

@@ -120,6 +120,11 @@ Current implementation status:
mounts the hub-core request list/detail router factory with State Hub's own
domain and request models injected, while keeping request creation, status
transitions, acceptance, patching, dispute, and reroute workflow routes local.
- 2026-06-07: CUST-WP-0048 T04 repos router boundary resolved. State Hub now
mounts the hub-core repo registry factory for collection, lookup, detail,
update, and host-path routes with State Hub's own models and schemas injected,
while keeping onboarding, DoI, scope-health, dispatch, archive, and
consistency-sync routes local.
## Extract Now
@@ -189,7 +194,7 @@ implementation is coupled to dev-hub concepts:
| Surface | Coupling to resolve |
| --- | --- |
| `Domain` and `domains.py` detail views | Detail counts now use a dev-hub callback behind the hub-core router factory. Domain relationships still need a later model split if State Hub stops carrying topics/goals on the core table. |
| `ManagedRepo` | State Hub create/read schemas now extend hub-core contracts, with `topic_id`, SBOM fields, and state-sync timestamps kept as dev-hub extensions. The repos router still carries onboarding, DoI, dispatch, and sync behavior locally. |
| `ManagedRepo` | State Hub create/read schemas now extend hub-core contracts, with `topic_id`, SBOM fields, and state-sync timestamps kept as dev-hub extensions. Generic repo registry collection, lookup, detail, update, and host-path routes now mount from the hub-core factory; State Hub keeps onboarding, DoI, scope-health, dispatch, archive, and consistency-sync behavior locally. |
| `CapabilityRequest` | Catalog schemas, catalog CRUD routes, and read-only request list/detail routes now import from hub-core. Adapter seam is implemented with generic `request_context` and `fulfillment_context`; State Hub still needs a later refactor to map workstream/task references into those fields or a dev-hub extension table before request workflow routes can move. |
| `ProgressEvent` | Adapter seam implemented with generic `subject_refs`; State Hub still needs a later refactor to map topic/workstream/task/decision foreign keys into that field or a dev-hub extension table. |
| MCP tools in `mcp_server/server.py` | Generic tools are still mixed into the State Hub server module. T08 should begin replacing those registrations with `HubCoreMCPServer` inheritance or composition while dev-hub keeps its own tools. |
@@ -227,7 +232,6 @@ to import it:
## Next Step
Continue T08 by applying host-model injection or callback seams to the next
lowest-risk generic routers. Repos and the capability request write workflow
each need a small dependency-injection review before replacement. Do not rename
State Hub to dev-hub until T05-T08 prove the shared package boundary.
Continue CUST-WP-0048 by resolving the capability request write workflow and
then the generic MCP registration split. Do not rename State Hub to dev-hub
until T05-T08 prove the shared package boundary.