Source Tables Do Not Settle Identity

Short Verdict

A source table is a review tool. It can organize records, show contradictions, point to missing evidence, and help a reader see why a claim needs narrower wording.

A source table does not certify identity, ancestry, nationality, tribal enrollment, DNA conclusions, legal status, restitution eligibility, private genealogy, living-community membership, descent, or historical certainty.

The safer public rule is simple: a table can show what each source says. It cannot turn weak evidence into proof.

Target URL

https://staging.thefoundationsof.us/source-tables-do-not-settle-identity/

Meta Description

A TheFoundations source-method guide explaining why templates, captions, citation counts, and source tables organize review but do not certify identity or settle historical claims.

Claim Cluster Being Consolidated

This guide should replace or absorb the public value of these short fact-check cards:

• `https://staging.thefoundationsof.us/fact-check/fact-check-template-certifies-research/`
• `https://staging.thefoundationsof.us/fact-check/fact-check-source-table-settles-identity/`
• `https://staging.thefoundationsof.us/fact-check/fact-check-citation-count-proves-truth/`
• `https://staging.thefoundationsof.us/fact-check/fact-check-caption-counts-as-citation/`

The live source-card pattern reviewed on `2026-07-07` showed the same useful editorial lesson repeated across multiple short pages: a research aid is not a verdict. For AdSense and reader value, this lesson works better as one durable source-method guide than as several thin micro fact checks.

Full Article Draft

TheFoundations uses source tables to slow down claims and make evidence easier to inspect.

That is their value. A source table helps readers see the difference between a public record, a caption, a template, a citation count, a repeated claim, and a supported conclusion. It can show where a record is strong, where it is limited, where the same name may belong to more than one person, and where a claim needs more evidence before it can be reused.

But a table is not proof by itself.

A table is only as strong as the sources placed inside it, the question being asked, and the wording of the conclusion. If the rows are weak, incomplete, repeated, misread, or unrelated to the claim, the table only organizes weakness. It does not settle identity.

The Claim Being Checked

This guide checks four related claims:

• "A completed template certifies the research."
• "A source table settles identity."
• "A citation count proves truth."
• "A caption counts as a citation."

Each claim has the same problem. It treats an organizing device as if it were evidence.

Templates, tables, citation counts, and captions can support a review process. They cannot replace the review process.

What A Source Table Can Do

A source table can be valuable when it is used carefully.

It can:

• identify the exact claim being tested,
• list the sources being used,
• separate primary records from summaries, captions, family notes, database hints, and modern commentary,
• show the date, place, person, institution, or object connected to each source,
• show whether the source supports the full claim or only a narrower statement,
• show contradictions or same-name problems,
• preserve review notes,
• flag sensitive claims for caution,
• point to the next source needed.

This is real publisher value. A table can help a reader understand why a conclusion should be narrowed, delayed, or rejected.

What A Source Table Cannot Do

A source table cannot make a claim true just because the table is complete.

It cannot:

• certify that two same-name people are the same person,
• prove family relationship from a single matching name,
• convert a caption into a source citation,
• convert a citation list into historical proof,
• settle ancestry, nationality, tribe, enrollment, DNA, legal status, restitution, or private genealogy,
• remove privacy and consent issues from living-person or identity-adjacent claims,
• erase contradictions in the records,
• make an unsupported claim safe for public reuse.

When a table is used to certify more than the sources prove, the table becomes a presentation layer for an unsupported claim.

Mistake 1: A Template Certifies Research

A template is a learning aid. It helps the researcher remember which questions to ask.

It does not certify that the answers are correct.

A completed template can still contain:

• missing sources,
• copied claims,
• unclear captions,
• weak citations,
• same-name confusion,
• timeline conflicts,
• place conflicts,
• relationship assumptions,
• private details that should not be published.

Safe wording:

The template records the current review status. It does not certify the claim.

Unsafe wording:

The template is complete, so the identity is confirmed.

Mistake 2: A Source Table Settles Identity

Identity-sensitive claims need more than a row of sources.

A table can show that several records contain similar names, dates, or places. That may be useful. It may also reveal the exact reason the claim is not ready. Similar names are not the same as identity proof. A shared place is not the same as kinship. A repeated family story is not the same as a public source trail.

A stronger identity-adjacent review asks:

• What is the exact claim?
• Does the source name the same person, or only a similar name?
• Does the source connect the person to the same place and time?
• Does it name a relationship directly?
• Does it conflict with another record?
• Does it rely on a modern index, caption, or database hint rather than the record itself?
• Does publishing the claim create privacy or community-status risk?
• Can the public wording be narrowed?

Safe wording:

The table supports a review question about possible same-person evidence. It does not settle identity.

Unsafe wording:

The source table proves this person is the same person across all records.

