Search docs
Docs searchFindings & Exceptions
Findings & Exceptions
Use ArchPilot Cloud to review findings across repositories, track lifecycle state, and handle exceptions without losing 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 workflows are governed as a Team-and-above Cloud workflow.
Findings visibility
Review uploaded architecture findings and repository posture from Cloud snapshots.
Exception workflows
List, create, update, and revoke repository exceptions as part of shared governance review.
What Cloud adds to findings
- Organization-wide findings visibility
- Repository-specific finding detail views
- Component filters when uploaded findings include component metadata
- Resource filters when uploaded findings include resource metadata
- Lifecycle state over time
- Exception-aware operational posture
How findings relate to components
Cloud uses component metadata from uploaded findings when it is present. Older uploads and repo-level findings continue to work without component data.
The componentId field and component name identify the logical component; resourceId and resource name identify an impacted API, database, queue, storage service, or infrastructure dependency when provided. Module remains the code-level grouping reported by the validation rule.
Finding categories
Uploaded findings can represent architecture violations, setup gaps, or guidance. Cloud stores and displays those categories from the local result instead of deciding them during upload.
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 uploaded 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 this is better than local-only issue tracking
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.