How the work is done.One custodian, both trails.
Two disciplines, one operating posture. The framework below is what holds the open-record work and the lineage work to a common standard — and what the dossier is built against, at intake and at closing.
The two methods below are not interchangeable: open-source practice grades a public claim; primary-source genealogical practice grades a record. Both have to hold before a dossier is citable.
OSINT source validation
Every open-source claim is graded before it lands in a dossier.
Public records, search-result snippets, broker registries, social posts, archived snapshots — each is evaluated against the same four-part rubric before it becomes a load-bearing assertion in an engagement file. The rubric exists so the dossier reads cleanly to a later reviewer: a counsel, a notary, a subject three years on.
The four-part rubric applied to every open-source claim:
Provenance chain
01Who first published, when, and who has re-shared it. Open records are treated as a graph, not a list — a single-source claim requires that single source to be named, dated, and link-stable.
Corroboration requirement
02Adverse claims require at least two independent sources. Single-source adverse claims are kept on the record but explicitly flagged as such; they do not become the basis of a takedown or a notification without independent support.
Re-validation cadence
03A source class carries a decay timeline. Search-engine snippets decay fastest; primary-record snapshots decay slowest. Each entry in the dossier carries the date it was last re-validated, not the date it was first found.
Toolchain transparency
04Search operators, archive snapshots, broker-lookup tooling, and the public-record indices queried are all recorded inline with the claim. Methodology is reproducible by a third party — that is the privacy posture.
Genealogical evidence standards
Identity-defining claims hold only to primary sources, never to derivative databases.
Where the digital practice audits what an open record says about the subject, the lineage practice audits what an authoritative record says about the subject's family. Both are evidence work, both are held to the same standard: a defensible, citable, notarised record at closing. The framework below cites the Genealogical Proof Standard as the working standard.
The four disciplines applied to every record before it enters the dossier:
Primary-source-only rule
01Identity-defining claims are sourced from the record itself: civil registries (birth, marriage, death), parish and sacramental registers, court records, census enumerations, and naturalisation or citizenship instruments. Derivative databases — family trees, online genealogy aggregators — are treated as leads to be confirmed against an original, never as evidence on their own.
Conflict-resolution protocol
02When records disagree, the heaviest-weight source wins. Birth, marriage, and death entries from the subject's own civil jurisdiction trump church transcriptions and family-tree claims. The exception is logged in the dossier: which record was preferred, why, and what weight the alternative was given.
Citation discipline
03Every dossier footnote names the record, the holding repository, the image or folio identifier, and the access date. A dossier reads like a verifiable trail — any reviewer can follow it back to a single named source. This is the Genealogical Proof Standard applied record-by-record.
Reproduction-grade output
04Closing deliverables — the evidentiary dossier, the family-tree narrative, the citizenship or estate brief — are produced to a standard that will stand up in a civil registry, a consulate, or a probate filing. The work is built to be referenced, not re-done.
Integration for dual-scope engagements
When an engagement spans both trails, evidence flows between them under one custodian.
Most engagements begin on one trail. Many end on both. A citizenship case opens as a digital-takedown scope and closes as an inheritance brief. A stubborn-takedown case opens as a search-engine scope and closes as a reunification contact. The integration discipline below keeps the two trails in lockstep — same custodian, shared ledger, single acknowledgement.
The three integration moves applied at every closing:
Evidence propagates between disciplines
01A verified birth record disambiguates a digital alias cluster; a takedown-confirmed account shutdown clears the way for a reunification contact. When a fact is settled in one discipline, it is travelling consent for the other — and the dossier records it that way.
Shared ledger, single acknowledgement
02One custodian runs both engagements. Notes do not fragment across teams; the next reader is the same person who audited the open record. This is the privacy posture, and the audit trail — at intake, mid-engagement, and at closing.
Sealed handoff at closing
03When a dual-scope engagement closes, the combined dossier is sealed under a single certificate of destruction. The subject receives a single reconciliation record — not two separate reports and not two contradictory ones.
GDPR / CCPA posture
Every engagement is held under a defined lawful basis, a bounded retention, and a written posture.
A privacy posture is not a footer note — it is the operating constraint that runs through every practice above. The framework below names the lawful basis, the data-subject rights, and the close-out commitments that govern all research, both open-source and lineage, regardless of jurisdiction.
The five-point posture applied to every engagement:
Lawful basis
01Legitimate interest is the standing basis for open-source research; consent is sought for any subject-provided material. Where the basis shifts — a takedown request against a data broker, a record request against a registry — the new basis is recorded in the dossier before the work continues.
Minimisation
02Only the field needed for the claim is collected. Personal identifiers are isolated, not aggregated; sensitive attributes are recorded only where their absence would weaken the evidence. The aim is fewer, better-grounded fields rather than fuller files.
Data-subject rights
03Access, rectification, erasure, and objection are honoured on request within a defined response window. The subject can ask, at any point in the engagement, what is held, what is undergoing takedown, and what is sealed. Requests do not require justification.
Takedown posture
04Broker removals are pressed under Art. 17 (GDPR) and §1798.105 (CCPA) where the regime applies, and under equivalent state-privacy statutes where it does not. The takedown letter carries a notebook — record, basis, expected response window — that lives in the dossier.
Retention & cross-border transfer
05Working copies are engagement-bounded. On closing, the dossier is sealed, the working copies are destroyed under a written protocol, and a certificate of destruction is issued. Cross-border transfers are minimised: data moves only to the jurisdiction where the next step is taken, and the legal basis is recorded there too.
Begin a scope
Two trails.
One custodian.
The first scope costs nothing — a brief on your situation, sealed and acknowledged within two business days. The framework above is what the work is run against; the intake is the part where the work begins.
Where the practice sits
The two methods, applied.
The OSINT rubric and the Genealogical Proof Standard meet at the closing dossier. The work between is held the same way.