Search docs
Docs searchFindings & Exceptions
Findings & Exceptions
Use ArchPilot Cloud to review findings across repositories, track lifecycle state, and handle exceptions while preserving architecture governance visibility.
Cloud turns local findings into a shared governance workflow so teams can review, triage, and manage architecture issues across repositories at organization scale.
Plan availability
Findings stay visible across plans. Exception management is Team and above, and Findings Intelligence is Growth and above.
Findings visibility
Review architecture findings and repository posture from Cloud snapshots.
Exception management
List, create, update, and revoke repository exceptions as part of shared governance review.
Findings Intelligence
Review highest-impact, recurring, team, and system patterns alongside the standard findings list.
What Cloud adds to findings
The standard findings list remains the starting point. It shows findings, lifecycle state, severity, repository context, and finding details across plans.
Findings Intelligence adds Growth and above views for organization-level patterns.
- Organization-wide findings visibility
- Repository-specific finding detail views
- Component filters when findings include component context
- Resource filters when findings include resource context
- Lifecycle state over time
- Exception-aware operational posture
Basic Findings vs Findings Intelligence
| Area | Available on | Use it for |
|---|---|---|
| Basic Findings | All plans | Review findings, severity, status, repository context, lifecycle state, and finding detail pages. |
| Exception management | Team and above | Acknowledge approved risk while keeping the original finding visible. |
| Findings Intelligence | Growth and above | Find highest-impact, recurring, team, and system patterns across the organization. |
How findings relate to components
Cloud uses component and resource context from findings when it is present. Repository-level findings continue to work without component or resource context.
Components identify logical architecture units such as apps, services, libraries, workers, and infrastructure packages. Resources identify impacted APIs, databases, queues, storage services, or infrastructure dependencies. Modules remain code-level groupings reported by validation rules.
Finding categories
Findings can represent architecture violations, setup gaps, or guidance. Cloud displays those categories from the local result.
This keeps bootstrap readiness problems separate from architecture rule breaches while still making both visible in shared review.
Rule and validation categories
Cloud finding rows keep the rule ID, rule title, source category, severity, and lifecycle state from local validation. The public Rule Catalog and Cloud category pages explain the same implemented rules with example violations and remediation guidance.
Use the category pages for Application Layering, Authorization, Tenant Isolation, Transaction Boundaries, Domain Model Quality, API Design, Data / Query Risk, and Event Architecture when a finding belongs to one of the newer implemented rule families.
How exceptions fit in Cloud
Exceptions let teams acknowledge a rule issue intentionally while keeping the raw finding history intact.
That gives Cloud an operational posture view without pretending the original architecture issue never existed.
Why shared review helps
Teams can see recurring issues across repositories, understand where posture is being changed by approved exceptions, and review architecture governance in a shared workspace rather than a single local report.