Architect

What Architect does

Architect provides proactive engineering intelligence built on the Software Graph. Instead of waiting for problems to surface in code review, Architect detects trends, tracks health over time, simulates migrations, and surfaces what needs attention — backed by deterministic evidence.

Health timeline

Every build produces a health snapshot — readiness score, grades, finding counts, ownership coverage. Architect plots these over time so you can see whether your codebase is improving or drifting. Spot regressions before they compound.

Trend detection

Architect watches for structural trends across builds and surfaces them proactively.

• Coupling trends — modules growing more interdependent
• Dead code growth — unused exports accumulating
• Cycle formation — new dependency cycles appearing
• Ownership erosion — unowned modules increasing
• Architecture drift — grades declining over time
• Dependency churn — frequent dependency changes

Monday morning briefing

A weekly summary of what changed, what improved, what drifted, and what needs attention. Generated from the health timeline and trend data. Designed to replace the question: "what happened to the codebase this week?"

Migration simulator

Plan large refactors before executing them. The simulator takes a proposed change (rename, move, split, extract) and computes the blast radius preview — every module, service, route, and test that would be affected. Make informed decisions about scope before writing code.

AI chat with evidence

Ask questions about your codebase in natural language. Architect answers using bounded evidence packs from the graph — not raw repository dumps. The AI explains; the graph proves. Every answer cites specific nodes and relationships as evidence.