History

tegwick 0709262ffd Some checks failed CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / pytest-smoke (push) Failing after 2s Details Build and Publish Container Image / build-and-push (push) Failing after 1m51s Details feat(ecosystem): adopt hub-core dependency and CI pin gate (CORE-WP-0009) Import slugify_or_default from hub-core, add contract tests, vendor hub-core in Docker/Forgejo CI, document metadata isolation and pagination deferral, and align INTENT/SCOPE with three-repo stack.		2026-07-11 01:26:53 +02:00
..
api-v2-compatibility.md	Implement ops-hub bootstrap compatibility	2026-06-27 13:04:54 +02:00
auth-access-and-custody.md	Set up Core Hub framework planning	2026-06-27 11:00:12 +02:00
contract-governance.md	Start Core Hub FastAPI replacement foundation	2026-06-27 11:41:26 +02:00
contract-ir.md	Set up Core Hub framework planning	2026-06-27 11:00:12 +02:00
core-hub-architecture.md	feat(ecosystem): adopt hub-core dependency and CI pin gate (CORE-WP-0009)	2026-07-11 01:26:53 +02:00
data-model.md	feat(ecosystem): adopt hub-core dependency and CI pin gate (CORE-WP-0009)	2026-07-11 01:26:53 +02:00
event-and-registry-model.md	Set up Core Hub framework planning	2026-06-27 11:00:12 +02:00
interhub-legacy-inventory.md	Implement ops-hub bootstrap compatibility	2026-06-27 13:04:54 +02:00
operator-ui-rebuild-backlog.md	Add operator UI rebuild backlog	2026-06-27 21:34:10 +02:00
ops-evidence-contract.md	Define ops evidence contract	2026-06-27 23:56:34 +02:00
pagination-adoption.md	feat(ecosystem): adopt hub-core dependency and CI pin gate (CORE-WP-0009)	2026-07-11 01:26:53 +02:00
README.md	feat(ecosystem): adopt hub-core dependency and CI pin gate (CORE-WP-0009)	2026-07-11 01:26:53 +02:00
testing-release-and-migration.md	Add operator UI rebuild backlog	2026-06-27 21:34:10 +02:00
ui-operator-console.md	Add operator UI rebuild backlog	2026-06-27 21:34:10 +02:00
whynot-ui-adapter.md	Define Core Hub operator UI contract	2026-06-27 13:39:13 +02:00
workplan-coordination.md	Set up Core Hub framework planning	2026-06-27 11:00:12 +02:00

README.md

Core Hub Specs

This directory is the specification map for Core Hub. The specs are intentionally ahead of implementation so the framework contract stays stable while the runtime is rebuilt.

Spec Set

Architecture - component model and boundaries
Contract and IR - canonical framework contract, schemas, fixtures, and adapter rules
API v2 Compatibility - Inter-Hub compatibility surface to preserve during transition
Inter-Hub Legacy Inventory - initial route/data/consumer inventory for migration
Contract Governance - how contract changes are reviewed and recorded
Data Model - initial entity model and migration posture
Event and Registry Model - event catalogs, manifests, widgets, and capability registries
Ops Evidence Contract - runtime evidence resources, event vocabulary, read-model gaps, and non-secret mapping rules
Auth, Access, and Custody - API auth semantics and secret routing rules
Workplan Coordination - file-first workplans, tasks, progress, messages, decisions
UI and Operator Console - whynot-design aligned UI direction
Operator UI Rebuild Backlog - gated first-screen backlog after API/CLI proof
whynot UI Adapter - design-system consumption and adapter rules
Testing, Release, and Migration - verification, deployment, and cutover gates
Pagination adoption - hub-core utils deferral and adoption trigger

Contract Artifacts

Implementation-neutral artifacts live in contracts/:

contracts/schemas/
contracts/catalogs/
contracts/fixtures/
contracts/openapi/

Contract Rule

The implementation may change. The contract changes only through a workplan and a compatibility note.

Any route, schema, event type, or manifest field used by existing consumers must have one of:

preserved behavior;
documented replacement and migration path;
explicit cancellation decision with affected consumers listed.