Send the Ledger page and the sentence that needs a stronger record.
The best growth signal is a useful reader asking for a better source. Route the question, verify the record, and fix the public page before sharing wider.
Separate when something happened from when a source was published or checked.
Ask for the exact file before treating a name mention as a claim.
Route the reader before the claim spreads
Find the official release routes
Use when the question is about DOJ, House, court, FOIA, or Data Set paths.
Start with the big finds
Use when the reader needs the main takeaways with the verification route attached.
Keep the name caveat attached
Use when a screenshot, list, or comment treats a mention as proof without document context.
Verify the claim before sharing
Use when the reader has a claim but not the source trail, response, outcome, or date.
Make the question checkable
Specific correction request
Page URL: [paste]. Disputed sentence: [paste]. Better source: [paste]. What the source changes: [date, outcome, label, or caveat].
Source request
Question: [what needs proving]. Current Ledger route: [paste]. Missing record: [court filing, official release, dataset, response, or date]. Why it matters: [one sentence].
No-link fallback
I would check the exact document and outcome before treating that as settled. A name, date, filing, or news summary needs the source route attached.
Use the contact and correction path.
The site does not collect source questions in a form. Use the contact page or correction standard, include the exact source trail, and avoid sending private personal details about third parties.
Open the right route
Publisher contact · Correction standard · Source directory · Answer pages