Advertise on podcast: Ancestors and Algorithms: AI for Genealogy

How do you find an unknown father among more than 2,000 DNA matches? Sort 20 of them into four grandparent groups with the Leeds Method and AI. In this composite case, Lorraine was born in Brisbane, Queensland, in 1944. Her birth registration left her father's name blank, and her mother told her only one thing: he was a Yank. This episode walks through every step of her search, from match list to a short list of candidates. In this episode you'll learn: - How the Leeds Method sorts AncestryDNA matches between 90 and 400 cM by shared matches - Why to replace every match's name with a code before using AI - A five-rule Claude prompt that sorts matches into clusters and flags bridge matches - The shuffle test: rerun the AI sort with the rows reversed and keep only what holds - How Gemini Notebook names each cluster from your own tree notes, with citations - How Perplexity and DNA Painter's free Shared cM Project tool test a relationship - What Ancestry's Regions by Grandparent (announced October 9, 2026) can and can't tell you - What target testing is, and how to approach possible relatives gently The honest outcome: a partial answer. The DNA made one candidate very unlikely, and two brothers remain. Paper records may not settle it, because the 1973 records fire destroyed an estimated 80 percent of Army personnel files for soldiers discharged between 1912 and 1960. Target testing is the next step. FREQUENTLY ASKED QUESTIONS What is the Leeds Method? The Leeds Method, created by Dana Leeds in 2018, sorts DNA matches sharing 90 to 400 cM into groups using shared matches, so the groups can point to your four grandparent lines. Can AI sort DNA matches with the Leeds Method? Yes, if you give it a coded table of shared matches and written rules. In this episode, Claude sorted 20 coded matches into four groups, set aside one bridge match, and refused to place two matches it had no evidence for. What is a bridge match? A bridge match links into two of your groups at once. It can descend from the couple whose marriage joined those two families, so study it instead of merging the groups. What is the shuffle test for AI DNA sorting? Run the same sorting prompt again in a fresh chat with the rows in reverse order. Keep only the placements that land in the same group both times. Should I put my DNA matches' names into ChatGPT or Claude? This show's rule is no. Give each match a code like M01 and keep the key on paper. The AI only needs the links between matches, not the names of living people. Does 297 cM fit a half niece or a first cousin once removed? In the Shared cM Project 4.0, a first cousin once removed ranges from 102 to 980 cM, so 297 cM fits. A half niece ranges from 492 to 1,315 cM, so 297 cM falls below that range. For Australian and UK researchers: the National Archives of Australia's fact sheet on United States forces in Queensland, Trove for wartime newspapers, and the GRO birth indexes and FreeBMD for England and Wales. The Companion Guide includes the full shuffle-test workflow, an advanced prompt for working a bridge match, a gentle first-message template for target testing, and a GPS Research Checklist for unknown parentage. Find it at ancestorsandai.com. Connect with Ancestors and Algorithms: 📧 Email: [email protected] 🌐 Website: https://ancestorsandai.com/ 📘 Facebook Group: Ancestors and Algorithms: AI for Genealogy - www.facebook.com/groups/ancestorsandalgorithms/ Golden Rule Reminder: AI is your research assistant, not your researcher. Join our Facebook group to share your AI genealogy breakthroughs, ask questions, and connect with fellow family historians who are embracing the future of genealogy research! New episodes every Tuesday. Subscribe so you never miss the latest AI tools and techniques for family history research.

Four records said Hanover, Prussia or Germany, and not one named his village. Here's how to find a German immigrant's village of origin with AI, step by step. When every record says "Germany," the problem is usually the research question, not the records. In this episode, we follow Friedrich Eckhoff, a Lutheran cooper who came from Bremen to Baltimore in 1869 (a composite case built on real record types). You'll learn the method that finally led to his village, one click at a time, with three free AI tools. This episode is for you if: • You're trying to find your German ancestor's village or hometown • Your immigrant's records say only Germany, Prussia or Hanover • You found several towns with the same name and don't know which is yours • You want to use ChatGPT, Perplexity and Gemini in Google AI Studio for genealogy without trusting them blindly FAQ What makes a good genealogy research question? A good research question names one person with identifiers such as age, place and occupation, asks for one fact, and points to a record that could contain that fact. Why does a census say Prussia instead of my ancestor's village? The 1870 U.S. census told enumerators to record the German state, such as Prussia or Bavaria, not a town. Prussia annexed the Kingdom of Hanover in 1866, so one man can appear as "Hanover" in 1870 and "Prussia" in 1880. Which records are most likely to name a German immigrant's village? The church registers of the immigrant's own congregation in America, especially marriage entries, are often the best chance. U.S. censuses, naturalizations before 1906 and 1860s arrival lists usually give only a state or country. Do the Bremen passenger lists survive? Mostly not. From 1875, Bremen kept only the three most recent years of lists, and it reversed that policy in 1907. Survivors are mainly from 1907 and 1908, 1913 and 1914, and 1920 through 1939. How do I tell which same-named German village is the right one? Search Meyers Gazetteer (meyersgaz.org), filter by region, check each place's parish church, then use witnesses and sponsors from family records. In this episode, a wedding witness's village narrowed eight Neuenkirchens in the province of Hanover to one. Can AI find my ancestor's German village for me? Not on its own. When asked directly, ChatGPT listed two to four Neuenkirchens and missed the right one both times. AI helped most by interviewing for a better question, sorting which records could answer it, and transcribing old German handwriting, with every claim checked against its source. The honest outcome: an 1846 baptism names Friedrich, son of Hinrich Eckhoff, in the one Neuenkirchen in his wedding witness's district. It's strong evidence but not airtight, because at least one other Neuenkirchen has no church book images online. Australian and UK listeners: the same approach works with the NSW assisted immigrant lists, which often record a native place, and the 1851 census, the first to record parish of birth, with free transcriptions on FreeCEN. AI is your research assistant, not your researcher. Want to go deeper? The Companion Guide at ancestorsandai.com includes the full Question Card workflow, a same-named village sorting prompt and a GPS Research Checklist for finding a place of origin. Connect with Ancestors and Algorithms: 📧 Email: [email protected] 🌐 Website: https://ancestorsandai.com/ 📘 Facebook Group: Ancestors and Algorithms: AI for Genealogy - www.facebook.com/groups/ancestorsandalgorithms/ Golden Rule Reminder: AI is your research assistant, not your researcher. Join our Facebook group to share your AI genealogy breakthroughs, ask questions, and connect with fellow family historians who are embracing the future of genealogy research! New episodes every Tuesday. Subscribe so you never miss the latest AI tools and techniques for family history research.

