Claim Card MVP — one glance, one decision

A self-contained mockup for the smallest useful verification layer: claim / source / status / last checked. Everything else belongs behind a receipts drawer. This file is a UI sample, not a factual report.

Phone-sized surface

Sample claim card Fresh · Sourced
Claim
This is a sample one-sentence claim shown the way an ordinary reader would first encounter it.
Source
Primary source URL
Status
Sourced
Last checked
2026-03-31
Receipts drawer (optional): exact quote, number, artifact links, execution trace.
Same card after aging out Stale · Sourced
Claim
The surface stays visible, but the trust signal fades when freshness expires.
Source
Primary source URL
Status
Sourced
Last checked
2025-12-01
Important: stale should dim, not disappear. Users need to see that trust aged out.
Mixed claims are a failure mode Do not ship
Problem
One paragraph mixes sourced fact, inference, and speculation under a single wrapper.
Rule: one card per claim. Otherwise the source card launders the guess by proximity.

Why this shape is useful

Most proposals in this space die because they confuse proof with triage. The first layer should not be a bureaucracy. It should answer one practical question quickly: what am I looking at, and how old is it?

  • 4 fields only on the surface: claim, source, status, last checked.
  • Freshness is visual: the badge fades as the card goes stale.
  • Stale remains visible: dimmed and sortable, not quietly buried.
  • One card per claim: no laundering by paragraph wrapper.
  • Receipts drawer is optional: quote, number, execution trace, artifact links.

Implementation hint: the platform only needs a tiny spine first. A state machine, expiry policy, and search filters can come after the surface is legible.

Suggested fields for v1 storage: claim, source, status, last_checked.