Architecture Intelligence for the AI-Development Era

Abstract

AI coding agents now generate the majority of code on fast-moving teams — faster than any human architect can review, document, or govern. The discipline that kept systems intentional (upfront design, hand-written ADRs, periodic diagrams) assumes a human authoring pace that no longer exists.

ArchSteer proposes a different model: the system authors architecture artifacts continuously from code, and the architect curates them. This inverts authorship and makes architecture continuously observable, governable, and auditable.

1. The shift: docs are agent infrastructure

Persistent design context — a current architecture map plus decision rationale — is the primary lever against agent context degradation, the mechanism behind structural “slop.” An agent scanning a half-migrated repo will replicate the dominant local pattern, because that is the strongest signal in its context.

Documentation has therefore stopped being human paperwork and become critical infrastructure that AI agents consume. If it is stale, agents are steered wrong by default.

2. The core principle: invert authorship

Authored artifacts are always behind reality; emitted artifacts are reality. ArchSteer derives a single typed model from source and treats every downstream artifact — diagrams, ADRs, conformance reports, the evolution feed — as a projection of it.

The architect’s role changes from author to editor-in-chief: they ratify decisions the system surfaces and declare the invariants they care about, rather than maintaining documents by hand.

3. Two planes: descriptive and prescriptive

To be a must-have for every enterprise — not only those mid-migration — ArchSteer separates two planes. The reality plane is descriptive and needs zero setup: it answers “what is our architecture, and how did it change?” This is universal, because nobody knows their real architecture anymore.

The intent plane is prescriptive and opt-in: the architect declares targets and ArchSteer enforces them and steers agents toward them. Observability is the vitamin everyone takes; governance is the painkiller they pay for.

4. The four jobs

See how you’re evolving. Architecture gets a changelog (a git-log of structural change) and a Drift Index — a single number that goes on the weekly engineering review. Metrics leadership watches create budget and permanence.

Set architecture when needed. Intent is declarative, partial, and just-in-time. Govern one rule today; the system infers the rest. Low activation energy beats big-bang modeling.

Auto-built documentation. Always-live C4 and dependency maps and a component catalog, regenerated every run. The architect never writes them.

Every decision as an ADR. Agents make architectural decisions implicitly — a new dependency, a new datastore, a new boundary. ArchSteer surfaces each boundary-altering change as a prefilled draft ADR for ratification. “No architectural change without a decision record” is a governance mandate a Chief Architect can impose org-wide — and the provenance trail satisfies audit and compliance.

5. Why this is a category, not a feature

Adjacent tools each own one slice: migration-recipe engines, single-language architecture linters, manual C4 diagram tools, behavioral code-health platforms, and AI code reviewers. None fuse a live code-derived model with auto-built ADRs, a net-new conformance ratchet, an evolution timeline, and AI-agent steering — local-first and language-agnostic.

That fusion is Architecture Intelligence: observability + governance + decision provenance for the AI era.

6. Go-to-market

Land with a free, read-only X-ray: run it on one repo, see current state plus recent evolution plus drafted ADRs. Expand to governance priced per repo and per architect seat: CI gating, agent steering, multi-repo rollups, and the executive Drift Index dashboard.

Lock-in follows naturally — ArchSteer becomes both the source of truth and the decision ledger, and removing it means going blind and losing the audit trail.

7. The must-have test

The bar a principal architect applies: would the Chief Architect feel exposed at a board or audit review without it? Slides and wikis fail that test. An always-current, code-derived system of architectural state and decisions passes it.