From a question to its evidence
One reference flow begins when a business application receives a question. Identity and authorization determine scope, planning selects a query or retrieval, connectors read the approved material, and validation organizes the answer and its sources. These responsibilities can be implemented by different components in different deployments.
Structured queries and knowledge retrieval can work together. A database supplies records from a particular snapshot, while documents explain rules and context. Preserve the provenance and date of each when combining them.
Assign responsibility at each layer
| Logical layer | What to evaluate |
|---|---|
| Entry point | Identity, session, cancellation and error feedback |
| Task planning | Business meaning, context and available tools |
| Semantics and knowledge | Metric definitions, document versions and citations |
| Execution and connectors | Read-only scope, query limits and failure states |
| Results and delivery | Answers, charts, files and access control |
Map where information actually travels
Mark question text, query results, document excerpts, credentials, caches, logs and backups on the deployment diagram. Add the location of inference and required external connections. Together, these flows show where processing takes place and which network or organizational boundaries it crosses.
Validate the diagram with one execution
- Ask for last month’s sales as a regional manager. Note which regions you can see, the reporting period and how sales are defined.
- Use the run history to find the order records behind the answer. If a result was reused, check its period before requesting a fresh query.
- Make a test reference unavailable and ask again. Check whether the answer identifies the missing evidence.
- Test retrying and cancelling a query, and exporting its results. Check that each action respects that user’s permissions.
