Understanding assistant summaries of Records¶
HiveAI has Records read operations for finding records, checking their status, inspecting document information, and summarizing dossiers and pre-system import submissions. These reads gather information; they do not register, file, sign, import or otherwise change a record.
Availability: this page describes what the Records service can return. The corresponding assistant screens, connected application links and target-environment behavior remain unverified. Use it to understand the meaning and limits of a result. Action-by-action assistant instructions require a separately verified journey.
For knowledge indexing, excluded record categories and basic status, see Records information in HiveAI. The richer reads below add a current Records viewing-permission check. They still depend on the correct organization and the access information supplied for the person asking.
What the different reads return¶
| Information requested | What Records supplies | What the result does not establish |
|---|---|---|
| Find records | A limited set of accessible record references and lifecycle, filing, custody and disposition facts. | A complete register or an exact count of all matches. |
| Registry-review information | Accessible items selected from the intake queue, with record type and saved destination hints. | The same selection as the application's narrower registry-review list. |
| Record detail or progress | The record's current reference and status facts. | Full record detail, the document body or a history of completed work. |
| Retrieval, review, compliance or stewardship information | A status summary labeled for that kind of work. | That work has happened, passed a review or has a recorded completion. |
| Registration choices or record types | Category keys from the active classification plan, required-main-document information, the supporting-file limit and general destination types. | A full set of live offices, people, positions or queues, or a guarantee that registration will succeed. |
| Document history | A summary per returned document: name, current version, file type, size when known and version count. | Every historical version or access to the document itself. |
| Primary document | Metadata for the record's main document. | A document-viewing session, downloaded file or signed document. |
| Signing readiness | Whether the source can identify a current primary-document version, plus version and file information. | That the person is authorized to sign or has completed the protected signing steps. |
| Dossier search or detail | Dossier title, reference, kind, category and linked-record count. | Access to every linked record or a full list of its contents. |
| Import search or detail | Submission name, method, state and total, imported and failed-item counts. | Individual failure reasons, the complete imported-item list or completion of a retry. |
| Archive source collections | A limited set of saved source-collection names. | A complete archive inventory or confirmation that all files in a collection were imported. |
These distinctions matter when an assistant phrases a result as a summary. For example, “review information” currently gives lifecycle facts; use the completed-work explanation to understand the separate evidence of an actual review.
A short result is not a complete search¶
These reads accept a requested limit of up to 50 items. Archive source-collection suggestions are further limited to 20. Some operations return a single summary even when they consult a larger underlying result.
Record search and the intake-based read select candidates before removing records outside the person's scope. A short or empty answer can therefore occur even when a later candidate would be accessible. Dossier and import searches return the first requested page; these assistant results currently provide no continuation to the remaining pages.
Do not treat the visible item count as the organization's total, or an empty answer as proof that a record does not exist. Refine the question with a known reference or use the authorized application list when you need a complete search. Application availability and the assistant's return link must still be confirmed for your organization.
Access and sensitive information¶
The richer read checks the person's current Records viewing permission. Record-level results also apply the source's classification and responsibility rules, including its exclusions for personnel, Secret, archived, rejected and disposed records. Changing permission can make a previously available result unavailable.
Dossier and import summaries have a different scope from individual-record answers. A dossier's linked-record count is not proof that the person can open each linked record. General dossier search excludes specialist dossier kinds, while direct dossier lookup has different restrictions. Administrators must verify the intended scope before relying on these summaries across specialist work.
If access changes or a result is withheld, ask the responsible registry team to check through an authorized journey. Changing a record's category or copying its contents into a chat is not an appropriate way to resolve an access problem.
Read readiness and completion separately¶
“Ready” in the current signing-information result means Records found the current version of the main document. It does not check all requirements of the signing service, establish a personal signature or PIN, or create a signing session. Unknown file size remains unknown. Continue through the approved protected signing journey when it is available; never send signing credentials into an ordinary assistant prompt.
Likewise, an import summary describes the saved submission state. It does not retry a failed submission or explain every failed item. See pre-system files for the submission lifecycle and recovery limits.
The simple “Eligible” disposition fact also appears in record summaries. It means no completed disposition and no block were found; it does not calculate retention eligibility. Follow the actual governance rules before a final disposition decision.
When a summary differs from the application¶
Check that both views concern the same organization, record and version. Consider whether the assistant returned a limited result, a saved destination hint or a status summary instead of the fuller app view. A successful read does not mean all information was collected at one instant: related metadata may change between the source reads.
Give support the reference, approximate time and the specific fact that differs. The support team should compare the authoritative record and the intended result type, then investigate access, freshness, result limits or a broken return link. Keep confidential contents and credentials out of unrelated support channels.
Business owners should verify these meanings with representative users before relying on summaries for oversight. A result labeled review, compliance or signing readiness is not, by itself, evidence of approval, compliance or a completed signature.