Two men named Giovanni Farruggia registered for the World War I draft in Tampa on the same day in 1917. An online family tree fused them into one ancestor. Identity separation for genealogists: how to tell two same-name ancestors apart with ChatGPT, Claude and Gemini Notebook, using a Sicilian case from Ybor City, Tampa. This episode is for you if: You attached a record because the name matched and something feels off. Your ancestor seems to live in two houses in the same year. You suspect a FamilySearch or Ancestry tree merged two people. Your Italian, Sicilian or immigrant family reused the same names every generation. What you'll learn: The four-step identity separation method: plan the identifiers, gather every record of the name, count the people, then trace every tree fact to its owner. Why birthplace, occupation and arrival year are weak identifiers for cousins from one village. The collision test: two records that can't describe one man on one day prove two men. How a census citizenship column led to a naturalization petition that settled the case. Click-by-click setup: a ChatGPT temporary chat set to Unpersonalized, a Claude incognito chat, and Gemini Notebook (formerly NotebookLM) with one record per source. Questions this episode answers: How do I tell if two ancestors with the same name are the same person? Count before you claim. Look for collisions: two records made on the same day or in the same census that list different birth dates, addresses, wives or households. One collision proves two people. No collision proves nothing. Can AI help separate two people with the same name in a family tree? Yes, if you make it show its work. A blind Claude chat sorted ten records into two men and named its own weakest link. Gemini Notebook traced each tree fact to the man it came from, with clickable citations. Is a birthplace enough to identify an ancestor? No. Historians say Santo Stefano Quisquina supplied more than sixty percent of Tampa's Italians, so two cousins could share a village, a trade and an arrival year. How do I know if an online family tree merged two people? Trace every fact back to its source. Here the birth date and parents came from a grocer born in 1893. The wife and children came from a cigar maker born in 1895. What census column can point to naturalization records? Citizenship. The cigar maker was an alien in 1920 and naturalized by 1930, which led to his 1928 petition with his exact birth date, address, wife and children. The honest outcome: the tree's one Giovanni was two men. Rosalia's husband was identified. His father is probable and his mother is still unproved. Both AI tools made the same slip, reading "son of the head" as naming both parents. The family is a composite built from real Tampa record types. For Australian and UK listeners: the same method works with First World War service records at the National Archives of Australia, Trove, the 1939 Register for England and Wales, and FreeBMD. The Companion Guide adds advanced prompts for a side-by-side identity table and for untangling a tree merged more than once. Find it at ancestorsandai.com. Connect with Ancestors and Algorithms: 📧 Email: [email protected] 🌐 Website: https://ancestorsandai.com/ 📘 Facebook Group: Ancestors and Algorithms: AI for Genealogy - www.facebook.com/groups/ancestorsandalgorithms/ Golden Rule Reminder: AI is your research assistant, not your researcher. Join our Facebook group to share your AI genealogy breakthroughs, ask questions, and connect with fellow family historians who are embracing the future of genealogy research! New episodes every Tuesday. Subscribe so you never miss the latest AI tools and techniques for family history research.

No record names her parents, and you can still prove them. This episode shows how, step by step, with 5 ordinary records and 3 free AI tools. Every family tree has a woman like Nancy Brockway: a first name, a married surname, and nothing before that. Our case is a composite family built from real 1850s New York record types. Nancy lived in New Berlin, Chenango County, and was born about 1816 in Otsego County. There's no marriage record and no will. There is a Hannah Pettibone, 67, in her 1850 household, and an 1847 deed that puts Nancy's name on a dead man's farm. WHAT YOU'LL LEARN - How to find a woman's maiden name with no marriage record - Why most New York marriages before 1847 left no government record - What the 1855 New York State census tells you that the 1850 census doesn't - How to search old deeds with FamilySearch Full-Text Search - How to transcribe a handwritten deed with Gemini in Google AI Studio - How to run a blind read in a Claude incognito chat, so AI can't confirm your bias - The knockout test: remove one record at a time to see what your case rests on FREQUENTLY ASKED QUESTIONS Can you prove a parent-child relationship when no record states it? Yes. Indirect evidence, several records that together leave one reasonable explanation, is fully acceptable under the Genealogical Proof Standard. Why can't I find a marriage record for my New York ancestor before 1847? According to the FamilySearch Research Wiki, no county, city, town or village government in New York recorded marriages before 1847. Statewide registration began in 1880 and 1881. How can a deed reveal a woman's maiden name? When a man died owning land and no one went to court, his heirs often settled it by deed. A married daughter may appear beside her husband with words like "in right of the said Nancy," meaning the share was hers, not his. What is a blind read with AI? You give a chatbot your records but not your theory, in a fresh incognito or temporary chat, and ask for every explanation the records allow. In this episode, Claude raised one I hadn't considered: stepmother. What is the knockout test in genealogy? Remove one record at a time and ask whether your conclusion still stands. Split your conclusion into single claims first. Claude overreached when it tested a two-part claim. Can I trust ChatGPT to tell me which genealogy records exist? Use it to brainstorm, then check every record type in the FamilySearch Research Wiki. In this episode, ChatGPT pointed to early county marriage records that don't exist for 1830s New York. THE HONEST RESULT A partial answer. The evidence best supports Nancy as a daughter of Stephen Pettibone. Whether Hannah was her mother or her stepmother is still open, and I name the record that could settle it. Australian and UK listeners: the same approach works with the NSW Historical Land Records Viewer and the National Library of Wales's wills proved before 1858. Patreon members: this episode's Companion Guide includes the full blind read and knockout workflow, plus advanced prompts for turning your results into a written proof summary. Find it, and every prompt from this episode, at ancestorsandai.com. Connect with Ancestors and Algorithms: 📧 Email: [email protected] 🌐 Website: https://ancestorsandai.com/ 📘 Facebook Group: Ancestors and Algorithms: AI for Genealogy - www.facebook.com/groups/ancestorsandalgorithms/ Golden Rule Reminder: AI is your research assistant, not your researcher. Join our Facebook group to share your AI genealogy breakthroughs, ask questions, and connect with fellow family historians who are embracing the future of genealogy research! New episodes every Tuesday. Subscribe so you never miss the latest AI tools and techniques for family history research.

