Search docs
Docs searchInspector
Architecture Inspector
The Architecture Inspector gives ArchPilot users an in-editor workspace for initialization, validation context, findings, maps, and local history.
Why it matters
Use the inspector when you want architecture validation feedback in VS Code without switching constantly between the terminal, reports, and project files.
What the inspector is for
- Initialization and Smart Init review
- Validation results and finding details
- Architecture maps and context views
- History and trend review
- Cloud connection guidance for governance upload
How it fits into daily work
The inspector is not a separate product flow. It is a user-facing view over the same local ArchPilot artifacts that the CLI uses.
That means architecture validation, review generation, and governance upload stay consistent whether you trigger them from the extension or from command-line workflows.
When teams rely on the inspector most
- During first-time rollout, when repository structure and findings need extra review
- When developers want fix suggestions and rule explanations close to the code
- When teams want a visual history of architecture drift, scores, and enforcement changes over time