Search docs
Docs searchFindings Intelligence
Findings Intelligence
Use Findings Intelligence to understand highest-impact, recurring, team, and system-level finding patterns across the organization.
Findings Intelligence helps Growth and above teams prioritize architecture findings across repositories while keeping the standard findings list available for detail review.
Plan availability
Basic findings remain available on every plan. Findings Intelligence is available on Growth and above.
Basic findings
Review findings, repository context, severity, status, lifecycle state, and finding detail views.
Findings Intelligence
Use Highest impact, Recurring, By team, and By system views to understand organization-level finding patterns.
What Findings Intelligence is for
The standard findings list is for concrete finding review. Findings Intelligence is for organization-level patterns: highest impact, recurrence, team ownership, and system ownership.
Highest impact findings
Highest impact findings help teams review the strongest governance signals first.
- Open or severe findings that need attention.
- Findings connected to repositories or systems with stronger risk signals.
- Patterns that are more useful to investigate than a simple chronological list.
Recurring findings
Recurring findings surface repeated architecture issues across repositories. Use this view to decide whether the response should be a local fix, shared refactor, or team guidance.
By team
The By team view groups finding patterns by team ownership when that metadata exists, so follow-up can happen with the teams closest to the affected repositories.
By system
The By system view groups patterns by system ownership when one product, platform boundary, or operational system has findings spread across repositories.
How to use it with the standard findings list
- Start with the standard findings list when you need concrete finding details.
- Use Highest impact when the list is too large and the team needs a first review order.
- Use Recurring when similar findings appear across multiple repositories.
- Use By team or By system when ownership context is needed for follow-up.
- Return to the standard finding detail page when you need lifecycle state, repository context, or rule guidance.