Coverage Methodology

Sources inspected

• MFE route definitions, page components, forms, action handlers, permissions, and services.
• API controllers, routes, action policies, request/response contracts, localization keys, seed menus, and system features.
• Application commands, queries, validators, handlers, managers, domain services, and public APIs.
• Domain entities, state methods, enums, persistence mappings, reports, integration events, and available tests.

What code can prove

Code can prove current implemented fields, validations, state checks, account resolution, journals, linked records, permissions, and error paths. It cannot prove that current behavior matches intended policy, undocumented manual operations, external procedures, or planned functionality.

Completeness controls

• Every controller is mapped in AppsPortal/Source-Coverage.md.
• Every endpoint is listed in Evidence/Endpoint-Catalog.csv.
• Commands, queries, validators, handlers, and domain support are listed in Evidence/Application-Artifact-Catalog.csv.
• Public integration contracts are listed in Evidence/Integration-Contract-Catalog.csv.
• MFE routes are listed in Evidence/Frontend-Route-Catalog.csv.
• Every business feature has a stable Story ID and appears in BACKLOG.md.
• Uncertain intent remains an explicit question; it is not silently converted into a rule.

Change-control expectation

Regenerate evidence and rerun coverage audits whenever routes, controllers, commands, validators, enums, integrations, or posting services change. A story is stale when its last source review predates a relevant source change.