Check an answer and its sources¶
Use an answer to understand a topic, then check the supporting material before relying on it. A citation is a reference to evidence that was selected for the answer. It does not guarantee that every sentence is correct or that all relevant records were considered.
Availability: The steps for expanding sources follow the intended 06 Final Screens. HiveAI entry remains unavailable in the inspected frontend. Protected knowledge reading exists in the backend, but its complete screen journey has not yet been verified. The steps below describe the designed experience for a compatible client when delivered.
Before asking¶
Use the correct organization and an account with HiveAI access. Source access still applies: permission to use the assistant does not provide permission to read every record, another person's conversation or an unpublished manual.
State the question and the context that matters. For example: “According to the current team handover guide, what information belongs in a handover note?” This is more useful than “Tell me everything about handovers.” If a document's title, version, department or equipment model matters, include it in the question. Naming a source does not grant access to it or guarantee that it was selected.
Follow the conversation guide to submit the question, understand any estimate and recover the original request after an interruption. Do not submit the same question again merely because the source list is still loading.
Expand the supporting sources¶
- Read the answer and its current progress message. The knowledge-answer designs can show Text ready · Preparing audio; text being available and audio being ready are separate outcomes.
- Find the source-count control beneath the answer. The inspected example says 2 sources. The number is illustrative and depends on the answer.
- Select that control to expand the supporting entries. Review each displayed title, location and freshness information.
- Compare the entries with the question you asked. Check whether they identify the right document, subject and version where that information is available.
- Use the follow-up question field to ask about a specific omission or ambiguity. A follow-up is another submitted request, with its own work and cost implications.
The mobile design keeps the answer and source disclosure in the conversation. Its wider navigation is reached through Menu. The inspected source entries show document titles and locations; they do not establish a working source-opening button or a complete document-viewing route. See reading published knowledge for the implemented reading capability and its current delivery limits.
Understand what the source details mean¶
| Detail | How to use it |
|---|---|
| Title | Identify the material supporting the answer; similar titles can refer to different documents |
| Version | Distinguish the evidence used for the answer from a later publication |
| Page | Locate the passage when a genuine page is available; an unpaginated text document must not be assigned an invented page |
| Section | Find the relevant part of the document; read surrounding material for qualifications or exceptions |
| Passage | Check what the cited text actually says, including what it does not say |
| Freshness information | Understand the source timestamp supplied with the evidence; it does not prove a human reviewed the generated answer |
| Source count | See how much evidence is attached; multiple passages may come from one document |
The current designs use “checked” beside a date. The backend supplies source-update or publication freshness, depending on the source. Treat that date as source context, not as an endorsement, a human review date or a promise that every organizational document was checked. The wording remains part of the design reconciliation.
A citation can identify a valid passage while the generated explanation still makes a mistaken inference. Match the claim to the passage rather than relying on the presence of a reference alone. Ask for clarification when the answer goes beyond what you can verify.
When evidence is incomplete¶
A search works within the current workspace, access rights, supported source types and result limits. It selects a bounded set of passages. Some material may be excluded by permissions, publication status, indexing state, size limits or the question's scope.
A missing source therefore does not mean that the source does not exist. A short list is not an exhaustive inventory, and the number of results is not a count of every matching document. Refine a broad question with the relevant subject or document details. Where the library is available, use its current published-document search as a separate way to locate material.
If the answer says the supplied manual does not contain the required information, obtain the correct authorized document or ask its owner. Do not fill the missing detail with an unsupported assumption. If different sources disagree, identify the documents and versions involved and ask the responsible owner which instruction applies. A generated preference between conflicting documents does not itself establish organizational authority.
When sources become unavailable¶
The unavailable-source designs show Sources unavailable — confirm the current procedure. That message means the evidence cannot currently be relied on through that view. It does not prove that the original document was deleted or that your entire HiveAI account is unavailable.
An earlier citation can become unavailable because access changed, the source was withdrawn or replaced, or the service could not verify it. Some checks deliberately avoid revealing which condition applies to protected material. Support should not infer the existence of a hidden source from an unavailable response.
For a published knowledge document with a newer authorized version, the backend can offer access to that current version. It keeps the old citation unavailable; it does not rewrite the earlier answer as though the new version had supported it. Ask a new, focused question about the current guidance if you need an updated explanation.
Conversation history and saved progress can behave differently. The current history read can omit an answer when its expected sources are no longer available. The inspected unavailable-source screen retains the answer and audio-preparation state, so that design still needs reconciliation with the actual read path. Do not assume that an unavailable source is permission to keep showing or speaking its earlier contents.
Recover according to the problem¶
| Situation | Next step |
|---|---|
| Source entries are still arriving | Keep the original request open and check its saved state before repeating work |
| The source list is empty or too narrow | Refine the question; use a known title or subject and check current published material |
| A cited version was replaced | Review the authorized current version separately and reassess the answer |
| Your membership or source permissions changed | Re-establish legitimate access with the responsible administrator or source owner |
| A document view expired | Start a fresh authorized view of the current publication |
| The service cannot verify a source | Retry after the interruption; if it persists, give support the safe request reference and time |
| Two publications disagree | Ask the responsible business owner which version or procedure governs the task |
| Text is ready but audio is not | Read the text where permitted and follow the speech recovery guidance |
Do not forward session credentials, raw access tokens or protected content to support. Give the organization, approximate time, visible message and safe reference, plus the document title only when you are authorized to share it.
For managers, executives and administrators¶
Review examples that include a useful answer, missing evidence, conflicting versions, changed access and an expired document view. A demonstration that only shows a successful answer will not establish reliable recovery.
Ask whether users can explain the difference between source freshness and answer accuracy, between a cited version and the current publication, and between a small result set and a complete search. These are practical comprehension checks for the initial reviewer; they are not recorded as completed acceptance tests.
Publish and govern knowledge deliberately. Making a document available to all current members affects who can read and use it, but it does not confer administrative powers or guarantee browser delivery. Source owners remain responsible for the content's meaning and applicability.