Search docs
Docs searchDrift & History
Drift, Baselines & History
ArchPilot tracks architecture drift detection, local history, and baseline comparisons so teams can see whether architecture quality is improving, stable, or regressing.
Why it matters
These features turn architecture validation into a time-based workflow instead of a one-off pass, which helps teams understand trend direction and baseline regression.
What ArchPilot records over time
- Minimal validation snapshots
- Architecture score and readiness trends
- Drift events between runs
- Baseline comparison results
- History views that summarize whether architecture is improving or regressing
Why this matters
Architecture drift detection is most useful when it is not purely anecdotal. History and baselines give teams a concrete way to discuss whether architecture is actually becoming healthier or just producing different findings.
That is valuable for local validation, CI architecture validation, and organization governance when you later add ArchPilot Cloud.
A practical baseline workflow
- Run validation until the current state is acceptable enough to use as a reference point.
- Create or refresh a baseline for the current architecture state.
- Compare later validation runs against that baseline to spot regressions.
- Use the local history view to see whether the architecture trend is improving, stable, or declining.