Loop 073
The genealogical proof loop
A genealogy research workflow that tests one identity, relationship, date, place, migration, or record-linkage claim against source quality and proof evidence.
Ready-to-use prompt
Copy the loop
Resolve exactly one genealogy proof question, such as an identity, relationship, date, place, migration, or record-linkage claim. State the claim, proof standard, target person or family, jurisdiction, date range, known evidence, conflicts, repositories in scope, and unavailable source classes. Build an identity profile, separate original records from derivatives, and choose the next best evidence action: inspect a citation, retrieve one record, correlate records, test a same-name conflict, analyze associates, record a negative search, or mark access blocked. Update source and claim ledgers after each pass. Stop when the claim is proved, disproved, likely, possible, conflicting, unresolved, blocked, or no next source would change the result.
Verify / stop
The proof conclusion follows from cited records, conflicts, and negative searches.
The output includes the updated claim status, identity profile, source ledger, claim ledger, proof note, conflict list, negative-search log, next source if any, and stopping reason.
Context and guidanceWhen to use it, steps, safety notes, and related loops
Use this when
Use this when genealogy work needs to prove or disprove a specific person, relationship, date, place, migration, or record-linkage claim without merging uncertain identities.
How to run it
- State the exact proof question, required standard, known evidence, conflicts, scope, and unavailable source classes.
- Build a compact identity profile from names, dates, places, relatives, associates, occupations, and other distinguishing facts.
- Separate original records, derivative records, indexes, trees, stories, and summaries before drawing conclusions.
- Choose one highest-value evidence action and update source and claim ledgers with reliability and limitations.
- Write a proof note and stop at a clear status, blocker, approval need, or no material next source.
Why it works
Genealogy claims can look proven when similar names, derivative records, or family stories are merged too early; this loop keeps each proof element accountable.
Implementation note
Do not merge possible people, relationships, dates, or places into proved facts. Paid-access repositories, living-person data, and sensitive family information require approval.