A source preview should help the user verify the answer without implying that a citation proves correctness. Show the supporting passage, relevant context, and source status under the same access rules as the document.
Previews expose the evidence boundary
A knowledge-assistant source preview displays the material used for a claim and enough surrounding context to interpret it. Useful elements include title, owner or source type, version or effective status, section or page location, and a controlled link.
For a proposed interface, connect each consequential claim to specific evidence rather than presenting a generic list of documents at the bottom. Preserve uncertainty when a source is incomplete, ambiguous, or unavailable.
Do not show private titles or snippets to unauthorised users. A preview is itself a disclosure, even if the full document requires login. Apply current resource permissions before rendering it.
Review a fictional policy answer
The assistant says a service option is available for product A. The preview highlights a general availability paragraph but omits the following exception for that product version. A user may trust the answer because the interface appears well cited.
The fixture should require the exception or an explicit context expansion. It should also check that the source actually supports the claimed product and condition, not merely contains similar words.
| Preview element | Verification purpose |
|---|---|
| Exact passage | Shows the claim’s actual basis |
| Heading path | Preserves topic and scope |
| Effective version | Indicates applicable policy context |
| Nearby condition or footnote | Prevents misleading fragments |
| Controlled source link | Enables authorised deeper review |
Ask users to verify correct and deliberately unsupported answers from the preview. Measure whether they can identify the mismatch rather than merely whether they like the visual design.
Handle stale and missing sources honestly
If a source changed after answer generation, show the defined version behaviour or re-evaluate the answer. If it expired or access was removed, do not leave a preview that implies the evidence remains available.
More context can improve verification while increasing clutter and disclosure risk. Use targeted expansion and clear source relationships. Keep the primary answer readable, but avoid reducing evidence to an uninformative document title that users cannot inspect.
This preview design is proposed. The voice integration case study describes related retrieval work without claiming this interface. Pair it with answer-to-passage tracing.
Source preview FAQ
Does a visible citation prove an answer is supported?
No. The cited passage must actually justify the claim under the correct scope.
Should previews include surrounding text?
Include the context necessary to understand conditions, with bounded expansion and permission checks.
What should happen after source access changes?
Apply the current policy to previews and links, and explain any resulting evidence limitation.