tegwick
cffdf9e0e4
Maturity reassessment (2026-07-07): discovery D3->D5 to honestly reflect Phases 0-9 being complete (real controllers, tests, versioned /api/v2 with OpenAPI/OAuth/SDKs/webhooks) -- the initial D3 undersold real depth. Status set to deprecated. Availability deliberately held at A1: the Haskell/IHP build chain is the specific reason for retirement, not raised despite the deep feature implementation. Completeness raised to C3 (nine phases delivered); the one broken expectation is build-chain reliability itself. Reliability held at R0 -- retirement is negative evidence, not a promotion. relations.related_to now points at capability.infotech.core-hub, the contract-first Python/FastAPI/Postgres rebuild (see core-hub/SCOPE.md), which plans Inter-Hub /api/v2 compatibility and a migration path. Requested by Bernd as a follow-up to the reuse-surface REUSE-WP-0017 coverage sweep. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
inter-hub
Specification and reference implementation of the Interaction Hub Framework (IHF) — a governed, observable interaction substrate for hub-based AI-enabled software systems.
IHF treats every meaningful UI element as a governed interaction artifact rather than mere markup. It connects the full traceability chain from rendered widget → user interaction → structured feedback → requirement candidate → decision record → implementation change → observed outcome, so UI evolution is evidence-based rather than opinion-based.
Status
Phases 0–9 of the implementation are complete (see SCOPE.md for the full
per-phase breakdown): specification, widget registry and event capture,
structured feedback and triage, governance and decision linkage, outcome
signals and regression detection, agent-assisted proposals, cross-framework
adapter contracts, friction/health observability, federated governance and
ownership, and a versioned external API (/api/v2) with OpenAPI, OAuth
client credentials, generated SDKs, and webhooks.
The core artifact model and schema are stable. This is a working reference
implementation, not just a spec — see Web/Controller/ for the full set of
implemented controllers (governance, requirements, hub capability
manifests, federated policy overlays, deployment records, and more) and
Test/ for the test suite.
Stack
Built on IHP (the Integrated Haskell Platform) v1.5 + PostgreSQL.
devenv up
Getting oriented
- Full spec:
specs/InteractionHubFrameworkSpecification_v0.1.md(and_v0.2.md) — 19 sections covering key concepts, core modules, and the phased implementation plan - Scope and boundaries:
SCOPE.md - Architecture:
ARCHITECTURE-LAYERS.md,specs/OperationalArchitecture_v0.1.md - Build history:
workplans/
Relevant when
Building or reviewing any hub dashboard or operator surface (dev-hub,
ops-hub, fin-hub), capturing and triaging feedback on existing hub UIs, or
defining governed widget identity for a new capability surface. See
SCOPE.md for the full relevant/not-relevant breakdown and related repos.