diff --git a/registry/capabilities/capability.infotech.sbom-management.md b/registry/capabilities/capability.infotech.sbom-management.md
index 5531a5f..cc36385 100644
--- a/registry/capabilities/capability.infotech.sbom-management.md
+++ b/registry/capabilities/capability.infotech.sbom-management.md
@@ -1,19 +1,96 @@
 ---
 id: capability.infotech.sbom-management
-type: capability
-name: SBOM management
-repo: sbom-nexus
+owner: sbom-nexus
+status: draft
 domain: infotech
-status: emerging
-interfaces:
-  - http
-  - cli
+maturity:
+  discovery:
+    current: D3
+    target: D5
+    confidence: medium
+    rationale: Owner scope, neighboring responsibilities, concrete use cases and limitations
+      are documented; no exhaustive or generalized maturity claim.
+  availability:
+    current: A4
+    target: A4
+    confidence: medium
+    rationale: 'Source interface assessed 2026-10-14: Controlled archive ingest, immutable
+      snapshots, freshness and license review. Availability describes the delivery
+      form, not production acceptance. SBOM and license evidence do not prove vulnerability
+      exploitability or artifact trust.'
+external_evidence:
+  completeness:
+    level: C1
+    confidence: low
+    basis: Source artifacts establish a bounded capability; no independent consumer-completeness
+      assessment in this review.
+  reliability:
+    level: R0
+    confidence: low
+    basis: No longitudinal consumer reliability measurement established by this review.
+name: Dependency provenance and SBOM evidence
+summary: Controlled archive ingest, immutable snapshots, freshness and license review.
+tags:
+- security
+- netkingdom
+- framework-reuse
+discovery:
+  intent: Controlled archive ingest, immutable snapshots, freshness and license review
+  includes:
+  - Controlled archive ingest, immutable snapshots, freshness and license review
+  excludes:
+  - SBOM and license evidence do not prove vulnerability exploitability or artifact
+    trust
+  use_cases:
+  - 'U12: Developer builds and publishes through controlled source, dependency and
+    runner paths'
+  - 'U09: Maintainer observes posture, prioritizes findings, coordinates work and
+    verifies outcomes'
+availability:
+  current_level: A4
+  target_level: A4
+  current_artifacts:
+  - README.md
+  consumption_modes:
+  - HTTP API
+  - source
+relations:
+  related_to:
+  - capability.security.iam-tooling-suite
+evidence:
+  documentation:
+  - README.md
+consumer_guidance:
+  recommended_for:
+  - Developer builds and publishes through controlled source, dependency and runner
+    paths
+  - Maintainer observes posture, prioritizes findings, coordinates work and verifies
+    outcomes
+  not_recommended_for:
+  - SBOM and license evidence do not prove vulnerability exploitability or artifact
+    trust
+  known_limitations:
+  - SBOM and license evidence do not prove vulnerability exploitability or artifact
+    trust
+  - 2026-10-14 architecture review estimates operational maturity separately; a registry
+    entry does not authorize execution or establish deployment.
 ---
 
-# SBOM management
+# Dependency provenance and SBOM evidence
 
-Capture repository dependency evidence, preserve immutable SBOM snapshot
-history, query current inventory and licence signals, and select a deterministic
-bounded fleet catch-up queue.
+Controlled archive ingest, immutable snapshots, freshness and license review.
 
-The extraction interface is documented in `ProductRequirementsDocument.md`.
+## Reuse boundary
+
+SBOM and license evidence do not prove vulnerability exploitability or artifact trust.
+
+## Supported use cases
+
+- U12: Developer builds and publishes through controlled source, dependency and runner paths
+- U09: Maintainer observes posture, prioritizes findings, coordinates work and verifies outcomes
+
+## Evidence and integration
+
+- [README.md](../../README.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.
diff --git a/registry/indexes/capabilities.yaml b/registry/indexes/capabilities.yaml
index 60db680..d38f3ef 100644
--- a/registry/indexes/capabilities.yaml
+++ b/registry/indexes/capabilities.yaml
@@ -1,6 +1,21 @@
 schema: reuse-surface.capability-index.v1
 repo: sbom-nexus
 capabilities:
-  - id: capability.infotech.sbom-management
-    path: registry/capabilities/capability.infotech.sbom-management.md
-    status: emerging
+- id: capability.infotech.sbom-management
+  name: Dependency provenance and SBOM evidence
+  summary: Controlled archive ingest, immutable snapshots, freshness and license review.
+  domain: infotech
+  status: draft
+  owner: sbom-nexus
+  tags:
+  - security
+  - netkingdom
+  - framework-reuse
+  vector: D3 / A4 / C1 / R0
+  path: registry/capabilities/capability.infotech.sbom-management.md
+  consumption_modes:
+  - HTTP API
+  - source
+updated: '2026-10-14'
+version: 1
+domain: infotech