Retire capability: Haskell/IHP build-chain problems, superseded by core-hub

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>

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

@@ -3,49 +3,67 @@ 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.
+  outcomes. Retired (Haskell/IHP build-chain problems); superseded by core-hub.
 owner: inter-hub
-status: draft
+status: deprecated
 domain: infotech
 tags:
 - interaction
 - governance
 - ihp
 - haskell
+- retired
 maturity:
   discovery:
-    current: D3
+    current: D5
     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.'
+    confidence: high
+    rationale: '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.'
   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.
+    target: A1
+    confidence: high
+    rationale: '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.'
 external_evidence:
   completeness:
-    level: C1
-    confidence: low
+    level: C3
+    confidence: medium
     basis: scope_vs_intent_and_consumer_expectations
     satisfied_expectations:
-    - widget identity/lifecycle governance scope documented
-    - interaction event capture and annotation scope documented
-    broken_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)
+    broken_expectations:
+    - build chain reliability -- the reason for retirement; feature completeness did not translate into a
+      dependable build/deploy path
     out_of_scope_expectations: []
   reliability:
     level: R0
-    confidence: low
+    confidence: high
     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)
+    - '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)
 discovery:
   intent: 'Make UI interaction observable and governable: connect every meaningful widget to structured
     feedback, distilled requirements, governance decisions, and observed post-change outcomes.'
@@ -55,42 +73,64 @@ discovery:
   - 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)
   excludes:
   - hub-specific business domain concepts outside the interaction-governance substrate
+  - new development -- retired; see core-hub for active work
   assumptions: []
   use_cases: []
   research_memos: []
 availability:
   current_level: A1
-  target_level: A3
+  target_level: A1
   current_artifacts:
-  - Haskell/IHP application
+  - Haskell/IHP application (retired, reference/historical only)
   target_artifacts: []
   consumption_modes:
   - application
 relations:
   depends_on: []
   supports: []
-  related_to: []
+  related_to:
+  - capability.infotech.core-hub
 evidence:
   documentation:
   - SCOPE.md
-  - specs/
+  - specs/InteractionHubFrameworkSpecification_v0.1.md
+  - specs/InteractionHubFrameworkSpecification_v0.2.md
   - contracts/
   tests:
   - Test/
   consumer_feedback: []
   bug_reports: []
-  incidents: []
+  incidents:
+  - Haskell/IHP build-chain instability led to full retirement of this capability (2026-07-07)
 consumer_guidance:
   recommended_for:
-  - hub-based systems wanting governed, traceable UI interaction
+  - historical reference and prior-art study for governed interaction substrates
+  - understanding requirements that core-hub's Inter-Hub /api/v2 compatibility layer must satisfy
   not_recommended_for:
-  - consumers needing a stable published API today (not yet independently verified in this sweep)
+  - any new integration or development -- retired; use core-hub instead
   known_limitations:
-  - README.md needs fixing (stale repo-seed leftover text); availability not independently build-verified
-    this sweep
-promotion_history: []
+  - '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).'
+promotion_history:
+- date: "2026-07-07"
+  dimension: discovery
+  from: D3
+  to: D5
+  rationale: 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.
+  author: reuse-surface-coverage-review
+- date: "2026-07-07"
+  dimension: reliability
+  from: R0
+  to: R0
+  rationale: 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.
+  author: bernd
 ---
 
 # Interaction Hub Framework (IHF)
@@ -99,31 +139,36 @@ promotion_history: []
 
 `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`](../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
 
-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.
+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
 
-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.
+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
 
-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.
+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
 
-No production consumer telemetry exists yet; reliability level is
-intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.
+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
 
 - [x] ID follows `capability.<domain>.<name>` pattern
 - [x] Maturity enums match `specs/CapabilityMaturityStandard.md`
 - [x] `external_evidence` is populated separately from `maturity`
-- [ ] Relations reference valid capability IDs (none yet)
+- [x] Relations reference valid capability IDs (`capability.infotech.core-hub`)
 - [x] Index entry added in `registry/indexes/capabilities.yaml`