Fact Check
Fact Check Requests
Ask for a deeper review of a claim, page, source, or interpretation.
What helps reviewers
Helpful requests include the exact claim, where it appears, what evidence supports or challenges it, and any source links. Published outcomes may update a page, add a Community Note, or create an entry in the Corrections Log.
What a fact check adds beyond disagreement
- It identifies the exact sentence or conclusion that needs review.
- It forces the site to compare public wording against the actual source trail.
- It can produce a narrower claim, a stronger label, a correction, or a hold decision.
- It creates a public record that the site is willing to revisit its own wording.
Claims that deserve fact-check review
- A page uses one source to imply a broader identity, ancestry, descent, legal-status, or membership conclusion.
- A source supports a date, place, or institution but the public wording turns it into certainty about a person or group.
- A claim mixes Muur history, Moor history, oral tradition, spiritual interpretation, or community memory without clear labels.
- A page omits contradiction, counter-evidence, name variation, boundary change, translation risk, or missing-source context.
Useful request format
- Quote or summarize the exact public claim.
- Link the page where it appears.
- Name the source or missing source at issue.
- Explain whether the problem is evidence, wording, privacy, classification, or correction history.
- Suggest safer wording if the current sentence overreaches.
Possible outcomes
A fact check may mark a claim supported, disputed, unsupported, corrected, or still open. It may also move the issue to Source Review, Community Notes, Corrections Log, or Safe Sharing if the main risk is source quality, public context, factual revision, or living-person exposure.
Fact Check Request
Ask for a claim to be reviewed against sources. Accepted requests are held for editorial review before publication.
Use a pseudonym if you want attribution. Do not include email addresses, phone numbers, addresses, private DNA data, or information about living people.
What this form adds
- It isolates the exact sentence, interpretation, or source use that needs review.
- It gives readers a formal way to challenge overreach without reducing the process to comment-thread argument.
- It helps the site build a visible public record of review pressure and correction paths.
Useful Fact Check examples
- A page sentence that sounds stronger than the source trail can support.
- A claim that blends record evidence, oral tradition, spiritual interpretation, or community memory without labeling the lanes.
- A source that contradicts, narrows, or complicates the current public wording.
- A missing citation, changed boundary, name variant, translation issue, OCR problem, or date conflict that affects the claim.
Hold or decline reasons
- The request does not quote or paraphrase a specific claim to review.
- The request asks the site to certify identity, ancestry, legal status, DNA, descent, tribe, Nation, or membership.
- The request depends on private documents, living-person details, or sensitive family material that cannot be reviewed publicly.
Possible routing outcomes
A Fact Check may end as supported, narrowed, relabeled, corrected, held, or unresolved. The safest result may be weaker public wording rather than a louder conclusion.
What remains open: A fact-check request can lead to narrower wording, a hold decision, a correction, or a stronger source packet, but the issue is not resolved until editorial review finishes.
Published Fact Checks
What this archive adds
- It keeps disputed wording and source tension visible instead of letting claims circulate without challenge.
- It shows the kinds of questions readers raise when a page feels overstated, undersourced, or mislabeled.
- It gives the site a public memory of which claims triggered deeper review.
You should leave with a clearer sense of what was challenged, what kind of evidence tension matters here, and how the project handles review without pretending every question already has a final answer.