{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "schema_version": "1.1",
  "content_item_id": "editorial-column-claim-level-source-audit.en",
  "translation_group_id": "editorial-column-claim-level-source-audit",
  "locale": "en",
  "type": "briefing",
  "section": "signal",
  "slug": "claim-level-source-audit",
  "title": "A domain in the sources does not prove the claim",
  "description": "An editorial column on checking a specific claim against a specific page fragment.",
  "direct_answer": "When an AI system shows a domain among its sources, that does not prove the domain supports the answer’s main claim. Check the chain “claim – page – fragment – date,” not only the matching domain name.",
  "sections": [
    {
      "heading": "Why a domain match is too little",
      "paragraphs": [
        "A large site can contain many sections, dates, and conflicting formulations. When an answer cites a domain, the reader still does not know which page was used or whether it supports the stated conclusion.",
        "Even the exact page may be only background: it mentions the topic but does not support the number, condition, or limitation. A domain is therefore a starting point for checking, not proof by itself."
      ]
    },
    {
      "heading": "Break the answer into atomic claims",
      "paragraphs": [
        "First rewrite the answer as short statements that can each be supported or challenged separately. Do not keep a fact, causal explanation, and recommendation in one sentence: they may need different sources and different levels of confidence.",
        "For each claim, record subject, action, object, date, and condition. This quickly reveals what was lost in paraphrase and where the system added meaning absent from the page."
      ]
    },
    {
      "heading": "Check the fragment, not the headline",
      "paragraphs": [
        "Open the page and locate the sentence or table that could support the answer. Record the exact fragment, section heading, update date, and surrounding context. A headline often promises more than the body confirms.",
        "If the page contains only a related topic, mark it “unclear,” not “supported.” A partial match may be useful as a possible connection, but it should not be presented as support for the main conclusion."
      ]
    },
    {
      "heading": "Date and version change meaning",
      "paragraphs": [
        "A fact may have changed after a system accessed the page. Save the observation date and source-check date, and for unstable pages keep a snapshot or other safe artifact. This does not prove that this exact fragment was read, but it makes the audit reproducible.",
        "Do not refresh an article date merely because you reopened the page. A new date is justified by a substantive change, correction, or new check that changes the conclusion."
      ]
    },
    {
      "heading": "How to record the result",
      "paragraphs": [
        "A useful record contains the original answer, atomic claim, URL, fragment, date, support status, and a short boundary note. Store visible link and domain mention separately: they are different observations answering different questions.",
        "If the fragment cannot be found, do not substitute another page from the same site merely to fill the row. A negative or unknown result can be correct; it protects the editorial team from false confidence."
      ]
    },
    {
      "heading": "What to publish",
      "paragraphs": [
        "In a public article, separate “domain shown,” “link visible,” “claim supported,” “quote accurate,” and “reader can act.” This ladder is clearer than one aggregate metric and prevents a technical log from becoming a claim of trust.",
        "The editorial recommendation is to show not only strong matches but also cases where the domain appeared while the needed claim was unsupported. A clear boundary of knowledge is more useful than a promotional list of wins."
      ]
    }
  ],
  "published_at": "2026-09-17",
  "modified_at": "2026-09-23",
  "data_through": "2026-09-23",
  "next_review_at": "2026-10-23",
  "author": "GeoAeoAle Editorial",
  "origin": "editorial",
  "topics": [
    "source-audit",
    "citation",
    "editorial-method"
  ],
  "publisher": "GeoAeoAle Editorial",
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "canonical_url": "https://geoaeoale.com/en/signal/claim-level-source-audit/",
  "claims": [
    {
      "claim_id": "domain-is-not-claim-support",
      "text": "A domain match in a source list does not prove support for a particular claim.",
      "status": "inference",
      "confidence": "high",
      "source_ids": [],
      "publication_status": "public",
      "confidentiality": "public"
    },
    {
      "claim_id": "claim-fragment-date-chain",
      "text": "A reliable audit links the claim to a specific page, fragment, and review date.",
      "status": "inference",
      "confidence": "high",
      "source_ids": [],
      "publication_status": "public",
      "confidentiality": "public"
    }
  ],
  "sources": [],
  "related_slugs": [
    "evidence-content-entities-citability",
    "crawler-access-vs-citation",
    "measuring-ai-visibility"
  ],
  "distribution_links": [
    {
      "kind": "telegram",
      "url": "https://t.me/geoaeoale/18",
      "label": "Short version on Telegram"
    }
  ],
  "limitations": [
    "This column describes a checking protocol and does not reveal how a particular AI service selects sources internally."
  ],
  "corrections": []
}