Texas did not register deaths statewide until 1903, so if your ancestor died there in the 1890s, no death certificate was ever created. This week, a county tax roll dated one anyway. Cyril Sebesta came to Fayette County, Texas from Moravia in 1873 and bought eighty acres in 1881. His headstone carries a birth year and nothing else. Three generations left a question mark in the death column. The record that finally narrowed it never mentions his death or his burial. This is a Partial Answer episode. The window closed from ten years to about twelve months, and it stops short of calling that proof. Negative evidence is suggestive, never conclusive. WHAT YOU WILL LEARN How to date a death when no death record was ever created Why searching a FamilySearch collection by name is not the same as searching the records The three gates that turn an absence into evidence Why a four-state research grid beats a three-state one How to stop AI from turning "I did not find it" into "it is not there" Free-tier workflows in Perplexity with Comet, Gemini Notebook, and Claude FREQUENTLY ASKED QUESTIONS How do I find a death date when there is no death certificate? Find a record created every year regardless of events, such as a county tax roll, a city directory, or an electoral roll, then look for the year your ancestor stops appearing in it. An annual series can narrow a death to a single year, where a ten-year census only narrows it to ten. When did Texas start registering deaths? Statewide registration of births and deaths in Texas began in 1903, and compliance was not universal at first, with rural counties lagging the cities. There is no state death certificate to order for a Texas death in the 1890s. What is negative evidence in genealogy? Negative evidence is a conclusion drawn from the absence of information where it should have appeared. It is not the same as a negative search result, which only means you looked and found nothing. Elizabeth Shown Mills calls it contextually suggestive silence. Is searching a FamilySearch collection the same as searching the records? Often not. The collection "Texas, County Tax Rolls, 1837-1910" carries a selective index covering 231 of 254 counties and only about nine years out of a seventy-year run. The rest of the images are browsable but unindexed, so a name search cannot see them. Can AI tell the difference between a missing record and one I have not searched? No. An AI tool has never seen the shelf, so it cannot separate a record that is absent from one you have not opened. That distinction has to come from you, which is why this episode uses a four-state grid instead of a three-state one. Why do Czech surnames change spelling in American records? The hacek, the small hook over the s in Sebesta, does not exist on an American pen, so clerks wrote what they heard. One family can appear as Sebesta, Shebesta, and Sebasta across three years of one record series. Identify the person by the land, not by the name. Which AI tools does this episode use, and are they free? Perplexity with Comet for record survival research, Gemini Notebook for source-grounded tabulation, and Claude for testing the argument. All three workflows run on free tiers. Gemini Notebook was renamed from NotebookLM in July 2026 and now lives at notebook.google.com. FOR AUSTRALIAN AND UK LISTENERS The same method runs on Australian electoral rolls and the digitised newspapers on Trove, and on English parish and borough rate books at the county record offices, with electoral registers on Findmypast and Scottish records on ScotlandsPeople. The Companion Guide for this episode includes the full absence grid workflow, advanced prompts, and a GPS Research Checklist built for negative evidence. It is all at ancestorsandai.com. Connect with Ancestors and Algorithms: 📧 Email: [email protected] 🌐 Website: https://ancestorsandai.com/ 📘 Facebook Group: Ancestors and Algorithms: AI for Genealogy - www.facebook.com/groups/ancestorsandalgorithms/ Golden Rule Reminder: AI is your research assistant, not your researcher. Join our Facebook group to share your AI genealogy breakthroughs, ask questions, and connect with fellow family historians who are embracing the future of genealogy research! New episodes every Tuesday. Subscribe so you never miss the latest AI tools and techniques for family history research.

Most genealogists audit a family tree by hunting for blanks. The dangerous conclusions are the ones that already have a source attached. In this episode, Brian builds a fifteen-person test GEDCOM with five deliberately planted errors, then turns AI loose on it to see how many it catches. Four found. One missed. And the one it missed was the most dangerous error in the file. This is the opposite of how the genealogy world is using AI right now. Everyone is running it forward to find new ancestors. This episode runs it backward, at conclusions you already made and never revisited. You will learn the Blast Radius Method: how to rank every unsupported parent-child link in your tree by how many people collapse if that link is wrong, so you work the conclusions that matter instead of the ones that are easy. Tools used: Claude, Gemini Notebook. All on free tiers. WHAT YOU WILL LEARN How to export a GEDCOM and audit it without giving any tool write access to your treeWhy a census can never establish a birth date, and what it actually provesThe difference between a fact that is sourced and a fact that is supportedWhy unsourced facts are honest and sourced facts are the hazardHow to build a research queue sorted by consequence instead of by alphabet FREQUENTLY ASKED QUESTIONS Can AI find errors in my family tree? Yes, but only the kinds of errors you ask it to look for. In this episode's controlled test, AI caught four of five deliberately planted errors and missed an inadequate citation until asked about citations specifically. A clean report means your questions came back clean, not that your tree is clean. What is the Blast Radius Method? It is a way of prioritizing genealogy research by consequence. You rank every parent-child link in your tree by the number of descendants who depend on it, then work the links with the most people hanging off them and the least evidence behind them first. Can I use AI to analyze a GEDCOM file? Yes. A GEDCOM is plain text, so tools like Claude and Gemini Notebook can read it directly with no conversion. Export a branch rather than a whole tree, strip living people first, and treat every finding as a question to research rather than a defect to fix. Does a census prove a birth date? No. A census records an age as of the official census day, reported by an unknown household informant. The 1880 census day was June 1, 1880. A birth year derived from a census carries at least a two-year range and should never be cited as a birth date. Is a source citation the same as evidence? No. A citation is a promise that evidence exists, made by whoever typed it. A citation can be real, correct, and still inadequate for the specific fact it is attached to. A death certificate is primary evidence for the death and derivative evidence for the birth. Why is FamilySearch unable to export a GEDCOM? FamilySearch Family Tree does not offer direct GEDCOM export. To get your data into a file, you have to use one of FamilySearch's certified partner programs and export from there. THE HONEST OUTCOME The audit did not produce a clean tree. It produced a queue. And the discovery was uncomfortable: the parts of the test file that looked documented were carrying more hidden risk than the parts that were visibly blank, because a source badge is a permission slip to stop looking. Remember: AI is your research assistant, not your researcher. Companion Guide members get the full twelve-prompt audit chain, a citation adequacy table covering nineteen record classes, and a GPS Research Checklist built around evidence you already have. Connect with Ancestors and Algorithms: 📧 Email: [email protected] 🌐 Website: https://ancestorsandai.com/ 📘 Facebook Group: Ancestors and Algorithms: AI for Genealogy - www.facebook.com/groups/ancestorsandalgorithms/ Golden Rule Reminder: AI is your research assistant, not your researcher. Join our Facebook group to share your AI genealogy breakthroughs, ask questions, and connect with fellow family historians who are embracing the future of genealogy research! New episodes every Tuesday. Subscribe so you never miss the latest AI tools and techniques for family history research.

