coulomb/state-hub
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
state-hub/SCOPE.md
tegwick 0b44cf12f5
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Build and Publish Multi-Context Image / build-and-push (push) Successful in 45s
Details
feat: complete cluster self-sufficiency hardening 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06d83-1cbc-71f2-b0dc-e0f48cedae43
2026-09-04 22:23:42 +02:00

2.4 KiB
Raw Blame History

SCOPE

One-Liner

State Hub is the transitional coordination service for repo-anchored workplans, tasks, decisions, progress events, repo classification and metadata, MCP tooling, and dashboard telemetry. Its primary runtime is on railiance01; local repository files remain authoritative for repository-owned work records.

In Scope

  • State Hub FastAPI service
  • PostgreSQL schema and Alembic migrations
  • FastMCP server and tool reference
  • Observable dashboard
  • repo registration (classification-driven) and consistency synchronization
  • repo classification spine (14 market domains, .repo-classification.yaml)
  • task-flow engine and flow definitions
  • SBOM, contribution, capability, demand-weighted suggestion backlog, TPSC, DoI, token, and interface-change tracking
  • State Hub tests, operational docs, policies, prompts, and local infra

Ecosystem position

Repo Role
hub-core Shared library and selected target runtime for capabilities retained after State Hub retirement
state-hub This repo — transitional coordination runtime and read projection; repository files retain work-record authority
core-hub Production /api/v2 compatibility runtime on railiance01 during consolidation into hub-core

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

State Hub does not implement Inter-Hub /api/v2 routes; those belong to core-hub. New permanent cross-domain capability should land in its disposition owner, not expand State Hub. The retirement program is governed by prj-state-hub-retirement.

Out Of Scope

  • Custodian canon and constitution content
  • Inter-Hub /api/v2 framework routes (owned by core-hub)
  • non-State-Hub domain implementation work
  • external publication or legal/financial commitments
  • plaintext secrets
  • generic hub-core extraction unless a dedicated workplan owns it
  • renaming State Hub to Dev Hub unless a dedicated workplan owns it

Extraction Note

This repo is the standalone State Hub home. It was extracted under CUST-WP-0043 from:

/home/worsch/the-custodian/state-hub

This repository is authoritative for State Hub implementation work. The embedded path in the-custodian is now a pointer only.

Workplan Convention

New State Hub-local workplans use STATE-WP-####.

Migrated legacy State Hub workplans may temporarily retain CUST-WP-#### identifiers when preserving existing State Hub workstream and task IDs is the least confusing path.