tegwick
bf199707ff
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a137ca-5c77-7a71-b9ae-23ad9b0b5684
198 lines
6.6 KiB
Markdown
198 lines
6.6 KiB
Markdown
---
|
|
id: capability.registry.register
|
|
name: Capability registry and federation
|
|
summary: Owner Markdown entries, indexes, federation hub and planning queries.
|
|
owner: reuse-surface
|
|
status: draft
|
|
domain: helix_forge
|
|
tags:
|
|
- registry
|
|
- governance
|
|
- meta
|
|
- security
|
|
- netkingdom
|
|
- framework-reuse
|
|
maturity:
|
|
discovery:
|
|
current: D3
|
|
target: D5
|
|
confidence: medium
|
|
rationale: 'Core use case UC-RS-001 is documented in specs/UseCaseCatalog.md and
|
|
the registry model is bounded in INTENT.md, but concrete promotion workflows
|
|
are not yet grounded in registry artifacts.
|
|
|
|
'
|
|
availability:
|
|
current: A3
|
|
target: A5
|
|
confidence: medium
|
|
rationale: 'Source interface assessed 2026-10-14: Owner Markdown entries, indexes,
|
|
federation hub and planning queries. Availability describes the delivery form,
|
|
not production acceptance. Discovery is not readiness; empty and stale entries
|
|
need evidence-led maintenance.'
|
|
external_evidence:
|
|
completeness:
|
|
level: C2
|
|
name: Partial
|
|
confidence: medium
|
|
basis: scope_vs_intent_and_consumer_expectations
|
|
satisfied_expectations:
|
|
- capability IDs can be assigned in registry entries
|
|
- maturity vectors can be recorded at registration time
|
|
- CLI validate, query, and export support registry workflows
|
|
- promotion history can be recorded in entries
|
|
- federation repo registration via hosted hub API and hub CLI
|
|
broken_expectations:
|
|
- no automated duplicate detection yet
|
|
out_of_scope_expectations:
|
|
- hosting registered capabilities
|
|
- enforcing implementation architecture
|
|
reliability:
|
|
level: R3
|
|
name: Usable
|
|
confidence: medium
|
|
basis: consumer_quality_signals
|
|
known_reliability_risks:
|
|
- index drift still possible if authors skip validate
|
|
- CLI requires local venv install
|
|
- sibling repos cannot register until indexes publish raw URLs
|
|
evidence:
|
|
satisfied_signals:
|
|
- CI validate with fail-on-warnings on every push
|
|
- hub register/list/federated smoke on production reuse.coulomb.social
|
|
- pytest coverage for hub API and federation compose paths
|
|
discovery:
|
|
intent: Owner Markdown entries, indexes, federation hub and planning queries
|
|
includes:
|
|
- Owner Markdown entries, indexes, federation hub and planning queries
|
|
excludes:
|
|
- Discovery is not readiness; empty and stale entries need evidence-led maintenance
|
|
assumptions:
|
|
- unregistered capabilities are invisible for registry-driven reuse
|
|
- low-maturity entries are acceptable when evidence gaps are explicit
|
|
use_cases:
|
|
- UC-RS-001
|
|
- 'U01: Architect composes a security deployment from explicit owner contracts and
|
|
case types'
|
|
- 'U09: Maintainer observes posture, prioritizes findings, coordinates work and
|
|
verifies outcomes'
|
|
- 'U14: Framework adopter validates and reuses selected contracts, tools and reference
|
|
compositions'
|
|
research_memos:
|
|
- specs/UseCaseCatalog.md
|
|
- specs/ProductRequirementsDocument.md
|
|
availability:
|
|
current_level: A3
|
|
target_level: A5
|
|
current_artifacts:
|
|
- docs/RegistryFederation.md
|
|
- specs/CapabilityMaturityStandard.md
|
|
target_artifacts:
|
|
- packaged container release with documented SLO
|
|
consumption_modes:
|
|
- library
|
|
- CLI
|
|
relations:
|
|
depends_on: []
|
|
supports:
|
|
- capability.feature-control.evaluate
|
|
- capability.identity.vocabulary-canonicalize
|
|
related_to:
|
|
- capability.registry.validate
|
|
- capability.security.iam-tooling-suite
|
|
evidence:
|
|
documentation:
|
|
- docs/RegistryFederation.md
|
|
- specs/CapabilityMaturityStandard.md
|
|
tests:
|
|
- tests/test_hub.py
|
|
- tests/test_hub_sync.py
|
|
- .forgejo/workflows/ci.yml
|
|
consumer_feedback:
|
|
- 'reuse-surface dogfood (REUSE-WP-0011): production hub registration and /v1/federated
|
|
compose succeeded on Railiance01 without write-path regressions after WP-0011
|
|
deploy.
|
|
|
|
'
|
|
bug_reports: []
|
|
incidents: []
|
|
consumer_guidance:
|
|
recommended_for:
|
|
- Architect composes a security deployment from explicit owner contracts and case
|
|
types
|
|
- Maintainer observes posture, prioritizes findings, coordinates work and verifies
|
|
outcomes
|
|
- Framework adopter validates and reuses selected contracts, tools and reference
|
|
compositions
|
|
not_recommended_for:
|
|
- Discovery is not readiness; empty and stale entries need evidence-led maintenance
|
|
known_limitations:
|
|
- Discovery is not readiness; empty and stale entries need evidence-led maintenance
|
|
- 2026-10-14 architecture review estimates operational maturity separately; a registry
|
|
entry does not authorize execution or establish deployment.
|
|
promotion_history:
|
|
- date: '2026-06-14'
|
|
dimension: discovery
|
|
from: D0
|
|
to: D1
|
|
rationale: Added name, summary, and registry-first intent from INTENT.md.
|
|
author: reuse-surface
|
|
- date: '2026-06-15'
|
|
dimension: discovery
|
|
from: D1
|
|
to: D3
|
|
rationale: Bounded scope with UC-RS-001 and MVP registry artifacts in specs/.
|
|
author: reuse-surface
|
|
- date: '2026-06-15'
|
|
dimension: availability
|
|
from: A0
|
|
to: A3
|
|
rationale: reuse-surface CLI shipped validate, query, and export commands.
|
|
author: reuse-surface
|
|
- date: '2026-06-15'
|
|
dimension: availability
|
|
from: A3
|
|
to: A4
|
|
rationale: 'Hosted federation hub live at reuse.coulomb.social; hub register/update
|
|
via HTTP API and reuse-surface hub CLI; production deploy on Railiance01.
|
|
|
|
'
|
|
author: reuse-surface
|
|
- date: '2026-06-16'
|
|
dimension: reliability
|
|
from: R2
|
|
to: R3
|
|
rationale: 'CI gates, pytest hub/federation coverage, and production hub smoke support
|
|
normal registration workflows with documented limitations.
|
|
|
|
'
|
|
author: reuse-surface
|
|
- date: '2026-10-14'
|
|
dimension: availability
|
|
from: A4
|
|
to: A3
|
|
rationale: Interface-form reassessment from current owner sources; no completeness/reliability
|
|
promotion.
|
|
author: codex
|
|
---
|
|
|
|
# Capability registry and federation
|
|
|
|
Owner Markdown entries, indexes, federation hub and planning queries.
|
|
|
|
## Reuse boundary
|
|
|
|
Discovery is not readiness; empty and stale entries need evidence-led maintenance.
|
|
|
|
## Supported use cases
|
|
|
|
- U01: Architect composes a security deployment from explicit owner contracts and case types
|
|
- U09: Maintainer observes posture, prioritizes findings, coordinates work and verifies outcomes
|
|
- U14: Framework adopter validates and reuses selected contracts, tools and reference compositions
|
|
|
|
## Evidence and integration
|
|
|
|
- [docs/RegistryFederation.md](../../docs/RegistryFederation.md)
|
|
- [specs/CapabilityMaturityStandard.md](../../specs/CapabilityMaturityStandard.md)
|
|
|
|
Assessment: CUST-WP-0081, 2026-10-14. Relations identify interfaces to compose; they do not certify native integration. Existing external evidence levels are retained where present. New entries use conservative C1/R0 until consumer assessment exists.
|