Quick Fixes, Exceptions & Suppressions

ArchPilot helps teams respond to architecture findings with fix suggestions, explicit exceptions, and suppression-aware governance rather than ad hoc ignore patterns.

Why it matters

Use these workflows when a finding needs a fast local fix, a time-bound exception, or a documented suppression strategy that still keeps governance visible.

Quick fixes

ArchPilot can surface suggested follow-up actions for some findings so users can move from architecture validation output to a practical next step faster.

This is useful for common bootstrap or structure problems that do not need a custom remediation plan.

Exceptions and suppressions are not the same thing

A suppression hides or softens a local finding in a validation context. An exception is a more deliberate governance choice that records that a rule is being relaxed for a reason.

Treating them differently helps teams avoid turning architecture policy enforcement into a hidden ignore list.

When teams use them well

When a violation is known and temporary
When a dependency or architecture policy needs a controlled exception
When teams want to preserve architecture review history instead of pretending the issue never existed

Dependency Rules & Module Contracts Policy & ADR Workflows Findings & Exceptions

Next steps

Governance Upload CLI Command Reference