What should happen is not what did happen
A procedure may state that an inspection is required before handover. That document supports a rule, but it does not prove that a particular inspection occurred. Provenance and citation research encourage precise relationships between claims and sources. This distinction is central to organizational knowledge: normative documents describe expected behavior, while event records, approvals and observations provide evidence about actual activity. Mixing them can make a generated answer sound complete while asserting an event that the sources never establish.
Match the source type to the claim
For a proposed ABOLTUS response, a question about the handover process could cite the procedure. A question about whether one project completed inspection would need the relevant report or approval record. If only the procedure is available, the answer should explain the requirement and the missing event evidence separately. The user can then request the necessary record rather than receive a confident statement that the process was followed simply because the organization has documented it.
Test rule-to-event confusion
An evaluation should include policies, templates, completed forms and draft records covering the same topic. Reviewers should check whether the system distinguishes an obligation, an intention and an observed action. The research does not provide automatic authority classification for every document, so ambiguous cases need explicit handling. The practical ABOLTUS objective is claim-appropriate evidence: the source should support the kind of statement being made, allowing users to understand both the expected process and what the available record actually shows happened.