Skip to main content
Start with the result you need. These tools can support the same review, but they serve different purposes.

A practical review sequence

1

Orient with AI Guide

Open the project and choose Complete architecture tour. Identify the main resources, boundaries, and chapters with missing evidence.
2

Ask a specific follow-up in AI Chat

Select the relevant resources and ask, for example: “Which recorded relationships connect these resources, and what cannot be inferred from them?”
3

Check the report

Review the relevant cost or posture findings. Confirm that the report covers the same project source and that it is recent enough for your decision.
4

Verify before changing anything

Use the source template, cloud configuration, or operational evidence to check the recommendation. Record the next action and owner.

What kinds of comparisons can I make?

An ordinary AI Guide is a walkthrough of its loaded project context. It is not automatically a before/after review, a live traffic monitor, or proof that a recommended change has been applied. See Interfaces and workflows for release boundaries.

Example questions

  • AI Guide: “Help me understand the project boundaries and major resources.”
  • AI Chat: “What evidence supports this dependency, and which configuration should I inspect next?”
  • Reports: “Which findings are actionable for this source, and what evidence supports each one?”
Continue with AI Guide, Reports, or AI Guide troubleshooting.
Last modified on September 14, 2026