hub-core/registry/capabilities/capability.infotech.hub-core-library.md

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.infotech.hub-core-library	Reusable FOS Hub Core Primitives	Reusable FastAPI, SQLAlchemy, and MCP primitives extracted from the State Hub for use by other FOS (Federation of Services) hubs.	hub-core	draft	infotech	hub fastapi sqlalchemy mcp	discovery availability current target confidence rationale D2 D4 medium README documents the extraction boundary from State Hub (CUST-WP-0025) and the first slice: base metadata, domain/repo registry primitives, agent inbox, progress-event/capability-request primitives, service catalog, DoI schemas. current target confidence rationale A1 A3 medium Python package (`hub-core`), pip-installable/importable; already has a `.forgejo/workflows/ci-smoke.yaml` CI check (ahead of most siblings on the Forgejo transition).	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C1 low scope_vs_intent_and_consumer_expectations SQLAlchemy base metadata/timestamp helpers domain and managed-repo registry primitives agent message inbox primitives progress-event/capability-request primitives Forgejo Actions CI smoke check level confidence basis known_reliability_risks R1 low consumer_quality_signals first extraction slice only; hub-specific concepts (topics, workstreams, tasks, decisions, SBOM, token accounting) intentionally excluded so far	intent includes excludes assumptions use_cases research_memos Let new FOS hubs reuse the generic primitives State Hub already built, without importing State-Hub-specific domain concepts. SQLAlchemy base metadata/timestamp helpers domain/repo registry and agent-inbox primitives progress-event/capability-request primitives with generic JSON context service catalog and DoI schemas State-Hub-specific concepts: topics, workstreams, tasks, decisions, SBOM, token accounting	current_level target_level current_artifacts target_artifacts consumption_modes A1 A3 `hub-core` Python package library import	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents README.md the-custodian:docs/hub-core-extraction-boundary.md tests/ .forgejo/workflows/ci-smoke.yaml	recommended_for not_recommended_for known_limitations new FOS hub services wanting shared FastAPI/SQLAlchemy/MCP primitives consumers needing State-Hub-specific domain concepts (not extracted yet) first extraction slice; boundary still evolving alongside State Hub

Reusable FOS Hub Core Primitives

Overview

hub-core is being extracted from the standalone State Hub repository (CUST-WP-0025) to give other FOS hubs reusable FastAPI/SQLAlchemy/MCP primitives without pulling in State-Hub-specific domain concepts.

Assessment notes

Discovery

README documents the extraction boundary from State Hub (CUST-WP-0025) and the first slice: base metadata, domain/repo registry primitives, agent inbox, progress-event/capability-request primitives, service catalog, DoI schemas.

Availability

Python package (hub-core), pip-installable/importable; already has a .forgejo/workflows/ci-smoke.yaml CI check (ahead of most siblings on the Forgejo transition).

Completeness

First-pass honest assessment from the REUSE-WP-0017 coverage campaign (reuse-surface). No external consumer feedback exists yet; levels reflect scope-vs-intent documentation quality, not internal code quality.

Reliability

No production consumer telemetry exists yet; reliability level is intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.

Promotion checklist

• ID follows capability.<domain>.<name> pattern
• Maturity enums match specs/CapabilityMaturityStandard.md
• external_evidence is populated separately from maturity
• Relations reference valid capability IDs (none yet)
• Index entry added in registry/indexes/capabilities.yaml