A Marine killed at Tarawa in 1943 was declared non-recoverable in 1949, but DNA proved eighty-one years later he had actually been buried within days. It was the paperwork that failed him, not the men who buried him. This episode is for you if you've hit a record whose final-sounding language you never verified, if your family tree has a WWII, Korean, or Vietnam War service member whose fate was never fully confirmed, or if you want to see Gemini Notebook, Claude, and Perplexity with the Comet browser used together on one real research problem, start to finish. What you'll learn: - How to test a record's administrative language instead of accepting it at face value - How to correlate a personal service record against unit-level records to find a documented historical pattern - How modern military DNA identification actually works, and who in a family is a valid reference sample - How the Defense POW/MIA Accounting Agency and its partner History Flight are still identifying WWII remains today Frequently Asked Questions What does "non-recoverable" mean on a WWII military record? Non-recoverable is an official U.S. military case designation meaning remains could not be located or matched to a name. It does not mean no burial or recovery effort ever occurred, though families have long read it that way. How does DNA identify unidentified WWII remains? The Defense POW/MIA Accounting Agency primarily uses mitochondrial DNA, passed from a mother to all her children but carried forward only by daughters, combined with anthropological and dental analysis, to match remains against a family reference sample. Can AI tools like Claude and Gemini Notebook actually help with genealogy research? Yes. In this episode, Gemini Notebook builds a citation-backed timeline from uploaded military documents, Claude compares conflicting records to explain a contradiction, and Perplexity, using Comet, verifies the theory against current, sourced information. Why did so many Marines killed at Tarawa remain unaccounted for? Wartime construction on the tiny island of Betio disrupted cemetery markers before a full recovery could be completed in 1946. Excavations beginning around 2015 have since located dozens of graves the original recovery never found. Were Marine Corps personnel records affected by the 1973 National Personnel Records Center fire? No. That fire destroyed a majority of Army and Air Force personnel files from the affected decades, but Navy, Marine Corps, and Coast Guard records were stored separately and were largely spared. How can I find out if a missing WWII relative has been identified? Check DPAA's free "Our Missing" search tool and "Recently Accounted For" list at dpaa.mil, or ABMC's free Burials and Memorializations database at abmc.gov, which adds a bronze rosette next to a name once DPAA confirms an identification. Australian listeners: the Army's Unrecovered War Casualties unit covers more than 30,000 missing Australians from the World Wars. UK listeners: the Ministry of Defence's Joint Casualty and Compassionate Centre, the War Detectives, does the same for missing British service members. This is an Unexpected Discovery episode. The family's eighty-one-year fear that nothing had ever been recovered turned out to be wrong, though the paperwork failure behind it is real and still affects hundreds of similar cases today. A Companion Guide with twelve advanced AI prompts, a full document-comparison workflow, and a GPS Research Checklist built specifically for military identification cases is available at ancestorsandai.com. Connect with Ancestors and Algorithms: 📧 Email: [email protected] 🌐 Website: https://ancestorsandai.com/ 📘 Facebook Group: Ancestors and Algorithms: AI for Genealogy - www.facebook.com/groups/ancestorsandalgorithms/ Golden Rule Reminder: AI is your research assistant, not your researcher. Join our Facebook group to share your AI genealogy breakthroughs, ask questions, and connect with fellow family historians who are embracing the future of genealogy research! New episodes every Tuesday. Subscribe so you never miss the latest AI tools and techniques for family history research.

A family told the same story about a 1948 move for nearly eighty years. One recorded interview and three AI tools changed that. Effie Napier is eighty-eight, and by her family's account, the last person alive who actually remembers why they left the West Virginia coal fields for Dayton, Ohio. The story everyone told was simple: better money, a fresh start. It's the version repeated at every reunion. Then her grandson sat down with a recorder and one question built from an actual document instead of a guess. What came back wasn't the story anyone expected, including Effie, who had quietly carried the real reason alone for most of her life. This episode (using a composite case built from the kind of families and records this show sees constantly) walks through the full technique end to end: researching a relative's world with Perplexity before writing a single question, turning that research into interview questions with Claude specific enough to unlock a real memory instead of a rehearsed one, and recording, transcribing, and fact-checking the interview with Gemini Notebook, including the two-hundred-megabyte file limit that can ruin an afternoon if you don't know about it going in. This is for you if you have a living relative who remembers something your documents never will, and you want an actual method for capturing it before it's gone, not only a recorder and good intentions. FAQ What AI tools are used in this episode? Perplexity with Comet for historical research, Claude for building interview questions from documented facts, and Gemini Notebook for transcribing and analyzing the recorded interview. Is NotebookLM the same as Gemini Notebook? Yes. Google renamed NotebookLM to Gemini Notebook on July 16, 2026. It is the same product, the same notebooks, and the same underlying tool, only a new name and logo. How large can an audio file be for Gemini Notebook? The limit is two hundred megabytes per file, not a fixed number of minutes. A typical compressed recording (MP3 or M4A) can run several hours and stay under that limit. The same length recorded as an uncompressed WAV file can exceed two hundred megabytes in under thirty minutes. What questions should I ask when interviewing an elderly relative? Specific questions built from documented facts, not general prompts like "tell me about your childhood." A question tied to a real date, document, or event produces a far more detailed and useful answer. For Australian and UK listeners: the same technique applies to any internal migration story in your own family history, whether your research draws on Trove, ScotlandsPeople, or The National Archives. Honest outcome, by the show's own Genealogical Proof Standard scoring: an unexpected discovery. The facts of the timeline confirmed cleanly. What they confirmed underneath the timeline was harder and more human than anyone went looking for. The free episode covers the full technique start to finish. The Companion Guide adds twelve advanced prompts for building a repeatable oral history research practice, including how to cross-reference multiple interviews and prepare your findings for your family tree software. Find both at ancestorsandai.com. Connect with Ancestors and Algorithms: 📧 Email: [email protected] 🌐 Website: https://ancestorsandai.com/ 📘 Facebook Group: Ancestors and Algorithms: AI for Genealogy - www.facebook.com/groups/ancestorsandalgorithms/ Golden Rule Reminder: AI is your research assistant, not your researcher. Join our Facebook group to share your AI genealogy breakthroughs, ask questions, and connect with fellow family historians who are embracing the future of genealogy research! New episodes every Tuesday. Subscribe so you never miss the latest AI tools and techniques for family history research.

