Priority Map
A data-driven view of the audit's 123 findings: clusters, 3-tier sprint allocation, and an effort gauge. Built from the structured cross-reference graph and the launch-priority field on each finding. Sprint assignment uses the simplest data-driven mapping (priority tier → sprint); refine by hand for client-specific timelines.
Top-line gauge
Effort distribution by launch priority — segments are width-proportional to engineer-days.
Effort heuristic: S = 1 day, M = 3 days, L = 10 days. These are coarse estimates aggregated across all launch-blocking findings; per-cluster execution may compress through parallelism. Use the cluster overview below to identify parallel tracks.
Cluster overview
Findings are interconnected. Resolving the gap underlying a cluster closes multiple findings at once — these are the highest-leverage targets.
Sprint kanban
Three columns, three tiers. Each tier maps directly from priority_for_launch on the finding — no hand-curation required.