coulomb/core-hub
Archived
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Set up Core Hub framework planning

Browse Source
This commit is contained in:
Bernd Worsch
2026-06-27 11:00:12 +02:00
parent 8ed13623e5
commit a69df288b7
33 changed files with 1058 additions and 274 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
SCOPE.md
View File

@@ -1,31 +1,35 @@
# SCOPE
> Lightweight boundary for agents and contributors.
> Boundary for agents and contributors working in Core Hub.
---
## One-Liner
## One-liner
Git repository template to bootstrap coulomb projects.
---
Core Hub is the 3rd-generation production interaction framework for Coulomb / Helixforge.
## Core Idea
repo-seed is the canonical template for new repos: agent instructions, registry scaffold, and onboarding conventions.
---
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
- Template files for new repo bootstrap
- Documentation for statehub_register usage
- Registry capability entry for template capability
---
- 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
- Application runtime code
- Owning downstream project implementations
- 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
## 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