A library boundary between shared hub infrastructure and host-specific hub implementations.
Find a file
tegwick 9c1fdd8a4c
Some checks failed
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / pytest-smoke (push) Failing after 2s
docs(HUB-WP-0004): readiness review, fix architecture path
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>
2026-08-20 08:56:27 +02:00
.claude/rules docs: workplan-first agent guidance prose (CUST-WP-0055 T04) 2026-07-08 16:35:51 +02:00
.forgejo/workflows feat(ecosystem): hub-core library lane for three-repo stack (HUB-WP-0003) 2026-07-11 01:26:47 +02:00
docs feat(ecosystem): hub-core library lane for three-repo stack (HUB-WP-0003) 2026-07-11 01:26:47 +02:00
hub_core feat(ecosystem): hub-core library lane for three-repo stack (HUB-WP-0003) 2026-07-11 01:26:47 +02:00
registry feat(ecosystem): hub-core library lane for three-repo stack (HUB-WP-0003) 2026-07-11 01:26:47 +02:00
tests feat(ecosystem): hub-core library lane for three-repo stack (HUB-WP-0003) 2026-07-11 01:26:47 +02:00
workplans docs(HUB-WP-0004): readiness review, fix architecture path 2026-08-20 08:56:27 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-06-22 19:52:37 +02:00
.gitignore Initial commit 2026-06-16 00:31:20 +00:00
.repo-classification.yaml feat(ecosystem): hub-core library lane for three-repo stack (HUB-WP-0003) 2026-07-11 01:26:47 +02:00
AGENTS.md Regenerate agent instructions from state-hub templates (CUST-WP-0055 T01) 2026-07-08 14:50:24 +02:00
CLAUDE.md Regenerate agent instruction files for dev-hub MCP name 2026-06-22 21:24:35 +02:00
INTENT.md feat(ecosystem): hub-core library lane for three-repo stack (HUB-WP-0003) 2026-07-11 01:26:47 +02:00
LICENSE Adopt Target Revenue Source License V1C1 (org-wide preliminary rollout) 2026-07-30 00:22:33 +02:00
Makefile feat(ecosystem): hub-core library lane for three-repo stack (HUB-WP-0003) 2026-07-11 01:26:47 +02:00
pyproject.toml feat(ecosystem): hub-core library lane for three-repo stack (HUB-WP-0003) 2026-07-11 01:26:47 +02:00
README.md feat(ecosystem): hub-core library lane for three-repo stack (HUB-WP-0003) 2026-07-11 01:26:47 +02:00
SCOPE.md feat(ecosystem): hub-core library lane for three-repo stack (HUB-WP-0003) 2026-07-11 01:26:47 +02:00
uv.lock feat(ecosystem): hub-core library lane for three-repo stack (HUB-WP-0003) 2026-07-11 01:26:47 +02:00
WORK-RECORDS.md Added workplan and work records 2026-08-19 21:20:40 +02:00

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/risks and /progress/alerts read 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.