coulomb/core-hub
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
core-hub/SCOPE.md
tegwick 35be412c14
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / pytest-smoke (push) Failing after 2s
Details
chore: keep generated orientation brief local 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 8340@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c
2026-10-21 12:31:11 +02:00

2.4 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 is the contract-first Python/FastAPI/Postgres framework that replaced the Haskell/IHP Inter-Hub implementation 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
  • Maintaining the production /api/v2 compatibility contract inherited from Inter-Hub
  • Relocating the current Core Hub runtime across production hosts without coupling continuity to future framework consolidation
  • Operator UI and whynot-design aligned component/adaptor planning
  • Evidence-preserving maintenance of the completed Inter-Hub migration and Haskell/IHP retirement record

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
  • Reintroducing the retired Inter-Hub runtime as an active production path

Ecosystem position

Repo Boundary
hub-core Shared library today; any permanent host is an explicit future architecture decision
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
  • Making the unresolved hub-core library-vs-thin-host decision merely to meet a host-decommission deadline

Local orientation brief policy — 2026-10-21

.custodian-brief.md is a local, ignored State Hub orientation snapshot. Refreshing it does not require a Git commit. Authored workplans and the generated WORK-RECORDS index keep their existing source and staged-generation contracts.