inter-hub/registry/capabilities/capability.infotech.interaction-hub-framework.md

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance, promotion_history

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.infotech.interaction-hub-framework	Interaction Hub Framework (IHF)	Specification and reference implementation of a governed, observable interaction substrate connecting rendered UI widgets to structured feedback, requirements, decisions, implementation changes, and observed outcomes. Retired (Haskell/IHP build-chain problems); superseded by core-hub.	inter-hub	deprecated	infotech	interaction governance ihp haskell retired	discovery availability current target confidence rationale D5 D5 high Reassessed 2026-07-07 against the actual implementation, not just SCOPE.md prose: Phases 0-9 are complete per SCOPE.md's own per-phase log, with real Web/Controller/ modules (governance, requirements, hub capability manifests, federated policy overlays, deployment records, agent registrations, webhooks, and more), a Test/ suite, and a versioned external API (/api/v2) with OpenAPI, OAuth client credentials, generated SDKs, and rate limiting. This was a substantial working reference implementation, not a paper spec -- discovery confidence raised from medium to high and D3 to D5 accordingly. Target stays D5: no further discovery work is planned now that the repo is retired. current target confidence rationale A1 A1 high Deliberately NOT raised despite the deep implementation: the Haskell/IHP build chain is the specific reason this capability was retired (2026-07-07, owner decision) in favor of core-hub on a more convenient Python/FastAPI/Postgres stack. Feature completeness and build/deploy reliability are different axes -- this one stayed low precisely because the latter broke down. Target frozen at A1; no further availability investment is planned.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C3 medium scope_vs_intent_and_consumer_expectations widget identity/lifecycle governance implemented (Phase 1) structured feedback, triage, and requirement distillation implemented (Phases 2-3) governance ledger and decision records implemented (Phase 3) outcome signals and regression detection implemented (Phase 4) agent-assisted proposals and review implemented (Phase 5) cross-framework adapter contracts (EnvelopeEmissionContract, WidgetAdapterSpec, React adapter) implemented (Phase 6) friction/health observability implemented (Phase 7) federated governance and delegated ownership implemented (Phase 8) versioned external API with OpenAPI, OAuth, SDKs, webhooks implemented (Phase 9) build chain reliability -- the reason for retirement; feature completeness did not translate into a dependable build/deploy path level confidence basis known_reliability_risks R0 high consumer_quality_signals RETIRED 2026-07-07: owner decision to retire this capability due to persistent Haskell/IHP build-chain problems. This is itself the reliability evidence -- a substantial feature-complete implementation that could not be kept dependably buildable/deployable. Do not build new integrations against it. successor is core-hub (capability.infotech.core-hub), a contract-first rebuild on Python/FastAPI/Postgres, explicitly scoped to include Inter-Hub /api/v2 compatibility and a data-migration/cutover plan during the transition (see core-hub/SCOPE.md)	intent includes excludes assumptions use_cases research_memos Make UI interaction observable and governable: connect every meaningful widget to structured feedback, distilled requirements, governance decisions, and observed post-change outcomes. widget identity, lifecycle governance, semantic addressability interaction event capture and contextual enrichment annotation/structured comment threads requirements distillation and governance ledger outcome observation federated governance, delegated ownership, cross-hub policy overlays (Phase 8) versioned external API surface (Phase 9) hub-specific business domain concepts outside the interaction-governance substrate new development -- retired; see core-hub for active work	current_level target_level current_artifacts target_artifacts consumption_modes A1 A1 Haskell/IHP application (retired, reference/historical only) application	depends_on supports related_to capability.infotech.core-hub	documentation tests consumer_feedback bug_reports incidents SCOPE.md specs/InteractionHubFrameworkSpecification_v0.1.md specs/InteractionHubFrameworkSpecification_v0.2.md contracts/ Test/ Haskell/IHP build-chain instability led to full retirement of this capability (2026-07-07)	recommended_for not_recommended_for known_limitations historical reference and prior-art study for governed interaction substrates understanding requirements that core-hub's Inter-Hub /api/v2 compatibility layer must satisfy any new integration or development -- retired; use core-hub instead Retired. Do not build against this. See capability.infotech.core-hub for the active successor (Python/FastAPI/Postgres, contract-first, includes an Inter-Hub /api/v2 compatibility and migration plan).	date dimension from to rationale author 2026-07-07 discovery D3 D5 Reassessed against the actual Phases 0-9 implementation (controllers, tests, versioned API) rather than SCOPE.md prose alone; the initial D3 undersold real discovery depth. reuse-surface-coverage-review date dimension from to rationale author 2026-07-07 reliability R0 R0 Owner retired this capability due to persistent Haskell/IHP build-chain problems; status set to deprecated, availability target frozen at A1, relations point at capability.infotech.core-hub as successor. Reliability level held at R0 -- the retirement is negative evidence, not a promotion. bernd

Interaction Hub Framework (IHF)

Overview

inter-hub specifies and implements the Interaction Hub Framework (IHF): every meaningful UI widget becomes a governed interaction artifact with a full traceability chain from rendered widget through user interaction, structured feedback, requirement distillation, governance decision, implementation change, to observed outcome.

Retired 2026-07-07. The Haskell/IHP implementation reached substantial feature completeness (Phases 0-9) but suffered persistent build-chain problems. The owner decided to retire this capability and rebuild the same framework ambition on a more convenient technology stack: see core-hub (capability.infotech.core-hub), a contract-first Python/FastAPI/Postgres rebuild that plans Inter-Hub /api/v2 compatibility and a migration path.

Assessment notes

Discovery

Reassessed 2026-07-07 against the actual implementation: Phases 0-9 complete per SCOPE.md's own per-phase log, with real Web/Controller/ modules, a Test/ suite, and a versioned external API. This was a substantial working reference implementation, not a paper spec — raised from D3 to D5.

Availability

Deliberately not raised: the Haskell/IHP build chain is the specific reason this capability was retired. Feature completeness and build/deploy reliability are different axes, and this one is exactly why the retirement happened.

Completeness

Nine implementation phases delivered against the original spec's traceability chain — genuinely high completeness on the feature axis (C3). The one broken expectation, build-chain reliability, is exactly what triggered retirement.

Reliability

Held at R0. The retirement itself is the reliability signal: a feature-complete implementation that could not be kept dependably buildable. This is documented as an incident, not glossed over.

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 (capability.infotech.core-hub)
• Index entry added in registry/indexes/capabilities.yaml