Automated architecture decision records, ratified by the architect
A new dependency, datastore, or boundary is a genuine decision — usually recorded nowhere. ArchSteer drafts an ADR for each, with context and blast radius, ready for the architect to ratify.
Conservative by design
Only external-boundary changes trigger a draft. Internal reshuffles and file splits produce nothing, so you're never buried in noise.
Architect-in-the-loop
ArchSteer drafts; it never auto-commits a decision. You ratify, edit, or reject.
An auditable ledger
The result is a continuously maintained decision trail — the provenance auditors and compliance reviews ask for.
Try it on your repo
Run `archsteer xray` on your repo to see this in under a minute, then declare intent when you're ready to govern.
FAQ
What counts as a decision worth an ADR?
A new third-party dependency, a new persistence entity, or a newly introduced architectural layer — the changes that move boundaries.
Are ADRs committed automatically?
No. Drafts are written for review; ratification is always a human step.
Related
AI agent guardrails that keep coding agents on-architecture
Stop AI coding agents replicating legacy patterns. ArchSteer injects file-scoped, ADR-back…
Architecture drift detection with a Drift Index leadership can watch
Detect and trend architectural drift continuously. ArchSteer turns every code change into …
Living architecture documentation that never goes stale
Stop hand-maintaining diagrams and system maps. ArchSteer regenerates living architecture …
Enterprise architecture governance across every repository
Govern architecture org-wide while agents move fast. ArchSteer's situation room shows conf…