| 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. | Show the measured object, current value, unit, minimum and maximum context, and threshold bands close to the gauge so users can interpret the reading without guessing. | 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. | Use source grounding display when users need to judge whether an AI answer is backed by the right body of evidence, not merely open one citation. | Use citation display when users must verify where a generated claim, summary, or recommendation came from without leaving the answer context. | Use a meter when users need to judge the current level of a bounded resource, score, capacity, or risk, not when they are completing a task or choosing a value. | 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 | A generated answer shows 97 percent sure without calibration, threshold, source coverage, or review path. | The answer shows a green Grounded badge even though only one citation supports one paragraph. | An answer ends with five links under Sources but no marker shows which link supports which claim. | A red-to-green bar says 89% with no unit, minimum, maximum, or explanation of whether high is good. | 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. | A reviewer opens the grounding panel, sees that the answer used the current policy but not the outdated FAQ, and flags one unsupported claim before publishing. | 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 | Users treat a high-confidence label as proof even though the answer has no source grounding and the claim still needs evidence. | A user trusts a generated answer because the product says Grounded, but the source scope was only web search and did not include internal policy. | A user trusts a generated compliance claim because it has a number beside it, but the number points to an unrelated source. | A user watches a meter animate during upload and waits for it to reach full even though it represents remaining quota, not upload progress. | A benefit-loss warning appears only after submission, so users cannot change the decision it warns about. |
| 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 | The system cannot estimate uncertainty or calibration honestly. | The system cannot determine source scope, retrieval status, or claim support reliably. | The product cannot reliably map claims to sources or label unresolved citations honestly. | The value has no meaningful maximum or minimum. | 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. | No-warning state where the action has no severe consequence. |
| 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. | Do not rely on color alone; include visible or programmatic warning wording and a non-color cue such as an icon. |
| 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. |