feat(ecosystem): hub-core library lane for three-repo stack (HUB-WP-0003)
Some checks failed
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / pytest-smoke (push) Failing after 2s

Add slugify_or_default for core-hub parity, bump to 0.2.0, document ecosystem
position in INTENT/SCOPE/README, wire capability relations to state-hub and
core-hub, and extend utils tests. Part of CUST-WP-0057 consolidation.
This commit is contained in:
tegwick 2026-07-11 01:26:47 +02:00
parent 41a396e807
commit 118d4fdcfe
16 changed files with 1766 additions and 21 deletions

View file

@ -2,6 +2,16 @@
Reusable FastAPI, SQLAlchemy, and MCP primitives for FOS hubs.
## Hub stack glossary
| Name | Role |
| --- | --- |
| **hub-core** | This repo — shared Python library (`hub_core`) |
| **state-hub** | Dev coordination host (workplans, MCP) |
| **core-hub** | Production framework (`/api/v2`, operator console) |
Ecosystem architecture: `/home/worsch/the-custodian/docs/hub-ecosystem-architecture.md`
`hub-core` is being extracted from the standalone State Hub repository as part
of `CUST-WP-0025`. The initial package slice contains only the generic database
models and schemas that can move without importing dev-hub concepts such as