tegwick
a1637ed449
REPO-WP-0001/0002 belong to repo-seed: these copies carry `repo: repo-seed` in their own frontmatter, so they are template residue from seeding rather than work this repository did under its own identity. They collided with repo-seed's real records on every projection reset. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 2583210@bnt-lap001 Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006 |
||
|---|---|---|
| .claude/rules | ||
| .forgejo/workflows | ||
| activity-definitions | ||
| contracts | ||
| docs | ||
| k8s | ||
| migrations | ||
| registry | ||
| scripts | ||
| src/core_hub | ||
| tests | ||
| workplans | ||
| .custodian-brief.md | ||
| .dockerignore | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| AGENTS.md | ||
| alembic.ini | ||
| CLAUDE.md | ||
| Dockerfile | ||
| INTENT.md | ||
| LICENSE | ||
| Makefile | ||
| pyproject.toml | ||
| README.md | ||
| SCOPE.md | ||
| STATE.md | ||
| uv.lock | ||
| WORK-RECORDS.md | ||
Core Hub
Core Hub is the 3rd-generation Production Interaction Framework for Coulomb / Helixforge.
Hub stack glossary
| Name | Role |
|---|---|
| hub-core | Production runtime and shared framework/library |
| state-hub | Dev coordination — file-first workplans, agent MCP |
| core-hub | This repo — previous /api/v2 runtime, retained as rollback until archive |
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
- Gen 1:
state-hub- file-backed workplans, tasks, progress, messages, and read-model synchronization. - Gen 2:
inter-hub- the integrated hub framework idea: manifests, widgets, registries, events, API consumers, and a shared UI, implemented in Haskell/IHP. - Gen 3:
core-hub- the same framework ambition rebuilt contract-first on the natural Coulomb stack.
Initial Stack Direction
- Python 3.12
- FastAPI and Pydantic v2
- SQLAlchemy async, Alembic, asyncpg, Postgres
- pytest and contract fixtures
- OpenAPI and JSON Schema for public contracts
- whynot-design aligned UI components/adapters where operator UI is needed
- Docker/Kubernetes/ArgoCD on the normal Railiance platform path
Key Documentation
- INTENT.md - purpose, lineage, principles, and platform direction
- STATE.md - current production truth, open work, and known conditions
- SCOPE.md - repo boundary
- Research artifact - what we learned from State Hub, Inter-Hub, Haskell/IHP, and whynot-design
- Specs index - contract and implementation specification map
- Workplans - staged implementation plan using ADR-001 workplan files
Current Work
The contract, FastAPI/Postgres foundation, Inter-Hub migration, Haskell/IHP
retirement, relocation from CoulombCore, and production absorption into
hub-core are complete. Hub-core revision 055cf49 is public authority. This
repository remains a no-writer rollback through the stabilization window
ending no earlier than 2026-08-28T20:49:50+02:00. New product work belongs in
hub-core; the only open local task is the prepared read-only archive closeout
in docs/deployment/archive-closeout.md.
Operational migration bundles are emitted without raw key material:
core-hub-ops migration export --source-revision "$(git rev-parse HEAD)" \
--output core-hub-export.json
CORE_HUB_V2_WRITE_GROUPS controls legacy write authority for registry,
credentials, interaction, and deferred. The deployment package must
remove a group here before enabling the matching hub-core writer.