coulomb/core-hub
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
core-hub/SCOPE.md
tegwick 0709262ffd
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
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.
2026-07-11 01:26:53 +02:00

1.9 KiB
Raw Blame History

SCOPE

Boundary for agents and contributors working in Core Hub.

One-Liner

Core Hub is the 3rd-generation production interaction framework for Coulomb / Helixforge.

Core Idea

Core Hub replaces the Haskell/IHP Inter-Hub implementation with a contract-first Python/FastAPI/Postgres framework for cross-domain state, agent coordination, evidence, registry facts, workplans, and operator interaction surfaces.

In Scope

  • Core Hub intent, research, specs, and implementation workplans
  • Contract/IR definition for hubs, manifests, widgets, events, tasks, progress, messages, decisions, and registry facts
  • FastAPI/Postgres implementation planning and eventual service code
  • Inter-Hub /api/v2 compatibility where existing consumers depend on it
  • Data migration and production cutover planning from Inter-Hub
  • Operator UI and whynot-design aligned component/adaptor planning
  • Haskell/IHP retirement planning after replacement evidence exists

Out of Scope

  • Continuing to act as a generic repo template
  • Owning every downstream domain hub implementation
  • Storing or vending secrets directly
  • Rewriting unrelated consumers before the Core Hub compatibility contract exists
  • Retiring production Inter-Hub before migration and smoke evidence exists

Ecosystem position

Repo Boundary
hub-core Library — core-hub imports utils; framework models stay in core_hub
state-hub Dev coordination canonical owner for workplans/tasks until ADR says otherwise
core-hub This repo — /api/v2, framework tables, operator console

See /home/worsch/the-custodian/docs/hub-ecosystem-architecture.md.

Non-Goals

  • Recreate IHP abstractions in Python
  • Bind the UI contract to React or any single frontend framework
  • Make State Hub disappear before Core Hub proves a compatible replacement path
  • Duplicating hub-core router factories or dev-hub workplan tables locally