Policy & ADR Workflows

ArchPilot adds a policy layer on top of architecture validation so teams can map risk to enforcement outcomes and use ADR workflows when structural change needs documentation.

Why it matters

Policy turns architecture validation into a governed workflow. ADR guidance helps teams explain intentional structural changes instead of treating every issue as a pure code problem.

What policy controls

When architecture outcomes stay advisory
When they should warn
When they should require an ADR
When CI should fail because the architecture state crosses the configured threshold

How ArchPilot thinks about enforcement

Architecture validation and policy are related but not identical. Validation produces findings and risk. Policy interprets that result and maps it to an enforcement decision.

This keeps architecture policy enforcement explainable. Teams can see both the underlying findings and the reason ArchPilot escalated the workflow.

Where ADR workflow fits

Some structural changes are intentional and worth documenting rather than simply suppressing. ArchPilot can guide users toward an ADR workflow when the policy outcome indicates that an architectural decision should be recorded.

This is especially useful for architecture as code programs that want change history, not just pass or fail output.

Dependency Rules & Module Contracts GitHub CI Integration Policies & Governance

Next steps

Drift, Baselines & History GitHub CI Integration