Skip to main content
Use results as decision evidence, not as an unexplained score. Start with the report or diagram, then inspect the supporting source, freshness, and coverage.

Diagrams

Read architecture and dependency views without assuming missing relationships are absent in reality.

Reports

Interpret briefs, action plans, posture, cost, security, resources, and evidence.

Sharing and collaboration

Share read-only results and distinguish active sharing from collaboration previews.

Review findings

Trace a recommendation back to its evidence and applicability boundary.

​
A trustworthy reading order

  1. Confirm the source, ref, commit, or cloud-sync timestamp.
  2. Check coverage and Not assessed areas.
  3. Inspect high-priority findings and their evidence.
  4. Compare diagrams and cost outputs with known architecture intent.
  5. Record the decision, owner, and next verification step.
Last modified on September 1, 2026