POWER, MONEY & THE PUBLIC RECORDResearch edition / Sep 11, 2026
CLAIM CHECK DESK

Match the claim to the record.

Use this page when a reader asks for proof, context, a correction, or the right Ledger route. Pick one route, keep the caveat attached, and do not turn a source lead into a conclusion.

Updated 2026-09-15 · source-safe claim routing · no public form, post, comment, join, invite, DM, boost, spend, follower claim, or traffic claim made by this page
CLAIM ROUTEone link

The strongest public reply is usually one exact route: what is claimed, what record supports it, what response or outcome exists, and what remains unproven.

ASSERTIONquote it

Write the exact claim before choosing a Ledger route.

RECORDopen it

Use the source map, case file, answer page, topic page, or tracker item that actually fits.

LIMITattach it

Say what the record does not prove before the link travels.

CLAIM ROUTES

Choose the narrowest useful link

Specific beats broad
COPY LINES

Ask for proof without escalating the thread

Copy, then adapt
RECORD FIRST

Ask for the exact file

I would match that claim to the exact record first: allegation, source, response, outcome, and date. Start here: https://innercircleledger.com/claim-check/

CAVEAT

Slow down a name claim

A name mention is a lead, not a verdict. Check the document route and context before treating it as proof: https://innercircleledger.com/answers/does-a-name-in-epstein-files-prove-wrongdoing/

CURRENT

Route a recent claim

If this is about a recent action or ruling, use a dated route instead of a broad claim. Tracker: https://innercircleledger.com/trump-tracker/

BEFORE SHARING

Do not overstate the file.

If the route does not show the claim, switch routes or say the evidence is not there. Count a share only when it is visible and allowed by the room.

Next useful route

Answer pages · Ask source question · Standards · Sharing checklist