repo-scoping/registry/capabilities/capability.agents.repo-scoping-service.md

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance, promotion_history

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.agents.repo-scoping-service	Repository Scoping Service	Maps repositories from usefulness to implementation (Ability -> Capability -> Feature -> Evidence -> Code location) via a Python registry core, FastAPI HTTP API, and curator UI.	repo-scoping	draft	agents	classification scoping registry	discovery availability current target confidence rationale D2 D4 medium 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. current target confidence rationale A2 A3 medium Installable Python package with a FastAPI HTTP API and curator UI; local development documented via venv + pip install -e.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C1 low scope_vs_intent_and_consumer_expectations repo registration importing basic metadata analysis building observed facts and candidate review entries level confidence basis known_reliability_risks R0 low consumer_quality_signals curator UI and analysis pipeline maturity not independently verified in this sweep	intent includes excludes assumptions use_cases research_memos 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. repository registration and metadata import observed-fact analysis and candidate review entries FastAPI HTTP API and curator UI the capability registry itself (see reuse-surface, a related but distinct concern)	current_level target_level current_artifacts target_artifacts consumption_modes A2 A3 Python package with FastAPI HTTP API curator UI http api library import ui	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents README.md tests/	recommended_for not_recommended_for known_limitations teams wanting a structured ability-to-code-location mapping and curation workflow for repos needs already served by reuse-surface's capability registry (related but distinct concern — worth comparing scope before adopting both) curator UI and analysis pipeline maturity not independently verified in this sweep

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

• ID follows capability.<domain>.<name> pattern
• Maturity enums match specs/CapabilityMaturityStandard.md
• external_evidence is populated separately from maturity
• Relations reference valid capability IDs (none yet)
• Index entry added in registry/indexes/capabilities.yaml