core-hub/docs/specs/interhub-legacy-inventory.md

Inter-Hub Legacy Inventory

Status: initial inventory for Core Hub compatibility work.

Production Role

inter-hub is the Haskell/IHP implementation that currently represents the second-generation interaction framework idea. Core Hub should preserve consumer-visible behavior before retiring it.

Public API v2 Routes To Preserve

• GET /api/v2/hubs
• GET /api/v2/hub-capability-manifests
• GET /api/v2/widget-types
• GET /api/v2/event-types
• GET /api/v2/annotation-categories
• GET /api/v2/policy-scopes
• GET /api/v2/openapi.json
• GET /api/v2/openapi.yaml
• GET /api/v2/docs

Protected API v2 Routes To Preserve

• POST /api/v2/token
• /api/v2/api-consumers
• /api/v2/widgets
• /api/v2/interaction-events
• /api/v2/annotations
• /api/v2/requirement-candidates
• /api/v2/decision-records
• /api/v2/deployment-records
• /api/v2/outcome-signals
• /api/v2/hub-registry

Current Consumers

• ops-hub bootstrap and gate probes use hub, manifest, API consumer, widget, interaction-event, token, and hub-registry surfaces.
• activity-core can emit through an Inter-Hub sink but has a State Hub fallback during transition.
• Custodian workplans and operator smokes depend on public route evidence and protected smoke evidence.

Data Sources For Migration

• Inter-Hub SQL migrations and schema snapshots.
• API consumer and key-prefix rows, with raw keys treated as non-recoverable.
• Hub manifests, widgets, registries, event rows, annotations, decisions, deployments, outcomes, and request logs where historically useful.

Compatibility Risk

The first Core Hub implementation preserves route presence and auth-before-business behavior with seed data. Full compatibility still requires fixture capture from legacy Inter-Hub and consumer smokes against ops-hub and activity-core.