In 1836, a Yorkshire parish legally removed a laborer to a village he'd probably never lived in, over his father's old apprenticeship. This episode uses Claude, Gemini, and ChatGPT to trace an English settlement dispute through parish chest records most genealogists never open. This episode is for you if: - You have English ancestors and don't know where to start before 1837 - You've heard the term "parish chest" and want to know what's actually in one - You want to see Claude, Gemini, and ChatGPT used for real genealogy research, not generic AI tips - You're trying to understand English Poor Law, settlement, and removal records What you'll learn: - Why the GRO index cannot help you before July 1, 1837, and what to search instead - What a settlement examination and removal order actually are, and why parishes created them - How Gemini via Google AI Studio transcribes period handwriting, and which free model to pick - Why an 1836 case used a 174-year-old legal mechanism most people assume ended with Victorian workhouse reform - How to use ChatGPT for archive research strategy, not just brainstorming FREQUENTLY ASKED QUESTIONS Does the GRO index have birth records for someone born before 1837? No. Civil registration in England and Wales began on July 1, 1837, so anyone born earlier has no GRO birth record at all. Parish baptism registers are the correct record type before that date. What is a settlement examination in English genealogy? A settlement examination was a formal, sworn interview conducted by parish officials to determine which parish was legally responsible for a person if they became poor. The mechanism was created by the Settlement Act of 1662, not the older 1601 Poor Relief Act many people assume covers it. Did settlement and removal records stop after the Poor Law Amendment Act of 1834? No. The 1834 Act reorganized day-to-day poor relief into larger Poor Law Unions, but which parish was legally responsible for a specific person stayed a parish-by-parish decision until 1865. An 1836 removal order still came from an individual parish, not a Union. Can Gemini transcribe old handwritten genealogy documents for free? Yes. Gemini 3 Flash, free through Google AI Studio, performs close to human-level accuracy on legible nineteenth-century handwriting. Current testing shows the free Flash model holding up as well as, or sometimes better than, the paid Gemini Pro tier for this specific task. Can ChatGPT's free tier build a custom GPT in 2026? No. As of 2026, creating and publishing a custom GPT requires a paid ChatGPT plan. The free tier still supports unlimited text conversations, enough for research strategy and archive brainstorming. What was the Dewsbury Poor Law Union? Formed in January of 1837, the Dewsbury Poor Law Union grouped the parishes of Dewsbury, Batley, Mirfield, Thornhill, West Ardsley, and part of Birstal for administering relief under the new system. UK listeners, this one is your home turf: search the GRO's own index at gro.gov.uk, and check whether The National Archives or your county record office holds parish chest material for your ancestor's parish. Australian listeners with English-origin ancestors, Trove is worth checking for newspaper mentions of arrivals from a specific parish. This is an Unexpected Discovery, not a full breakthrough, and we say so plainly: the trail goes cold after 1836, and we don't know what happened to Amos next. Sometimes the honest answer to a four-generation mystery is smaller than the mystery itself, and that's still a real result. Want the twelve-prompt Advanced version, the exact workflow for tracing a settlement dispute through parish chest material, and a GPS Checklist for English civil and parish records? The Companion Guide has it all, plus every episode, at ancestorsandai.com. Connect with Ancestors and Algorithms: 📧 Email: [email protected] 🌐 Website: https://ancestorsandai.com/ 📘 Facebook Group: Ancestors and Algorithms: AI for Genealogy - www.facebook.com/groups/ancestorsandalgorithms/ Golden Rule Reminder: AI is your research assistant, not your researcher. Join our Facebook group to share your AI genealogy breakthroughs, ask questions, and connect with fellow family historians who are embracing the future of genealogy research! New episodes every Tuesday. Subscribe so you never miss the latest AI tools and techniques for family history research.

A Jewish ancestor's hometown was spelled three different ways across three documents. A 1985 algorithm and three AI tools narrowed it down. This episode shows exactly how, and exactly where the method stops working. This episode is for you if you are researching Eastern European Jewish ancestors, if a hometown name on an old document does not match any map you can find, or if you want to see how Claude, Gemini, and NotebookLM actually perform on real historical documents rather than a marketing demo. You will learn: How the Daitch-Mokotoff Soundex system, built in 1985 specifically for Eastern European Jewish names, still powers the free JewishGen Communities Database todayWhy Ellis Island inspectors did not change immigrants' names, and where name changes actually happened insteadHow to use Gemini via Google AI Studio to transcribe messy historical handwriting, and how to read its uncertainty flagsHow to use Claude to weigh competing candidate towns against the evidence, and what it takes to turn a strong guess into a confirmed factHow to use NotebookLM to correlate multiple documents with citations, and why that matters when no single source closes the gapFREQUENTLY ASKED QUESTIONS What is Daitch-Mokotoff Soundex? Daitch-Mokotoff Soundex is a phonetic name-matching system built in 1985 by Gary Mokotoff and Randy Daitch specifically to handle the spelling variation common in Eastern European Jewish surnames and place names. It still powers JewishGen's free Communities Database today. Did immigration officials at Ellis Island change immigrants' names? No. Ellis Island inspectors worked from passenger manifests already prepared by the shipping line in Europe and did not write names down for the first time. When a name changed, it typically happened later, at the hands of the immigrant or a naturalization clerk. How accurate is Gemini at transcribing old handwritten documents? As of August 2026, independent testing on eighteenth and nineteenth century English-language handwriting has measured Gemini's character error rate at around one to two percent. Early Russian-language testing has been promising too, though not yet benchmarked as rigorously. What is the JewishGen Communities Database? It is a free, Soundex-searchable database that lets researchers search for a place name phonetically rather than by exact spelling, then filter results by province and by historical Jewish population, useful when a name has been transliterated inconsistently across records. Can AI tools confirm an ancestor's exact hometown? Not always, and this episode is honest about that. AI tools can narrow a list of real candidates and help weigh which one is best supported by the evidence, but confirming an exact match usually still requires a document that names the specific family in connection to that place. What AI tools are featured in this episode? Claude, for comparing and reasoning across multiple transcribed documents. Gemini via Google AI Studio, for handwriting transcription. NotebookLM, for source-grounded correlation across every document gathered, each claim cited to its source. For my Australian and UK listeners: this same wave of Eastern European Jewish emigration built major communities in Melbourne, Sydney, and London's East End. The same free Daitch-Mokotoff Soundex search works from anywhere in the world, and the National Archives of Australia and The National Archives in the UK are essential next steps once a place name is narrowed down. An honest note on the outcome: this is a Brick Wall episode. The leading candidate town is well supported but not confirmed, and the episode says so plainly rather than dressing up a strong guess as solved. For a deeper walkthrough of this exact technique, including additional advanced prompts and record-collection guidance for Eastern European Jewish research, the Companion Guide for this episode is available at ancestorsandai.com. Connect with Ancestors and Algorithms: 📧 Email: [email protected] 🌐 Website: https://ancestorsandai.com/ 📘 Facebook Group: Ancestors and Algorithms: AI for Genealogy - www.facebook.com/groups/ancestorsandalgorithms/ Golden Rule Reminder: AI is your research assistant, not your researcher. Join our Facebook group to share your AI genealogy breakthroughs, ask questions, and connect with fellow family historians who are embracing the future of genealogy research! New episodes every Tuesday. Subscribe so you never miss the latest AI tools and techniques for family history research.