Mistake 3: Citation Count Proves Truth

Many citations can still point back to the same unsupported claim.

A citation count can tell the reader that a claim has been repeated. It does not tell the reader that the claim has been proven.

Ten citations are weak if they all depend on one unreviewed index entry. Three citations may be strong if they are independent, direct, and tied to the same person, place, date, and relationship. The question is not how many links exist. The question is what each source actually supports.

Useful citation review asks:

• Is the source primary, secondary, or tertiary?
• Is the cited page a record, an index, a caption, a blog post, or a database result?
• Does the citation directly support the exact sentence?
• Are the citations independent, or do they repeat the same source?
• Does the evidence support the full claim or only a narrower statement?

Safe wording:

The citations show where the claim appears. They do not prove the claim unless the underlying sources support it.

Unsafe wording:

This is true because it has many citations.

Mistake 4: A Caption Counts As A Citation

A caption can help identify an image, object, map, chart, table, or record. It is not automatically a source citation.

A useful caption may include a title, creator, date, collection, location, rights note, or source URL. A weak caption may only describe what the viewer is supposed to see. A promotional caption may repeat a claim without showing where the claim came from.

For TheFoundations, a caption becomes useful evidence only when it points the reader to an inspectable source trail.

At minimum, a source-ready caption should include:

• object or record title,
• holding institution or publisher,
• creator when known,
• date or date range,
• location when relevant,
• stable URL or archive reference,
• rights or access note when relevant,
• a narrow statement of what the object shows.

Safe wording:

The caption identifies the object and points to the source trail. The source itself must still be reviewed.

Unsafe wording:

The caption says it, so the historical claim is proven.

A Better Source Table Structure

Use source tables to separate evidence from conclusion.

Recommended columns:

| Column | Purpose | | — | — | | Claim sentence | The exact sentence being tested. | | Source title | The source or object being reviewed. | | Source type | Primary record, image, map, index, caption, article, book, database hint, oral history, or working note. | | Date | The source date or date range. | | Place | The place named in the source, if relevant. | | Person or entity named | The name as written in the source. | | Direct quote or summary | The narrow content the source actually provides. | | What it supports | The safest statement supported by this source. | | What it does not support | The overclaim this source cannot prove. | | Conflict or caution | Same-name issue, date conflict, place conflict, transcription issue, privacy issue, or missing context. | | Review status | Supported, partly supported, needs review, unsupported, misleading, out of scope, or hold. | | Next action | The next source or review step needed. |

The "what it does not support" column is not optional. That column is what prevents a table from becoming a proof display.

Example Source Table Row

Use neutral examples instead of private genealogy or living-person details.

| Claim sentence | Source title | Source type | What it supports | What it does not support | Review status | | — | — | — | — | — | — | | "A person with this name appears in the county record." | County record index entry | Index | A name appears in an index tied to a county and approximate date. | It does not prove same-person identity, relationship, ancestry, legal status, or membership. | Needs review |

This row is useful because it does not overstate the index. It names the narrow support and the limit at the same time.

Evidence Ladder For Identity-Adjacent Claims

TheFoundations should use an evidence ladder before any identity-adjacent wording is published.

1. Exact claim sentence. 2. Source table with source type and source link. 3. Direct record review, not only an index or caption. 4. Date and place consistency. 5. Name comparison with spelling and same-name caution. 6. Relationship evidence where the claim involves family connection. 7. Conflict check against other records. 8. Privacy and sensitivity review. 9. Narrow public wording. 10. Correction path if later evidence changes the conclusion.

If a claim stops at steps 1 through 3, it is usually a research question, not a public conclusion.

Safe Public Wording Patterns

Use language that shows the boundary.

The current source table supports the narrower statement that [source] names [person/place/object/date]. It does not prove [overclaim].

This remains a review question because the current sources do not yet connect the same person, place, date, and relationship.

The citation list shows where the claim appears. It does not show that independent sources prove the claim.

The caption identifies the item for review. It is not a substitute for the holding institution record or source page.

The template is complete enough for internal review, but not enough for public certification language.

Avoid:

confirmed
certified
settled
proves identity
proves ancestry
proves enrollment
proves legal status
DNA proves
restitution proof
family line proven

unless the article is explicitly quoting an outside source and immediately explaining that TheFoundations does not certify that claim.

Editorial Rule

When a claim depends on a source table, TheFoundations should publish the table only with its limits visible.

The page should answer:

• What is the exact claim?
• What source supports the narrowest safe version?
• What part of the claim is not supported?
• What would change the verdict?
• What should the reader avoid repeating?

If those questions are not answered, the table should stay internal, noindexed, or attached to a larger source-method guide.

Source Trail

Policy and readiness sources:

