Content type
Wiki explainer
Primary use
Use this page to compare source lanes, place anchors, and wording limits before repeating a historical claim as settled.
What this page adds
It should add source-aware context, place anchors, wording limits, and a clearer next step than a raw claim or isolated source link can provide.
Evidence level
Starter
Claim status
Open
You should leave with a narrower question, a clearer place context, and a better sense of what the current source trail can support.
Overview
St. Augustine records can move across Spanish, English, church, military, civil, and newspaper contexts. This guide keeps translation notes and name variants visible so readers do not mistake one spelling or one translated phrase for complete proof.
What this page adds
- It turns a topic, place, or naming question into a source-led learning page instead of leaving it as a vague claim or isolated citation.
- It separates what the current record can support from what still needs comparison, correction, or stronger evidence.
- It gives readers a next-step research path instead of pretending the page is the last word.
What this helps you learn
- Translation notes can clarify record creator, language, uncertainty, and alternate readings.
- Name variants may reflect spelling practice, language shifts, clerical choices, family usage, or OCR error.
- A careful source table distinguishes what the source says from what the researcher infers.
Careful claims
- Do not treat one translated phrase or one name variant as ancestry, descent, legal-status, tribe, DNA, identity, or membership certification.
- Do not hide uncertainty when the record language, transcription, or translation is contested.
- Do not convert colonial church or civil categories into modern identity claims without review.
Research path
- Record the original wording, translation, uncertainty note, name variant, and claim limit in separate columns.
- Compare parish, military, cemetery, newspaper, and map records before strengthening public copy.
- Route contested translation or identity-adjacent wording through Source Review and Fact Check.
Reader quality check
- Can you name the exact place, period, institution, or source type this page is using?
- Can you separate a direct source detail from an interpretation or community-memory reading?
- Can you identify which sentence would need a Source Table, Place Packet, or Claim Review Card before reuse?
- Can you explain what would change the wording: a new source, a contradiction, a boundary change, a name variant, or a privacy concern?
Before reusing this page
- Copy the claim only with its evidence label, place context, and uncertainty note.
- Check whether the page is explaining a source, a memory lane, an interpretation, or a working hypothesis.
- Use Source Review before turning the page into stronger identity, ancestry, legal-status, descent, DNA, membership, or Nation-language wording.
- Use Community Notes or Fact Check if a missing source, changed boundary, name variation, or contradiction would alter the public wording.
Source trail
- FOBA Source Table Template – Keep wording, translation, and inference separate.
- FOBA St. Augustine Fort Mose Service Ledger Method – Use service lanes before family claims.
- FOBA Evidence Gates – Label translation-sensitive claims carefully.
What remains open
This starter should be treated as a working research surface. Dates, naming, family continuity, identity-adjacent conclusions, and disputed interpretation may still need Source Review, Fact Check, Community Notes, or stronger corroboration.
Evidence note: This starter entry is educational. Add sources, dates, maps, Community Notes, and Fact Checks as research develops.