# Roadmap

Phase 1 is intentionally narrow: evidence retrieval, coverage-aware analysis, build briefs, Agent Skill, static API/site, and release automation. The items below are deferred until v0.1.0 is public and usable.

## Phase 2 — broaden evidence

- add robust keyword, npm, Hub, catalog, and community source adapters;
- track source-level freshness, parsing failures, and historical coverage;
- ingest external structural and runtime verification evidence without duplicating plugin checkers or compatibility radars.

## Phase 2 — capability graph and demand

- evolve flat tags into Need → Capability → DSH extension surface → Project → Evidence;
- use GitHub Issues as an initial public “Wanted / Needs” database;
- add a transparent opportunity score with visible components, not fake precision.

## Phase 2 — history and semantics

- publish periodic ecosystem changes and filled-gap history;
- evaluate local rerankers/embeddings and additional provider adapters while preserving keyless deterministic search;
- cache inferred enrichment with model/version provenance and reviewed overrides.

## Phase 2 — distribution

- consider an MCP server and hosted API only after Skill/CLI demand is demonstrated;
- submit the project to suitable DSH catalogs and Skills discovery surfaces;
- expand the website with capability maps, compare views, and historical trends.

No invasive telemetry is planned. Phase 2 must not weaken source provenance or turn incomplete discovery into a GAP claim.