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

docs: complete hub-core MCP and risk tools

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-07 01:05:45 +02:00
parent fb2232cfee
commit fb59749533
2 changed files with 22 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -79,6 +79,9 @@ Current implementation status:
utilities needed before T06/T08.
- 2026-06-07: `HubCoreMCPServer` was added as the first T06 slice. It wraps the
generic REST endpoints with FastMCP tools and keeps the MCP layer stateless.
- 2026-06-07: T06/T07 completed in hub-core with orientation and DoI MCP tools,
canonical FOS §10 risk/alert event types, `/progress/risks` and
`/progress/alerts` REST views, and matching MCP read tools.
## Extract Now
@@ -151,7 +154,7 @@ implementation is coupled to dev-hub concepts:
| `ManagedRepo` | Contains `topic_id`, SBOM fields, and state-sync timestamps. Keep minimal repo identity in core, then add dev-hub extensions. |
| `CapabilityRequest` | Adapter seam 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. |
| `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 mixed into a single dev-hub server module. T06 should create a base registration class that receives API client/config dependencies and lets dev-hub add its own tools. |
| 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. |
The first two adapter seams are now implemented in hub-core:
@@ -186,6 +189,7 @@ to import it:
## Next Step
Continue T06 by adding DoI and FOS §10 risk/alert surfaces, then return to
`/home/worsch/state-hub` for the first import-based refactor. Do not rename
State Hub to dev-hub until T05-T08 prove the shared package boundary.
Start T08 by introducing `/home/worsch/hub-core` as an editable dependency of
`/home/worsch/state-hub`, then replace the lowest-risk generic imports first.
Do not rename State Hub to dev-hub until T05-T08 prove the shared package
boundary.