A library boundary between shared hub infrastructure and host-specific hub implementations.
STATE-WP-0079 is blocked on this plan: Wave B of the State Hub cutover slice plan is 125 inventory items and none can start while this sits at proposed. It is currently the largest single gate in the retirement program. Reviewed against current repo state -- nothing structurally prevents ready. The plan has been unreviewed since 2026-08-09 rather than blocked. All referenced architecture artefacts exist in prj-state-hub-retirement, and T01 is a review task whose inputs are available, so it can start immediately. Fixes the architecture citation: the path is project-relative, but reads as hub-core-relative and hub-core has no architecture/ directory. Records that port.* appears nowhere in hub-core outside this workplan, and that two of T04's five ports have no existing basis -- the minimal vertical is partly greenfield and worth sizing first. Status left at proposed for the owner to flip. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude/rules | ||
| .forgejo/workflows | ||
| docs | ||
| hub_core | ||
| registry | ||
| tests | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| INTENT.md | ||
| LICENSE | ||
| Makefile | ||
| pyproject.toml | ||
| README.md | ||
| SCOPE.md | ||
| uv.lock | ||
| WORK-RECORDS.md | ||
Hub Core
Reusable FastAPI, SQLAlchemy, and MCP primitives for FOS hubs.
Hub stack glossary
| Name | Role |
|---|---|
| hub-core | This repo — shared Python library (hub_core) |
| state-hub | Dev coordination host (workplans, MCP) |
| core-hub | Production framework (/api/v2, operator console) |
Ecosystem architecture: /home/worsch/the-custodian/docs/hub-ecosystem-architecture.md
hub-core is being extracted from the standalone State Hub repository as part
of CUST-WP-0025. The initial package slice contains only the generic database
models and schemas that can move without importing dev-hub concepts such as
topics, workplans, tasks, decisions, SBOM, or token accounting.
Source boundary notes live in:
/home/worsch/the-custodian/docs/hub-core-extraction-boundary.md
First Slice
- SQLAlchemy base metadata and timestamp helpers.
- Domain and managed-repository registry primitives.
- Agent message inbox primitives.
- Progress-event and capability-request primitives with generic JSON context fields for hub-specific references.
- Third-party service catalog and snapshot primitives.
- Matching Pydantic schemas for those primitives.
- Generic DoI report and summary schemas used by the MCP DoI tools.
- Router factory functions for domains, repos, messages, policy lookup, and progress, capability, and TPSC catalog/snapshot/report endpoints.
- Canonical FOS §10 risk and alert event types with
/progress/risksand/progress/alertsread views. - Shared utility helpers for slugs, pagination, repo path resolution, and trailing-slash path normalization.
- Alembic templates plus an initial core-schema migration for hub adopters.
- FastMCP base-server wrapper for generic orientation, messaging, capability, repo, DoI, TPSC/GDPR, risk/alert, and progress tools.
Domain-specific MCP tools follow in each hub package.