diff --git a/registry/capabilities/capability.infotech.interaction-hub-framework.md b/registry/capabilities/capability.infotech.interaction-hub-framework.md new file mode 100644 index 0000000..138364a --- /dev/null +++ b/registry/capabilities/capability.infotech.interaction-hub-framework.md @@ -0,0 +1,129 @@ +--- +id: capability.infotech.interaction-hub-framework +name: Interaction Hub Framework (IHF) +summary: Specification and reference implementation of a governed, observable interaction substrate connecting + rendered UI widgets to structured feedback, requirements, decisions, implementation changes, and observed + outcomes. +owner: inter-hub +status: draft +domain: infotech +tags: +- interaction +- governance +- ihp +- haskell +maturity: + discovery: + current: D3 + target: D5 + confidence: medium + rationale: '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: + current: A1 + target: A3 + confidence: low + rationale: 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. +external_evidence: + completeness: + level: C1 + confidence: low + basis: scope_vs_intent_and_consumer_expectations + satisfied_expectations: + - widget identity/lifecycle governance scope documented + - interaction event capture and annotation scope documented + broken_expectations: [] + out_of_scope_expectations: [] + reliability: + level: R0 + confidence: low + basis: consumer_quality_signals + known_reliability_risks: + - 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) +discovery: + intent: 'Make UI interaction observable and governable: connect every meaningful widget to structured + feedback, distilled requirements, governance decisions, and observed post-change outcomes.' + includes: + - widget identity, lifecycle governance, semantic addressability + - interaction event capture and contextual enrichment + - annotation/structured comment threads + - requirements distillation and governance ledger + - outcome observation + excludes: + - hub-specific business domain concepts outside the interaction-governance substrate + assumptions: [] + use_cases: [] + research_memos: [] +availability: + current_level: A1 + target_level: A3 + current_artifacts: + - Haskell/IHP application + target_artifacts: [] + consumption_modes: + - application +relations: + depends_on: [] + supports: [] + related_to: [] +evidence: + documentation: + - SCOPE.md + - specs/ + - contracts/ + tests: + - Test/ + consumer_feedback: [] + bug_reports: [] + incidents: [] +consumer_guidance: + recommended_for: + - hub-based systems wanting governed, traceable UI interaction + not_recommended_for: + - consumers needing a stable published API today (not yet independently verified in this sweep) + known_limitations: + - README.md needs fixing (stale repo-seed leftover text); availability not independently build-verified + this sweep +promotion_history: [] +--- + +# 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 + +- [x] ID follows `capability..` pattern +- [x] Maturity enums match `specs/CapabilityMaturityStandard.md` +- [x] `external_evidence` is populated separately from `maturity` +- [ ] Relations reference valid capability IDs (none yet) +- [x] Index entry added in `registry/indexes/capabilities.yaml` diff --git a/registry/indexes/capabilities.yaml b/registry/indexes/capabilities.yaml index f944e47..c74edc2 100644 --- a/registry/indexes/capabilities.yaml +++ b/registry/indexes/capabilities.yaml @@ -1,4 +1,21 @@ version: 1 -updated: '2026-06-16' +updated: '2026-07-06' domain: helix_forge -capabilities: [] +capabilities: +- id: capability.infotech.interaction-hub-framework + name: Interaction Hub Framework (IHF) + summary: Specification and reference implementation of a governed, observable interaction substrate + connecting rendered UI widgets to structured feedback, requirements, decisions, implementation changes, + and observed outcomes. + vector: D3 / A1 / C1 / R0 + domain: infotech + status: draft + owner: inter-hub + path: registry/capabilities/capability.infotech.interaction-hub-framework.md + tags: + - interaction + - governance + - ihp + - haskell + consumption_modes: + - application