Episode 50, The AI Lab: Brian tests four AI features built directly into FamilySearch and Ancestry, using a five-question trust rubric built live with Claude, to find out which ones you can actually trust with your family tree. One of the four had not even shipped yet when this episode was first outlined, which becomes part of the story you'll hear. THIS EPISODE IS FOR YOU IF YOU HAVE SEARCHED: Is FamilySearch's AI Research Assistant accurate? Can you trust AncestryAI's AI Stories feature? What is Ancestry's new Get Ideas tool? Should I use AI on my family tree? How do I know if a genealogy AI answer is wrong? Is Ancestry's AI free or does it need a subscription? Does FamilySearch's AI work outside the United States? What's the difference between FamilySearch Simple Search and the AI Research Assistant? WHAT YOU WILL LEARN: How to build a five-question trust rubric you can run against any AI research assistant, present or future, in under two minutes.How to catch a confidently wrong AI answer before it gets written into your tree, using the same method that caught a false claim in this episode.Why FamilySearch's AI Research Assistant is not yet available in every country, confirmed directly from FamilySearch's own support team, and what to do if you're one of the researchers it hasn't reached yet.What a real, documented AI mixup on another genealogist's own family tree can teach you before the same thing happens on yours.How to tell the difference between an AI tool that shows its sources and one that only sounds like it does.THE FOUR AI FEATURES TESTED: FamilySearch's Simple Search, a free natural-language search experiment currently in FamilySearch Labs. FamilySearch's AI Research Assistant, which scans your existing tree and hints for possible missing relatives, and flags them right on your homepage. Ancestry's AncestryAI, which turns a single record into a narrated, AI-written story, still labeled beta. Ancestry's Get Ideas, a brand-new beta feature, launched in late June 2026, that suggests what to research next based on a person's existing records and family connections. IN THIS EPISODE: Brian opens by revisiting Hazel Kirby, a research problem introduced in Episode 49 that was never fully solved: a woman who appears once in a 1920 Chicago city directory, working and living independently, then vanishes from the record for twenty years. Before touching any AI tool, he builds a five-question trust rubric live with Claude. He then runs FamilySearch's Simple Search and AI Research Assistant against Hazel's case, followed by Ancestry's AncestryAI and its newly launched Get Ideas feature, scoring each one against the same five questions. Along the way, he uses Perplexity to verify what's actually changed about these tools since the episode was first outlined, and cites a real, documented AI error from another genealogist's own research to show the risk is not hypothetical. FREQUENTLY ASKED QUESTIONS FROM THIS EPISODE: Is FamilySearch's AI Research Assistant free? Yes. All of FamilySearch's tools, including this one, are free, the same as the rest of the site. Is FamilySearch's AI Research Assistant available worldwide? Not yet. FamilySearch's own support team has confirmed there is no release date yet for the UK, with the feature currently centered on the US and Canada. Is Ancestry's AncestryAI free? The lighter context questions and the record summarizer are part of the standard Ancestry experience; the deeper AI Stories audio narration requires an active subscription. Can AI on genealogy sites be wrong? Yes, and this episode shows exactly how, using both a constructed test case and a real, documented example from a working genealogist's own research. What is the Genealogical Proof Standard? A five-element professional framework genealogists use to evaluate evidence. This episode maps a simplified version of it onto AI tool testing, and the full five-element checklist is in the Companion Guide. What is Ancestry's Get Ideas feature? A beta tool, launched June 29, 2026, accessed through a sparkle icon on an ancestor's profile page. It reviews a person's existing records and family connections and suggests research directions, tags, and timeline descriptions. Does FamilySearch's AI ever get things wrong? Yes. This episode is upfront about real, documented community reports of the AI Research Assistant suggesting incorrect family matches, alongside the ways it gets things right. What tools does Ancestors and Algorithms use most often? Claude for reasoning and document analysis, Perplexity and Comet for current web research, Gemini for handwriting transcription, ChatGPT for brainstorming, and NotebookLM for source-grounded organization, rotated episode to episode based on what the research task actually needs. THE HONEST OUTCOME: Hazel Kirby's brick wall from Episode 49 is still not fully solved. One tool surfaces a real, sourced, still-unconfirmed lead worth chasing next season, a possible 1926 Cook County marriage record. Another states a false claim about her death with total confidence, the same kind of error genealogist Randy Seaver independently caught and published about his own family tree months before this episode was recorded. You will hear exactly how to tell a trustworthy AI answer from a dangerous one, on any tool, at any time, including ones that do not exist yet. RESEARCHING FROM AUSTRALIA OR THE UK? This episode covers whether FamilySearch's and Ancestry's AI features are actually live in your account yet, plus how to run the same five-question trust test against your own country's major archives, including Trove, the National Archives of Australia, and ScotlandsPeople. GO DEEPER WITH THE COMPANION GUIDE: This free episode stands entirely on its own. For listeners who want to take it further, the Companion Guide includes a printable version of the five-question trust rubric, five intermediate prompts for Patreon members built around the exact obstacles you'll hit trying these tools on your own research, and twelve advanced prompts for stress-testing any platform AI feature against the full Genealogical Proof Standard, twenty prompts in total built from this single episode. Full show notes, the Companion Guide, our private community, and every past episode live at ancestorsandai.com. ABOUT ANCESTORS AND ALGORITHMS: Ancestors and Algorithms is a weekly podcast where family history meets artificial intelligence, hosted by Brian. Every episode pairs a real genealogy research problem with copy-paste AI prompts you can use immediately, built around the professional Genealogical Proof Standard, with an honest mix of breakthroughs and brick walls. New to the show? Start with any episode; each one stands completely on its own. The Golden Rule of this show, and the whole point of today's episode: AI is your research assistant, not your researcher. Connect with Ancestors and Algorithms: 📧 Email: [email protected] 🌐 Website: https://ancestorsandai.com/ 📘 Facebook Group: Ancestors and Algorithms: AI for Genealogy - www.facebook.com/groups/ancestorsandalgorithms/ Golden Rule Reminder: AI is your research assistant, not your researcher. Join our Facebook group to share your AI genealogy breakthroughs, ask questions, and connect with fellow family historians who are embracing the future of genealogy research! New episodes every Tuesday. Subscribe so you never miss the latest AI tools and techniques for family history research.

