Put the result inside the reply.
When someone asks a question, the first thing they need is an answer in context. A chart that appears elsewhere on the page makes the connection harder to follow. Keep the explanation, visual result and source links together in the same reply.
In a supplier example, a short sentence can state which definition was used before a table lists the matching orders. A total then has a clear meaning and a visible boundary.
Use progressive detail, not hidden evidence.
A source list can begin with record identifiers and a short explanation of relevance. Selecting a reference would reveal its original fields or passage. This keeps the first answer readable while leaving the supporting detail within reach.
If an answer depends on a date filter or deduplication rule, show that definition beside the result. It should not require opening a separate technical manual to understand what was counted.
Make an unavailable source visible.
When a source cannot be reached, retain the question and say which part of the answer cannot be checked. Offer a retry only when retrying is supported. Avoid replacing missing data with a polished but unsupported certainty.
These are proposed interaction patterns. Live retrieval, persistent history and feedback submission remain coming-soon capabilities in this website preview.