coulomb/core-hub
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(ecosystem): adopt hub-core dependency and CI pin gate (CORE-WP-0009)
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / pytest-smoke (push) Failing after 2s
Details
Build and Publish Container Image / build-and-push (push) Failing after 1m51s
Details

Browse source 
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:
tegwick 2026-07-11 01:26:53 +02:00
parent 564830c4aa
commit 0709262ffd
21 changed files with 1082 additions and 55 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/specs/core-hub-architecture.md
View file

@ -44,3 +44,5 @@ Build the production interaction framework as a small set of explicit layers rat
- Domain hubs own their domain data and domain-specific runtime logic.
- Credential systems keep owning secrets; Core Hub records non-secret evidence and routing metadata only.
- State Hub remains active until Core Hub has a proven compatibility and migration path.
- SQLAlchemy metadata stays separate from hub-core; see `hub-core/docs/metadata-isolation.md`.
- Shared slug/pagination utilities come from `hub_core.utils`; framework tables stay in `core_hub.models`.