# Fact-check report - {ticket title} (ticket #{id})

**Date:** {YYYY-MM-DD}
**Author:** {independent fact-checker role - must differ from the ticket's writer}
**Artifact covered:** {file(s) or content under review}
**Scope:** every factual claim destined for public text, plus any platform/product fact
the work depends on.

## Claims

| # | Claim | Primary source | Verified passage | Status |
|---|---|---|---|---|
| C1 | {exact claim as written} | {URL or API call} | {the exact text/field that supports it, or "NOT FOUND"} | ✅ / ❌ / ⚠️ unverifiable |
| C2 | | | | |

## Platform / destination facts

Claims the work *depends on* but that don't appear in the public text - including whether
any third-party platform the work targets is still operating.

| # | Fact | Primary source | Verified passage | Status |
|---|---|---|---|---|
| P1 | {e.g. "target platform has no shutdown/retirement notice"} | {platform's own homepage / status / legal page, checked directly - not a cached copy} | {quote or "no notice found"} | ✅ / ❌ / ⚠️ unverifiable |

## Notes

- Anything flagged `unverifiable` (403s, anti-bot walls, JS-rendered pages that don't curl
  cleanly) needs a manual follow-up - it does not count as a pass.
- Relative time references in the source content ("in two weeks", "this quarter") should be
  rewritten as absolute dates before the claim is marked verified.
- A homepage link used as evidence for a *specific* fact is a FAIL even if it loads (200) -
  note it as such rather than passing it.

## Verdict

**PASS** - every claim verified, no unsourced claim remains, safe to route toward Done.
**FAIL** - {list exactly which claim(s)/fact(s) failed and why}. Ticket stays in Review.