What this page adds

• It directs readers into reviewed public workflows instead of pushing sensitive research, identity claims, or correction requests into unmanaged inboxes.
• It protects the editorial process by separating source leads, factual challenges, and general safety questions into clearer lanes.
• It makes the current infrastructure honest: no fake contact promise, no hidden private review channel, and no encouragement to publish personal contact information.

Current contact path

Use the reviewed public workflows below for source leads, correction requests, privacy concerns, permissions questions, community notes, and general editorial contact. Do not publish personal email addresses publicly.

• Corrections and source suggestions
• Submit a Community Note
• Request a Fact Check
• Review Safe Sharing guidance
• Privacy Policy
• Editorial Standards

What belongs in each lane

Use Corrections for factual errors, source suggestions, permissions questions, and public wording problems. Use Community Notes for added context, archive leads, map links, and wording cautions. Use Fact Check for a claim that appears overstated, mislabeled, unsupported, or in need of correction. Use Safe Sharing when the main issue is privacy, exposure, or harm reduction.

How to write a useful message

• Start with the page URL or topic.
• Name the exact claim, source, correction, or privacy concern.
• Include public source links when available.
• State whether the issue is corrections, source suggestions, community notes, privacy/safe-sharing, permissions, general editorial contact, accessibility, or classroom use.
• Leave out private contact details, raw DNA files, living-person records, private family records, legal documents, private lineage notes, and unpublished oral-history material.

What not to send publicly

Do not send private family, genetic, lineage, oral-history, legal, living-person, or sensitive identity information through public or insecure forms. Do not ask this site to certify identity, ancestry, tribe, nationality, DNA conclusions, legal status, descent, or membership.

Permissions

For classroom use, excerpts, screenshots, reuse, quotation, or linking questions, start here and include the page URL, intended use, publication context, and any deadline. Do not attach private documents unless a safer private route has been reviewed.

Network handoff

TheFoundationsOf.us may coordinate with CultureUP or related network properties for broader support routing, but this same-domain page remains the public destination for TheFoundationsOf.us editorial, privacy, source-review, and support questions. Any handoff should be labeled before readers leave this site.

Response expectation

These workflows are review lanes, not instant support chat. A useful submission may become a page update, a source-review note, a fact-check entry, a correction, or a held item if the public wording is not safe yet.

What makes a message actionable

An actionable message names the page, the exact wording, the source or source gap, the privacy risk if any, and the lane you think fits. Short notes are fine when they are specific. Broad claims, private proof demands, identity-certification requests, and unsupported conclusions usually need source review before they can change public wording.

The contact path exists to protect the site from two weak outcomes: ignoring reader corrections and publishing sensitive material too quickly. The stronger path is to receive the lead, label the risk, route it to the right public workflow, and only update the page when the evidence and privacy posture are clear.

Low-depth value guardrail

Contact / Support is a trust page, but it also has to be useful. It should tell readers how to make the next message better: name the route, identify the source, describe the claim boundary, avoid private evidence, and choose the correct public workflow. That makes the page more than a directory of links.

The page also protects the project’s lane. TheFoundations handles foundations, Muur history, ancestral memory, place-based research, source review, safe sharing, corrections, and careful public claims. Messages that belong to CultureUP, MoorOfUS, African Memory, or private family review should be labeled and routed without turning TheFoundations into a generic support desk.

Contact routing checklist

• Use Corrections when the message reports a factual issue, source suggestion, permissions question, privacy concern, or public wording problem.
• Use Community Notes when the message adds context, a source lead, a place clue, or a careful wording caution.
• Use Fact Check when the message challenges a specific public claim that may be overstated, unsupported, mislabeled, or contradicted.
• Use Safe Sharing first when the message contains living-person details, family records, contact information, DNA, or private documents.