| UI or UX | UI + UX - Calibrated reliability and uncertainty display for AI or automated predictions before user action | UI + UX - Whole-answer source coverage and grounding evidence display | UI + UX - Inline claim-to-source evidence display for generated or summarized content | UI + UX - Read-only scalar value gauge within a known range | UI + UX - Severe-consequence warning copy before an action |
| UI guidance | Render confidence and uncertainty as labelled reliability information with confidence band, reason, input scope, calibration status, review threshold, freshness, and the next safe action. | Render source grounding as an answer-wide evidence panel that separates source scope, searched sources, retrieved sources, used sources, supported claims, partially supported claims, unsupported claims, and unresolved source states. | Render citation markers beside the claims they support, and connect each marker to a selected source preview with title, source type, excerpt, date or version, permission state, and open source action. | Use native meter semantics or equivalent read-only meter attributes, and pair color bands with text such as Healthy, Warning, Critical, Low, Normal, High, or Over limit. | Render warning text as a short high-emphasis statement with a warning icon, visible or hidden warning label, and explicit consequence copy placed before the relevant action, declaration, or instruction. |
| UX guidance | Use confidence / uncertainty display when users need to decide whether an AI prediction, classification, recommendation, extraction, risk assessment, or generated answer is reliable enough to apply. | Let users inspect coverage gaps, source scope, retrieval status, and unsupported claims before they copy, publish, apply, or rely on the answer. | Keep the claim-to-source mapping durable through streaming, regeneration, copying, mobile layout changes, and permission checks so users can tell what evidence applies to which claim. | Explain whether higher, lower, or middle values are better, what threshold the current value crosses, and what action is available when the meter enters a warning or critical range. | Use warning text when users must understand a serious consequence before acting or failing to act, such as a fine, loss of access, permanent deletion, eligibility impact, or legal responsibility. |
| Good UI | A claim classifier says Medium confidence, 71 to 78 percent calibrated range, review threshold 80 percent, conflicting account-age signal, and routes the case to manual review. | A policy answer includes a Grounding panel showing 4 sources searched, 3 retrieved, 2 used, 5 supported claims, 1 partially supported claim, and 1 unsupported claim with a Review action. | A policy assistant places numbered citation chips after each sourced claim; selecting a chip opens a source preview with the document title, section, quoted excerpt, updated date, and Open source action. | An account storage card says 86 GB of 100 GB used, marks 70 GB as warning and 90 GB as critical, and labels the current state Critical. | Before Submit declaration, a warning with an exclamation icon says the user may be fined if they provide false information. |
| Bad UI | Users over-trust an AI answer because a confidence badge looks authoritative. | The answer shows a green Grounded badge even though only one citation supports one paragraph. | A citation appears verified while retrieval is still pending. | A progress bar for uploading evidence.zip is implemented as a meter, so task completion and capacity status are confused. | A red sentence says Important below the submit button after the user has already acted. |
| Good UX | A reviewer sees low confidence and out-of-distribution input, opens the reason panel, collects the missing invoice, and avoids auto-denying the claim. | The person reaches the intended result with clear feedback. | A user checks a claim, opens its source preview, compares the quoted excerpt with the answer text, and copies the citation with the source title included. | A user sees storage at 86 of 100 GB, understands the account is in the critical band, opens Manage storage, and deletes old exports before uploads are blocked. | Users see the fine or eligibility consequence before checking the declaration and can pause to verify their answer. |
| Bad UX | A model update invalidates old confidence scores but the UI keeps showing them as current. | Grounded status is shown before retrieval finishes. | A user trusts a generated compliance claim because it has a number beside it, but the number points to an unrelated source. | Users mistake quota level for upload completion because the meter animates like progress. | Users incur a penalty because the warning looked like ordinary hint text. |
| Best fit | Users must judge whether an AI prediction, classification, recommendation, extraction, risk score, or generated answer is reliable enough to use. | Users need answer-wide evidence coverage before trusting generated content. | Users need to verify generated claims, summaries, recommendations, or extracted facts against source material. | A current value exists inside a meaningful known range. | A user must understand a serious consequence before taking or skipping an action. |
| Avoid when | Users only need source coverage or claim evidence, which belongs to source grounding display or citation display. | The only task is opening one claim's source preview, which belongs to citation display. | Links are simply optional onward reading rather than evidence for the answer. | The value represents task completion or loading progress. | The message is a dynamic task status that must be announced when it appears. |
| Required state | High confidence state with calibration scope, reason, and whether direct apply is allowed. | Default grounded state with source scope, searched sources, retrieved sources, used sources, and supported-claim count. | Default answer with cited claims and inline citation markers. | Normal state inside the acceptable band. | Before-action warning state placed immediately before the related control or declaration. |
| Accessibility burden | Expose confidence label, uncertainty reason, threshold, freshness, and gated action as text rather than relying on color, position, or animation alone. | Expose grounding summary, source scope, status counts, unsupported claims, and source groups as text. | Give citation markers accessible names that include their selected state and source status, such as Citation 2, verified source, or Citation pending. | Prefer the native meter element where possible because it carries the correct read-only meter semantics. | Keep the warning in reading order before the control, declaration, or instruction it qualifies. |
| Common misuse | Showing a fake percent or exact decimal for an uncalibrated model score. | Showing a global Grounded badge when only some claims have evidence. | Displaying a link dump below the answer instead of mapping sources to specific claims. | Using a meter to show task progress such as upload completion. | Using warning text for routine hints, explanations, or mild reminders. |