diff --git a/registry/capabilities/capability.agents.repo-scoping-service.md b/registry/capabilities/capability.agents.repo-scoping-service.md
new file mode 100644
index 0000000..04ba944
--- /dev/null
+++ b/registry/capabilities/capability.agents.repo-scoping-service.md
@@ -0,0 +1,122 @@
+---
+id: capability.agents.repo-scoping-service
+name: Repository Scoping Service
+summary: Maps repositories from usefulness to implementation (Ability -> Capability -> Feature -> Evidence
+  -> Code location) via a Python registry core, FastAPI HTTP API, and curator UI.
+owner: repo-scoping
+status: draft
+domain: agents
+tags:
+- classification
+- scoping
+- registry
+maturity:
+  discovery:
+    current: D2
+    target: D4
+    confidence: medium
+    rationale: README documents the Ability->Capability->Feature->Evidence->Code-location mapping model
+      and the three-part implementation (registry core, FastAPI HTTP API, curator UI); no separate INTENT/SCOPE
+      with deeper detail found in this sweep.
+  availability:
+    current: A2
+    target: A3
+    confidence: medium
+    rationale: Installable Python package with a FastAPI HTTP API and curator UI; local development documented
+      via venv + pip install -e.
+external_evidence:
+  completeness:
+    level: C1
+    confidence: low
+    basis: scope_vs_intent_and_consumer_expectations
+    satisfied_expectations:
+    - repo registration importing basic metadata
+    - analysis building observed facts and candidate review entries
+    broken_expectations: []
+    out_of_scope_expectations: []
+  reliability:
+    level: R0
+    confidence: low
+    basis: consumer_quality_signals
+    known_reliability_risks:
+    - curator UI and analysis pipeline maturity not independently verified in this sweep
+discovery:
+  intent: Give the ecosystem a structured way to map repositories from raw usefulness down to concrete
+    code locations, via an explicit ability/capability/feature/evidence chain.
+  includes:
+  - repository registration and metadata import
+  - observed-fact analysis and candidate review entries
+  - FastAPI HTTP API and curator UI
+  excludes:
+  - the capability registry itself (see reuse-surface, a related but distinct concern)
+  assumptions: []
+  use_cases: []
+  research_memos: []
+availability:
+  current_level: A2
+  target_level: A3
+  current_artifacts:
+  - Python package with FastAPI HTTP API
+  - curator UI
+  target_artifacts: []
+  consumption_modes:
+  - http api
+  - library import
+  - ui
+relations:
+  depends_on: []
+  supports: []
+  related_to: []
+evidence:
+  documentation:
+  - README.md
+  tests:
+  - tests/
+  consumer_feedback: []
+  bug_reports: []
+  incidents: []
+consumer_guidance:
+  recommended_for:
+  - teams wanting a structured ability-to-code-location mapping and curation workflow for repos
+  not_recommended_for:
+  - needs already served by reuse-surface's capability registry (related but distinct concern — worth
+    comparing scope before adopting both)
+  known_limitations:
+  - curator UI and analysis pipeline maturity not independently verified in this sweep
+promotion_history: []
+---
+
+# Repository Scoping Service
+
+## Overview
+
+`repo-scoping` maps repositories from usefulness to implementation along an Ability -> Capability -> Feature -> Evidence -> Code-location chain, via a Python registry core, a FastAPI HTTP API, and a small curator UI for reviewing candidate entries.
+
+## Assessment notes
+
+### Discovery
+
+README documents the Ability->Capability->Feature->Evidence->Code-location mapping model and the three-part implementation (registry core, FastAPI HTTP API, curator UI); no separate INTENT/SCOPE with deeper detail found in this sweep.
+
+### Availability
+
+Installable Python package with a FastAPI HTTP API and curator UI; local development documented via venv + pip install -e.
+
+### 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.<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] Index entry added in `registry/indexes/capabilities.yaml`
diff --git a/registry/indexes/capabilities.yaml b/registry/indexes/capabilities.yaml
index f944e47..c29df14 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.agents.repo-scoping-service
+  name: Repository Scoping Service
+  summary: Maps repositories from usefulness to implementation (Ability -> Capability -> Feature -> Evidence
+    -> Code location) via a Python registry core, FastAPI HTTP API, and curator UI.
+  vector: D2 / A2 / C1 / R0
+  domain: agents
+  status: draft
+  owner: repo-scoping
+  path: registry/capabilities/capability.agents.repo-scoping-service.md
+  tags:
+  - classification
+  - scoping
+  - registry
+  consumption_modes:
+  - http api
+  - library import
+  - ui