feat(ecosystem): adopt hub-core dependency and CI pin gate (CORE-WP-0009)
Import slugify_or_default from hub-core, add contract tests, vendor hub-core in Docker/Forgejo CI, document metadata isolation and pagination deferral, and align INTENT/SCOPE with three-repo stack.
This commit is contained in:
parent
564830c4aa
commit
0709262ffd
21 changed files with 1082 additions and 55 deletions
10
README.md
10
README.md
|
|
@ -2,6 +2,16 @@
|
|||
|
||||
Core Hub is the 3rd-generation Production Interaction Framework for Coulomb / Helixforge.
|
||||
|
||||
## Hub stack glossary
|
||||
|
||||
| Name | Role |
|
||||
| --- | --- |
|
||||
| **hub-core** | Shared library — `hub_core` utils, models, router factories |
|
||||
| **state-hub** | Dev coordination — file-first workplans, agent MCP |
|
||||
| **core-hub** | This repo — production `/api/v2` framework |
|
||||
|
||||
Ecosystem architecture: `/home/worsch/the-custodian/docs/hub-ecosystem-architecture.md`
|
||||
|
||||
It carries forward the lessons from State Hub and Inter-Hub: workplans and progress need to be durable, domains need typed ways to publish state and evidence, operators need a coherent console, and agents need APIs that are predictable enough to automate against. The rebuild moves that intent onto a lighter production platform.
|
||||
|
||||
## Generations
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue