Resources · 114

AI citations: check an answer when its source changes

Bind claims to a document version and passage, then handle stale citations without rewriting history.

· 2 min

Documents and note taking during a discussion Illustration · fictional scene

What this guide helps achieve

  • Identify the evidence used
  • Test a document revision
  • Reassess the claim and publish a correction

Quick check

  • Claim, version, passage and context table.
  • Change cases and anchor verdicts.
  • Dated correction and explicit evidence status.

Step-by-step method

  1. 01

    Identify the evidence used

    Link claim, document, version or reference date and precise passage. Keep a permitted short excerpt or position with enough context to find it. A working URL does not establish that the current document supports the claim; a technical anchor does not validate meaning.

    Claim, version, passage and context table.

  2. 02

    Test a document revision

    In a fictional case, change a value, remove a paragraph and repeat one sentence in two locations. Check that the citation flags a missing or ambiguous passage rather than silently pointing elsewhere. Contextual text selectors help locate passages, not verify factual truth.

    Change cases and anchor verdicts.

  3. 03

    Reassess the claim and publish a correction

    Separate located passage, supported claim, contradiction and insufficient evidence. Set the relevant date for the question and review important changes before publication. Retain the prior answer and reference when history is useful; do not present old evidence as current validation.

    Dated correction and explicit evidence status.

Acceptance case to reproduce

Fictional example: these inputs describe no customer or observed result.

View case inputs
{
    "cited_version": "v1",
    "cited_delay_days": 5,
    "opened_version": "v2",
    "current_delay_days": 7,
    "expected": "historical_context_or_current_correction"
}

Expected decision

Fictional example: an answer cites a 5-day delay from v1, but the link opens v2 stating 7 days. Finding the document does not validate 5 days; retain the historical context or correct the answer for the current question.

NIST AI 600-1 — Generative AI Profile

Your acceptance workbook

Record observations against this guide’s criteria. A record is not certification.

The workbook does not save automatically. Export before leaving.

Management indicators

IndicatorWhat it measuresFirst action
Resolved anchorsLocated passages / checked citationsRetain version and ambiguities
Unsupported claimsChecked claims lacking sufficient evidenceSeparate contradiction, absence and unavailable source

Common pitfalls

    Frequently asked questions

    Does a citation found in the new version confirm the answer?

    Not necessarily. Context or scope may have changed. Check actual support for the claim, its date and possible contradictions.

    Official references

    References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.