A citation can open the right document and still support the wrong answer. If a travel policy changed between booking and reimbursement, the document title alone cannot tell a reviewer whether the assistant used the applicable rules.
For a knowledge product owner, version accuracy means preserving the connection between a claim, the source revision that supplied it, and the revision shown when someone follows the link. Treat those as three separately testable objects.
Keep revision identity alongside every retrieved passage
Record a stable document identifier, a revision identifier or content fingerprint, the source location, the ingestion time, and any explicit effective date. An update timestamp is useful evidence of change; it is not necessarily the date a policy became applicable. Store that distinction deliberately.
At answer time, retain the revision and passage used to support each material claim. If the source only provides a moving link to its current content, label that limitation in the citation interface. A content snapshot may help authorised reviewers reproduce the answer, but its retention and access rules need a separate decision.
Work through a fictional reimbursement dispute
Suppose revision A allows a fictional allowance of 40 units and revision B allows 55. Revision B was uploaded on June 10 and applies to travel beginning July 1. Ask about a trip starting June 25, then about one starting July 3. These are illustrative test values, not real policy advice.
The first response should use the rule applicable to June travel. The second should use the July rule. Open every citation and check whether it shows the same revision and effective-date wording as the retrieved passage. A correct number with a link that silently opens another revision still deserves a citation defect.
Add a third question with no travel date. The expected behaviour is to ask for the missing date or explain the conditional rules. Guessing the latest version converts missing context into an apparently authoritative answer.
Separate stale retrieval from unstable links
Use failure categories that identify repair work: old content retrieved, effective date ignored, correct passage cited incorrectly, or destination changed after generation. Reindexing might fix the first category while doing nothing for a link that always resolves to the newest file.
Immutable revision links improve reproducibility but create a maintenance obligation when documents are withdrawn. Moving links are simpler for readers yet require an explicit version label. Neither choice removes the need to check current permissions before opening retained content.
The source-citation guide explains the broader evidence boundary. The Nucleus portfolio account provides related project context; this reimbursement exercise is a proposed test, not a reported client incident.
Questions about document-version citations
Is a matching document title enough?
No. Titles can remain unchanged across revisions. Compare the revision identity and the relevant passage, including conditions around the cited sentence.
Should every answer always use the latest revision?
Only when that revision applies to the question. Historical questions may require an older policy, and effective dates can differ from upload dates.
What should a reviewer capture first?
Save the question, answer, source revision, retrieved span, and opened destination together. Bring one failed example to a knowledge integration review before changing the whole retrieval pipeline.