Your agents ship faster than you can govern.
ArchSteer is the always-current system of record for how your software evolves. It derives your real architecture from code, auto-builds living docs and ADRs, tracks your drift, and steers AI agents to conform — instead of replicating legacy slop.
See your architecture. Govern your agents. Capture every decision.
$ archsteer xray # zero-config, no rules required ✓ X-ray of billing-api: 142 components, 5 layers. 3 architectural change(s) since the last snapshot. → .archsteer/architecture.md and report.html $ archsteer evolution Architecture Evolution — 3 change(s) this week. ✓ Conformance 64% → 71% (+7 pts) ✗ New dependency: stripe • +4 components (142 total)
Documentation is no longer paperwork. It's agent infrastructure.
When AI agents write most of the code, four failures compound — fast:
📉 Docs rot instantly
ADRs and system maps are stale the moment a feature ships. Nobody trusts the wiki.
🌫️ The real architecture is invisible
You can't read every PR. Nobody — least of all the architect — knows the current shape of the system.
🤫 Decisions are made silently
An agent adds a datastore, an external call, a new boundary. A genuine decision — recorded nowhere.
🌀 Drift is unbounded
With no continuous conformance, every edit quietly erodes intent. Migrations never converge.
One idea: invert authorship
Today humans author docs, diagrams, and ADRs — so they rot the instant an agent ships code. ArchSteer makes the system author them continuously and the architect curate. The architect's job shifts from writing the map to ratifying what the map already shows.
See what your architecture is
Point ArchSteer at any repo. Get the current map, a component catalog, an evolution feed, and auto-drafted ADRs of what structurally changed — with no rules to declare.
- Universal: every enterprise wants to see its own system
- The free wedge — instant “I didn't know we had that”
Declare what you want
Govern one invariant you care about today — not the whole system. ArchSteer enforces it in CI, tracks drift, and steers agents toward it.
- Incremental: govern a single rule, not boil the ocean
- The expansion — conformance, steering, the exec drift dashboard
Five pillars. One model.
Everything is a pure projection of one code-derived model.json — which is what keeps a broad product coherent.
archsteer map① Map
Derive the real architecture from source — components, layers, dependencies, data access, external calls.
archsteer docs② Document
Living docs + Mermaid C4/dependency diagrams, regenerated deterministically. Never authored by hand.
archsteer govern③ Govern
Fitness functions with a net-new ratchet: block regressions, never freeze features for existing debt.
archsteer steer④ Steer
Sharp, file-scoped guardrails injected into CLAUDE.md / AGENTS.md so agents conform to the target.
archsteer adr⑤ Decide
Boundary-altering changes surface as prefilled draft ADRs for ratification. No change without a record.
archsteer evolution＋ Evolve
A git-log for your architecture and a Drift Index leadership can watch trend over time.
Roadmap
get_target_pattern, check_file, current_architecture).Get started in 30 seconds
$ pip install archsteer $ cd your-repo $ archsteer xray # map + docs + evolution, no config # then, when ready to govern: $ archsteer init && archsteer steer && archsteer check