> ## Documentation Index
> Fetch the complete documentation index at: https://vicewire.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Facts vs Rumors

> How ViceWire distinguishes officially confirmed claims from sourced reporting and rumor-level speculation.

`claim_confirmation_status` describes **how the article presents the evidentiary status** of the claim itself.

For example, a partnership can be reported as being implemented while still not being formally confirmed by the relevant parties. Keeping these dimensions separate helps avoid overstating certainty.

<Warning>
  `claim_confirmation_status` captures how the article represents the claim, not whether the claim is objectively true.

  An article may present something as official or confirmed even when that is not well supported. This field should therefore be read alongside source-quality signals such as `domain_tier` and broader story coverage.

  ViceWire is also developing a cross-source fact-checking layer to help validate how widely supported a claimed fact is, but that is not part of the current field definition.
</Warning>

<ResponseField name="claim_confirmation_status">
  `claim_confirmation_status` captures whether the article presents the claim as officially confirmed, reported but not officially confirmed, or rumor-level speculation.
</ResponseField>

<ResponseField name="officially_confirmed">
  `officially_confirmed` means the article presents the claim as formally confirmed by the company, or another authoritative primary source.
</ResponseField>

<ResponseField name="reported_not_official">
  `reported_not_official` means the article presents the claim as a real reported development based on sourcing, but it is not formally confirmed by the relevant parties.
</ResponseField>

<ResponseField name="rumor_or_market_speculation">
  `rumor_or_market_speculation` means the article frames the claim as rumor, speculation, chatter, or early market talk rather than as a well-sourced reported development.
</ResponseField>

<Info>
  This field should be read alongside `event_stage_statuses`, not as a replacement for it.
</Info>