• Google Publisher Policies: `https://support.google.com/adsense/answer/10502938`
• Google AdSense site-readiness guidance: `https://support.google.com/adsense/answer/7299563`
• Google Search spam policies: `https://developers.google.com/search/docs/essentials/spam-policies`

Operational TheFoundations sources:

• TheFoundations sitemap index: `https://staging.thefoundationsof.us/wp-sitemap.xml`
• Representative fact-check card: `https://staging.thefoundationsof.us/fact-check/fact-check-template-certifies-research/`
• Representative fact-check card: `https://staging.thefoundationsof.us/fact-check/fact-check-source-table-settles-identity/`
• Representative fact-check card: `https://staging.thefoundationsof.us/fact-check/fact-check-citation-count-proves-truth/`
• Representative fact-check card: `https://staging.thefoundationsof.us/fact-check/fact-check-caption-counts-as-citation/`
• TheFoundations fact-check publishing standard artifact: `outputs/thefoundations_fact_check_publishing_standard.md`

Source review note:

The reviewed fact-check cards already contain useful cautionary language. Their weakness is not that they are wrong. Their weakness is that they repeat one editorial lesson across several short public URLs. This guide keeps the lesson, adds a stronger source-method explanation, and gives the old URLs a cleaner place to point.

What This Proves

This proves:

• A source table can organize evidence.
• A template can guide review.
• A citation list can show where a claim appears.
• A caption can identify an object or source for inspection.
• The current fact-check cards share one claim-boundary lesson and should be consolidated.
• The consolidated guide gives readers more original value than several short, repeated cards.

What This Does Not Prove

This does not prove:

• that every source table is unreliable,
• that every caption is useless,
• that every short fact-check page should be deleted,
• that a claim is false merely because it needs review,
• that TheFoundations can certify identity, ancestry, nationality, tribal enrollment, DNA conclusions, legal status, restitution eligibility, private genealogy, living-community membership, descent, or family line proof.

The narrow conclusion is that source tools should organize review, not replace proof.

Internal-Link Plan

Add this guide to:

• `/fact-check/`
• `/source-review/`
• `/editorial-standards/`
• `/safe-sharing/` if available
• `/corrections-log/` if available
• `/fact-check-publishing-standard/`
• any source-method, library, or review-template hub

Update the representative old fact-check cards:

• `fact-check-template-certifies-research`
• `fact-check-source-table-settles-identity`
• `fact-check-citation-count-proves-truth`
• `fact-check-caption-counts-as-citation`

Recommended old-card treatment:

• Add a visible note at the top: "This short review card has been consolidated into Source Tables Do Not Settle Identity."
• Link to `/source-tables-do-not-settle-identity/`.
• Keep the old card `noindex,follow` if it remains live.
• Remove the old card from XML sitemaps if it is not expanded above the publication threshold.
• Redirect only when the old page does not need to preserve a separate correction or review history.

AdSense Readiness Notes

This guide is stronger for AdSense review than the separate short cards because it adds original publisher analysis, a clear public method, a source trail, safe wording, and explicit claim boundaries.

Implementation notes:

• Publish this guide as an indexable source-method page only after final editorial review.
• Do not serve ad code on the old short fact-check cards while they remain noindexed or below the publication threshold.
• Remove thin review cards from sitemaps when they are not intended as public search landing pages.
• Keep repeated claim-boundary cards merged into durable guides rather than expanding the site with many near-duplicate pages.
• Add a correction path and last-reviewed date to the public page.
• Keep private genealogy, living-person, and community-status claims out of examples.

Policy alignment:

• Google AdSense readiness guidance emphasizes unique, relevant content and a good user experience.
• Google Publisher Policies restrict ad serving on low-value screens or screens without publisher content.
• Google Search spam policies warn against scaled pages that provide little original value for users.

Correction / Review Note

Review this page after the four representative fact-check cards are updated.

Checklist:

• Confirm whether each old card is noindexed, redirected, or expanded.
• Confirm the new guide is linked from the fact-check hub and source-review pages.
• Confirm no old review card remains in the XML sitemap if it is not publication-ready.
• Confirm the guide uses cautious wording and does not certify identity-sensitive claims.
• Confirm the correction log or review note records the consolidation date.

Suggested visible note:

Review note: This guide consolidates several short fact-check cards about templates, source tables, citation counts, and captions. The consolidation keeps the source-method lesson while making the public page more useful to readers.

Global Guardrail Language

TheFoundations explains public historical evidence, source trails, and claim boundaries. It does not certify identity, ancestry, nationality, tribal enrollment, DNA conclusions, legal status, restitution eligibility, private genealogy, or living-community membership.

Related Guides

One Record Does Not Prove A Family Line, Fact-Check Publishing Standard, and the corrections path.