Skip to main content

Research Method

Research Method

Move from claim to source trail

Use this method to separate sourced records, interpretation, memory, oral tradition, spiritual meaning, DNA leads, and questions needing review.

Research Method

The FOBA research method is evidence-led, correction-friendly, and privacy-safe. It helps readers distinguish sourced records, historical interpretation, community memory, oral tradition, spiritual interpretation, DNA leads, and claims needing more review.

What this method adds

  • It gives readers a repeatable way to slow a claim down before it turns into public certainty language.
  • It keeps source type, place context, and wording risk in the same frame instead of scattering them across different pages.
  • It helps a learner move from curiosity to a usable source trail without pretending every clue is proof.
  • It creates cleaner handoffs into Source Review, Claim Review, Fact Check, and Community Notes.

Method steps

  1. Write the claim plainly. Avoid loaded wording until the source trail is clear.
  2. Name the source type. Public record, map, archaeology, scholarly summary, oral history, community memory, spiritual interpretation, or DNA lead.
  3. Anchor the place. Identify rivers, roads, towns, counties, archives, churches, schools, cemeteries, and boundary changes.
  4. Separate support from interpretation. Say what the evidence supports, what remains debated, and what sources should be reviewed next.
  5. Protect living people. Redact private details, avoid personal contact information, and use pseudonyms when helpful.
  6. Invite correction. Use Community Notes and Fact Check requests when wording needs review.

Source-quality matrix

  • Primary source row: exact record, map, image, transcript, archive identifier, date, place, and quoted detail.
  • Context source row: museum, archive guide, scholarly summary, public-history page, or institutional background that explains how to read the primary row.
  • Conflict row: a source that disagrees, uses another name, changes boundaries, gives a different date, or leaves a gap.
  • Memory row: oral history, community memory, or story material that should be labeled and protected rather than treated as documentary proof.
  • Risk row: privacy, living-person exposure, identity-adjacent wording, DNA, legal-status implication, or community-consent concern.

When the method says slow down

Slow down when the page has only one source lane, when a source supports place context but not identity language, when names or boundaries change, when a living person could be exposed, or when spiritual/community meaning is being converted into documentary proof.

Claim review frame

This frame adds one disciplined move to public reading: separate the sentence being made, the evidence behind it, the uncertainty around it, and the wording that is actually safe to publish.

What the claim says

Write the claim in one plain sentence before adding interpretation.

What evidence supports

Name the records, maps, archaeology, oral-history notes, or scholarly summaries that can be checked.

What remains debated

Mark interpretation, community memory, spiritual reading, or open questions honestly.

Recommended wording

Use careful wording that does not certify identity, ancestry, tribe, legal status, DNA conclusions, or community membership.

What remains open: A completed frame improves clarity, but it does not settle a claim until the source trail is strong enough and the wording survives review.

Recommended wording

Use language such as “the record supports,” “the source suggests,” “community memory holds,” “this remains debated,” or “citation needed.” Avoid language that certifies identity, tribe, legal status, descent, DNA conclusions, or community membership.

What a reader should leave with

  • A more precise version of the claim than they started with.
  • A short list of place anchors, institutions, and source types to check next.
  • A better sense of what can be said publicly now and what still needs review.

Method output packet

A useful method pass should leave a small packet: one plain claim, one place anchor, one source-quality row, one risk row, one safer wording option, and one next review lane.

Scroll to Top