Ancestors and Algorithms Episode 49, "The Research Assistant That Remembers," teaches genealogists how to build a persistent AI research assistant across three free tools: Claude Projects, Gemini Gems, and ChatGPT Custom Instructions, so you stop re-explaining your family history case to a brand new chat every single session. Host Brian walks through the exact custom instructions he wrote into each AI tool, with the Genealogical Proof Standard's Golden Rule, AI is your research assistant, not your researcher, written directly into the assistant's own settings instead of repeated by hand every time you sit down to research. He tests the build against a constructed case designed to stress it: a Chicago city directory entry from 1920, then twenty years of silence, then a reappearance in 1940 under a possibly different surname. This episode is for you if you have ever: Retyped the same family background into a new AI chat every time you sat down to research your family treeWondered whether Claude, Gemini, or ChatGPT can actually remember a genealogy case between sessionsSearched for how to build an AI research assistant for family history using free toolsWanted a real, tested answer on Claude Projects, Gemini Gems, or ChatGPT Custom Instructions for genealogy research, not only a feature listAsked whether AI tools for genealogy actually hold up, or only sound convincing In this episode, you will learn: How to write AI assistant instructions that hold up under real pressure, not only instructions that sound carefulHow to test whether your AI research assistant is actually following its own guardrails, instead of only agreeing that it willContext loading, tool chaining, multi-document comparison, and verification choreography, four techniques used across a genuine multi-tool workflowWhich free tier limits actually apply to Claude Projects, Gemini Gems, and ChatGPT Custom Instructions as of this recording, and how to work within themHow the Genealogical Proof Standard's five elements, reasonably exhaustive research, source citations, analysis and correlation, resolution of conflicting evidence, and a soundly reasoned written conclusion, show up naturally in an AI-assisted research session For Australian listeners, this same persistent-assistant technique applies directly to convict and immigration research through Findmypast. For UK listeners, it applies to government and military records through The National Archives, or to Scottish lines through ScotlandsPeople. The tool does not care which country's archives it is helping you organize. This is an honest Partial Answer episode, one of the outcome types this show tracks openly alongside Full Breakthroughs, Unexpected Discoveries, and Brick Walls. The AI assistant technique itself is fully validated and ready to build today, for free, in about fifteen minutes. The twenty-year gap in the case built to test it stays open on purpose, because Ancestors and Algorithms does not manufacture a clean ending the evidence has not actually earned. Brian brings over a decade of hands-on genealogy research experience and more than a thousand hours of direct AI tool use to every episode, translating AI capability into research methodology genealogists can trust and verify for themselves. The free episode stands on its own with everything you need to start today. For the exact instructions used in all three tools, word for word, plus advanced prompts for stress-testing your own assistant's guardrails and confirming it holds the line under real pressure, the Companion Guide is available at ancestorsandai.com. Genealogy meets artificial intelligence, every week, on Ancestors and Algorithms: AI genealogy tools, family history research, Claude for genealogy, Gemini for genealogy, ChatGPT for genealogy, and practical AI-assisted family tree research for genealogists at every level. Connect with Ancestors and Algorithms: 📧 Email: [email protected] 🌐 Website: https://ancestorsandai.com/ 📘 Facebook Group: Ancestors and Algorithms: AI for Genealogy - www.facebook.com/groups/ancestorsandalgorithms/ Golden Rule Reminder: AI is your research assistant, not your researcher. Join our Facebook group to share your AI genealogy breakthroughs, ask questions, and connect with fellow family historians who are embracing the future of genealogy research! New episodes every Tuesday. Subscribe so you never miss the latest AI tools and techniques for family history research.

A Quebec family's baptismal records begin abruptly in 1850, though family memory said they were French Canadian for generations before that. The answer is a dit name: Quebec's centuries-old tradition of alternate family surnames, in which a family could be baptized under one name and married under another, and it is hiding more genealogy brick walls than most researchers realize. This episode of Ancestors and Algorithms, a genealogy and artificial intelligence podcast, follows a real French Canadian research case rooted in Nicolet County, Quebec, and the mill town of Woonsocket, Rhode Island, home to some of the nearly one million French Canadians who crossed the border for work by 1930. Host Brian uses Claude AI, Gemini via AI Studio, and NotebookLM, alongside FamilySearch's newly expanded French language full text search, to trace a surname that hides an entirely different baptismal name underneath it: Pepin. This episode is for you if: - You have French Canadian, Quebecois, Franco-American, or Acadian ancestry and have hit a wall in Catholic parish registers - You want to know what a "dit name" is and how it can make a well-documented family look invisible in vital records - You are curious how AI tools like Claude, ChatGPT, and Gemini can be used responsibly in family history research: to search, transcribe, and organize faster, not to invent an answer - You are researching Quebec notarial records, marriage contracts, the Drouin Collection, or the PRDH for the first time - You have ever traced a family from Quebec into a New England mill town, a "Little Canada" neighborhood, and lost the thread at the border You'll learn how to spot a suspiciously clean starting date in a parish register before assuming a family arrived from elsewhere, how Quebec's dit name tradition works and where to check it for free, how a notarial marriage contract can name a hidden family connection a parish baptism never would, and how AI-powered full text search can surface a document even when it is filed under a completely different surname than the one you are searching. For listeners in Australia and the UK: this episode's approach to a naming-convention brick wall applies directly to your own family history research too, whether that means convict-era name variants searchable through Trove, or Scottish surname and sept patterns searchable through ScotlandsPeople and The National Archives. Honest outcome: this one is a partial answer, not a full breakthrough. We confirm the family's real, much deeper roots in Quebec and solve the naming mystery behind the missing baptisms, but we do not yet know why this specific family adopted the nickname they did, or which parish in France their line sailed from before New France began. For the full episode transcript, a deeper Companion Guide with advanced AI prompts and a GPS research checklist built around this exact case, and more free genealogy and AI research content, visit ancestorsandai.com. Connect with Ancestors and Algorithms: 📧 Email: [email protected] 🌐 Website: https://ancestorsandai.com/ 📘 Facebook Group: Ancestors and Algorithms: AI for Genealogy - www.facebook.com/groups/ancestorsandalgorithms/ Golden Rule Reminder: AI is your research assistant, not your researcher. Join our Facebook group to share your AI genealogy breakthroughs, ask questions, and connect with fellow family historians who are embracing the future of genealogy research! New episodes every Tuesday. Subscribe so you never miss the latest AI tools and techniques for family history research.

