Files
inter-hub/registry
tegwick cffdf9e0e4
Some checks are pending
Build and Deploy / build-push-deploy (push) Waiting to run
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>
2026-07-07 01:43:42 +02:00
..

Capability Registry

Markdown-first capability index for federation and reuse planning.

Authoring

  1. Copy a capability entry template (see reuse-surface templates/capability-entry.template.md).
  2. Add the row to indexes/capabilities.yaml.
  3. Run reuse-surface validate from a checkout with the CLI installed.
  4. Merge to main and verify publish with reuse-surface establish --publish-check.

Federation contract: reuse-surface docs/RegistryFederation.md.