Use the tool as a translator between customer conversation, business function, and delivery: first clarify which decision should become safer, then capture only the information needed for owner, scope, evidence, review, or handoff.

1. For sales / non-technical users: no governance lecture required. Capture in customer language what is slow, risky, expensive, unclear, or hard to evidence.
2. For tech / delivery: use the report as context and boundary, not as finished architecture. Open assumptions stay visible until owner and review confirm them.
3. Do not use it as a tool shortcut: catalog, BI, dbt, IAM, or platform come only after problem, function, owner, and first evidence slice are clear.
4. The result view is the reviewable handoff block. Copy it, download Markdown, save it, or write it back directly when you came from a plan.