A family believed their ancestor arrived in Australia a free man in the 1830s. A 190-year-old government pardon said otherwise, and nobody had ever read past the word "Pardon" printed across the top of it. In this episode of Ancestors and Algorithms, host Brian uses AI genealogy tools to work a full case study built around Australian convict records, a first for this show. More than 76,000 convicts were transported to Van Diemen's Land, now Tasmania, between 1804 and 1853, and this episode walks through exactly how to search that archive when a family's own story about "how we got here" turns out to be the wrong question. When a thorough search for a free settler's arrival turns up nothing at all, widening that same search into convict records instead surfaces a transportation record tied to England's 1830 Captain Swing riots, when agricultural laborers across more than thirty English counties rose up against the threshing machines replacing their winter wages with silence. Hampshire's own reckoning came at a Special Commission convened in Winchester's Great Hall that December, organized under the Duke of Wellington himself, and it turns a private family shame into something else entirely. This episode is for you if: You have, or suspect you have, a convict ancestor somewhere in an Australian family treeYou want to see NotebookLM, Perplexity with the Comet browser, and Claude used together on one real, multi-step genealogy investigation, prompts and allYour own research touches Van Diemen's Land, Tasmania, Hampshire, England, or the Swing Riots of 1830You have ever hit a dead-end search and wondered whether you were searching the right record category to begin withWhat you'll learn: How to search Libraries Tasmania's free Tasmanian Names Index for convict conduct records, indents, and permission-to-marry registersThe real difference between a Ticket of Leave, a Conditional Pardon, and a Free Pardon, and why mixing them up can misstate exactly how free your ancestor actually wasHow to use AI to correlate one individual's record against a larger, documented historical event instead of treating it as an isolated incidentWhy "reasonably exhaustive research," one of the five elements of the Genealogical Proof Standard, means searching the record category your family's own story quietly ruled outFor Australian researchers, this episode centers on Libraries Tasmania's convict archive and Trove, the National Library of Australia's digitized newspaper collection. For UK researchers, it covers the National Archives' criminal registers and the Home Office correspondence generated by the Swing Riots themselves, the same paperwork that put a nineteen-year-old farm laborer on a convict ship out of Portsmouth. The honest outcome: this is a Pivot episode. The original question, which ship carried a free settler to Australia, never gets answered, because that ship never existed. What the research turns up instead is richer: a real, documented historical movement, a family myth two centuries in the making, and a pardon dated February 3rd, 1836, that the family had been misreading since the day it was framed. For most of Australian history, a convict ancestor was a source of shame, edited quietly out of the family story rather than framed on a wall. Since the country's Bicentenary, that has shifted for many families toward something closer to pride, and this episode sits right in that turn. As always on this show: AI is your research assistant, not your researcher. Every record and historical detail in this episode, from the ship Eliza to the Hampshire Special Commission, has been independently verified. A Companion Guide with advanced prompts, workflows, and a GPS research checklist for this episode is available for members at ancestorsandai.com, along with every past episode, our private community, and The Research Lab. Connect with Ancestors and Algorithms: 📧 Email: [email protected] 🌐 Website: https://ancestorsandai.com/ 📘 Facebook Group: Ancestors and Algorithms: AI for Genealogy - www.facebook.com/groups/ancestorsandalgorithms/ Golden Rule Reminder: AI is your research assistant, not your researcher. Join our Facebook group to share your AI genealogy breakthroughs, ask questions, and connect with fellow family historians who are embracing the future of genealogy research! New episodes every Tuesday. Subscribe so you never miss the latest AI tools and techniques for family history research.

During the Chinese Exclusion Act, one immigrant's 200-page federal case file was built to hide his real name, and nearly succeeded. For sixty-one years, the Chinese Exclusion Act barred an entire ethnicity from immigrating to the United States, with one narrow exception: the children of Chinese American citizens. That loophole created the "paper son" system, families with no blood relation to a citizen buying a purchased identity, memorizing a stranger's village and household, and surviving a formal cross-examination at Angel Island to get through the door. In this episode, we follow one of those case files: two hundred pages of coached interrogation testimony, hand-drawn maps, and a personal letter in Chinese that the government never meant to be evidence of anything except fraud, and that turned out to hold the truth instead. This episode is for you if you're researching Chinese American genealogy, tracing an ancestor from the Chinese Exclusion Act era (1882 to 1943), working with Angel Island immigration case files, searching for a "paper son" or "paper daughter" identity in your family tree, dealing with Cantonese or Toishanese surname romanization, or trying to translate a handwritten document in a language you don't read yourself. We show our work with three AI tools, each doing a specific job. Claude builds a side-by-side comparison table across two separately-taken interrogation testimonies and flags exactly where a coached story starts to crack under pressure. Gemini, through the free AI Studio, transcribes and translates a handwritten Chinese-language letter, the piece of the file that finally answers who this man really was. Perplexity, through the free Comet browser, tracks down the historical context and points us to a real, free resource for identifying an ancestral Chinese village: the Friends of Roots Village Database. For my Australian and UK listeners, this record type has real cousins in your own archives. Australia ran its own version of exclusion through the Immigration Restriction Act of 1901, and Chinese residents needed a Certificate Exempting from Dictation Test just to leave the country and come home again, records held today by the National Archives of Australia. In the UK, the parallel runs through the Aliens Act of 1905 and the Home Office alien registration files held at The National Archives in Kew. Same instinct, different door, same kind of file left behind. Honest outcome: this is an Unexpected Discovery. We find the real answer, but it is not the answer four generations of one family believed about themselves. The Chinese Exclusion Act was state racism enacted as law, and this episode treats that history, and the resourcefulness it took to survive it, with the weight it deserves, not as a plot twist. Want to go deeper than the free episode? The Companion Guide includes twelve advanced AI prompts and full workflows for this exact kind of case: spotting a coached interrogation, verifying a translation you can't read yourself, and building a properly cited research file. Patreon members also get five intermediate prompts built around real, verified record collections for Chinese Exclusion Act research, including where files are actually held, how to search around a broken index, and how to tell the National Archives from USCIS before you send a request to the wrong agency. Find all of it, and every episode, at ancestorsandai.com. Connect with Ancestors and Algorithms: 📧 Email: [email protected] 🌐 Website: https://ancestorsandai.com/ 📘 Facebook Group: Ancestors and Algorithms: AI for Genealogy - www.facebook.com/groups/ancestorsandalgorithms/ Golden Rule Reminder: AI is your research assistant, not your researcher. Join our Facebook group to share your AI genealogy breakthroughs, ask questions, and connect with fellow family historians who are embracing the future of genealogy research! New episodes every Tuesday. Subscribe so you never miss the latest AI tools and techniques for family history research.