Appearance
Generated Evidence Catalog
This catalog makes coverage reviewable. CSV files retain one row per source artifact and can be filtered by the BA, QA, engineering, and handover teams.
| Evidence | Rows | Purpose |
|---|---|---|
| Backlog Register | 111 | Stable story IDs, epic, type, status, criteria count, questions, and Markdown source. |
| Endpoint Catalog | 1206 | HTTP verb, controller/action route, method, story mapping, and source line. |
| Application Artifact Catalog | 2986 | Commands, queries, validators, handlers, and supporting services mapped to stories/modules. |
| Integration Contract Catalog | 184 | Shared public APIs, DTOs, enums, and integration events mapped to their owning business area. |
| Frontend Route Catalog | 802 | MFE application route segment, component/lazy target, story mapping, and source line. |
Mapping interpretation
- Feature token match: artifact names overlap the owning feature vocabulary and are mapped to that story.
- Module-level supporting artifact: the artifact supports the module but is not safe to claim as a standalone user-facing feature without BA review.
- Generated mappings are a review aid, not proof that the business meaning is approved.
Current generated totals
- Stories: 111
- HTTP endpoints: 1206
- Application artifacts: 2986
- Public integration-contract artifacts: 184
- Frontend routes: 802