What problem does it solve? Genealogical records were created under specific legal, political, and social conditions, and misreading that context leads to misinterpreting evidence — a place discrepancy may be a boundary change, not a conflict. This Skill explains the historical background behind records so researchers interpret them correctly. ## Core Features & Use Cases - Boundary and jurisdiction analysis: Explains place discrepancies caused by county formation, state splits, annexation, and post-war border shifts, verified live from FamilySearch wiki pages. - Historical terminology interpretation: Clarifies period-specific meanings of relationship terms ("in-law", "Junior/Senior"), legal terms ("relict", "feme sole"), and occupations ("cordwainer", "yeoman"). - Migration, economic, and cultural context: Covers chain migration, ethnic enclaves, naming conventions, and record-availability gaps such as courthouse fires or pre-civil-registration eras. - Use Case: A user asks why an 1850 census says an ancestor was born in Ireland while a death certificate says Pennsylvania. The Skill explains informant reliability and immigrant reporting practices, then states which record carries more weight for birthplace. ## Quick Start Ask why a genealogical record shows an unexpected place, date, or term, such as "why would my ancestor appear in two different counties?"
