Retrieve the correction with the claim
Enterprise search can retrieve an accurate quotation from a superseded document. Keep correction evidence attached to the claim, and establish whether the question asks for the current position or an earlier recorded state.
Keep development and test groups separate before comparing performance. No measured results are shown.
An enterprise assistant can quote a slide correctly and still give the wrong answer. A correction may sit in a message, while the old chart remains in a presentation copied into a newer folder. The useful search result is the claim together with the evidence needed to establish which version applies.
MMEnterprise-Bench, a preprint submitted on 20 October, tests question answering over simulated workplace records containing text, images and retained revisions. Its tasks distinguish reasoning from sufficient evidence, resolving conflicts and recognising missing information. (Benchmark design, section 3)
For the knowledge-service owner, the opportunity is more dependable answers from a working archive without erasing its history. The data design should connect corrections to the claims they change. A recent timestamp or a high search score cannot establish that relationship by itself.
A newer file can contain an older claim
Consider a hypothetical equipment project. An initial slide says a component passed a qualification check. The test owner later records that the result belonged to a different component and explicitly withdraws the claim. A colleague subsequently uploads the original slide to a meeting folder without changing its contents.
Asked whether the component passed, the assistant should retrieve the withdrawal alongside the slide. Asked what the initial presentation reported, it should describe the earlier claim and identify the later correction. Those are different questions with different supported answers. Neither requires deleting the original slide.
The example also shows why sorting by upload time is insufficient. The newest file is a later copy of earlier content. A proposed change, a confirmed correction and an administrative copy have different meanings even when all carry timestamps.
The paper reports a qualitative failure in which a model answers a question about the deadline before a revision with the revised deadline, despite the earlier value being present. That is a failure to select the requested state, rather than simply a missing document. (Qualitative analysis, section 4.5)
Preserve the relationship that changes the answer
A proposed correction record should identify the affected claim, its source version, the replacement or withdrawal, the responsible source and the evidence for that relationship. Scope it to the relevant subject, measure and period. A correction to one component’s result must not silently change every similar chart in the project.
The older World Wide Web Consortium PROV ontology, published in 2013, supplies a vocabulary for provenance, the recorded origins and relationships of information. Its revision relation connects a revised entity to its original. This can support document-version lineage. It does not determine who may approve a correction or which claim should govern a business answer.
Do not force every correction message into a whole-document revision. A message may withdraw one assertion while leaving the rest of the slide intact. Store the claim-level link and its supporting passage separately from document lineage. If a model proposes that link, retain it as a candidate until the service’s agreed validation process establishes it.
For visual material, preserve the page or chart region, its labels and the surrounding qualification. Keep extracted text linked to the original image. A corrected legend or denominator can change a chart’s interpretation even when its headline remains unchanged. Reviewers need both the earlier visual and the record explaining the change.
Change the rule for selecting a recorded claim
Fictional internal search service · 2026-10-19 → 2026-10-21
Previous text · 2026-10-19
Answer from the most recently uploaded matching file. Cite that file as the source.
Revised text · 2026-10-21
Identify the requested subject, period and historical perspective. Retrieve the claim with explicit correction evidence. Select the supported revision or report the conflict as unresolved.
Interpretation · decisions to reassess
- A later upload of an old slide does not reverse a documented correction.
- A historical question can legitimately require the earlier recorded value.
- A proposed revision without confirmed authority remains a candidate for review.
A hypothetical internal rule comparison, not a legal change, adopted Institute policy or measured benchmark result. The dates belong only to this constructed example.
Compare two fictional internal search rules. The original selects the latest matching file. The proposed rule follows explicit corrections for the same subject and period, preserves historical versions and leaves unresolved conflicts visible.
The comparison illustrates a proposed selection rule. It is not a rule tested by MMEnterprise-Bench. Its practical cost is maintaining relationships that ordinary keyword or similarity search may omit. Start with a bounded collection whose owners already record revisions, rather than inferring a complete correction history across every workplace channel.
Retrieve the related evidence within the same access boundary
When search finds a claim, use established links to obtain relevant revisions, withdrawals and supporting records. Preserve their identifiers in the answer trace. Let the requester inspect why the selected value applies, including whether the answer describes the current position or an earlier recorded state.
Apply access checks to every related record. A link from an accessible slide must not disclose a restricted correction. Where permitted metadata establishes that the slide is no longer current but the replacement cannot be shown, return an appropriately scoped unresolved answer or route the request to its owner. Do not manufacture a current value from the older slide.
A disputed correction needs an explicit unresolved state. More recent text does not automatically outrank an approved source, and disagreement between authorised owners may require their decision. The assistant can present the conflict with its evidence without settling the organisation’s authority structure.
The archive’s answerability article distinguishes missing guidance from a retrieval miss. Here the records may all be available, yet the relationship between them determines the answer. The backtesting article asks what information was available to an earlier system. A historical question asked today can instead use later evidence to explain what an earlier document said. Make that requested perspective explicit.
Test corrections that travel through different formats
Build a small, approved fixture containing an original chart, a correcting message, a revised document and a later copy of the original. Ask paired questions about the current claim and the earlier presentation. Add a correction concerning a different subject, an unconfirmed proposal and a withdrawal with no replacement value.
Check whether the service retrieves the needed relationship and whether it answers correctly when those records are supplied directly. This separates discovery failures from interpretation failures. Record wrong current answers, wrong historical answers, unsupported conflict resolution and unnecessary refusals separately. Have the document owner adjudicate the expected answer and the evidence that supports it.
MMEnterprise-Bench uses generated workplace material grounded in public documents, model-assisted validation and an automatic answer judge. Human validation covers a subset and was performed by the authors. Its results do not establish another organisation’s error rate or validate the proposed correction-link design. (Validation, evaluation and limitations) No model experiment was run for this article.
The knowledge-service owner should choose a collection where resolving revisions would remove useful manual investigation. Agree the correction authority with its document owners, then compare ordinary retrieval with the proposed linked-evidence route. Expand only where the service can explain both the selected claim and the revision state it describes. Where that relationship remains uncertain, preserve the question for its owner rather than turning recency into authority.