The problem
A verdict is more useful when you can see how it was reached.
A bare "blocked" tells you the outcome. What a reviewer, an engineer, or an auditor needs is the reasoning behind it — which independent critic decided what, how the findings aggregated, and exactly where each one points.
The dashboard puts that trail in one place: the same decision the gate posted on the pull request, laid out so a person can follow it.
How it works
The decision trail, opened up.
Every verdict decomposes into its independent critics — how each one decided, how many findings it raised, and how those findings aggregated into the final verdict. Each finding carries a severity, a category, and a location, grouped by the critic that raised it, with deep links back to the pull request and the check run.
It reads across your repositories, so the whole quality trail is one view — auditable end to end. Findings surface severity, category, and location, while your source stays inside your perimeter.
- Per-critic decomposition — how each independent reviewer decided, and how many findings it raised
- Aggregate reasoning — how independent findings became one verdict
- Structured findings by severity, category, and file — grouped by the critic that raised them
- Deep links to the pull request and the check run
- The full trail per commit and across your repositories, auditable end to end
See how your gate decides.
The dashboard surfaces the reasoning behind every verdict across your repositories — what each critic decided, why, and where.