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.	inter-hub	draft	infotech	interaction governance ihp haskell	discovery availability current target confidence rationale D3 D5 medium SCOPE.md documents the full traceability chain (widget -> interaction -> feedback -> requirement -> decision -> implementation -> outcome) with explicit in-scope/out-of-scope lists; specs/ and contracts/ dirs back this up. Note: README.md is a stale repo-seed template leftover, not representative — SCOPE.md is authoritative. current target confidence rationale A1 A3 low Haskell/IHP application (App.cabal, Main.hs, Web/Application dirs) with a `.gitea/workflows/deploy.yaml`; runnable/deployable but availability confidence is low pending direct verification of a working build in this sweep.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C1 low scope_vs_intent_and_consumer_expectations widget identity/lifecycle governance scope documented interaction event capture and annotation scope documented level confidence basis known_reliability_risks R0 low consumer_quality_signals README.md is stale/misleading (leftover repo-seed template text) — needs fixing regardless of registry status availability not independently verified (build not run during this sweep)	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 hub-specific business domain concepts outside the interaction-governance substrate	current_level target_level current_artifacts target_artifacts consumption_modes A1 A3 Haskell/IHP application application	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents SCOPE.md specs/ contracts/ Test/	recommended_for not_recommended_for known_limitations hub-based systems wanting governed, traceable UI interaction consumers needing a stable published API today (not yet independently verified in this sweep) README.md needs fixing (stale repo-seed leftover text); availability not independently build-verified this sweep

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.

Assessment notes

Discovery

SCOPE.md documents the full traceability chain (widget -> interaction -> feedback -> requirement -> decision -> implementation -> outcome) with explicit in-scope/out-of-scope lists; specs/ and contracts/ dirs back this up. Note: README.md is a stale repo-seed template leftover, not representative — SCOPE.md is authoritative.

Availability

Haskell/IHP application (App.cabal, Main.hs, Web/Application dirs) with a .gitea/workflows/deploy.yaml; runnable/deployable but availability confidence is low pending direct verification of a working build in this sweep.

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