Kin ResolveEvidence-led genealogy
Apply for the private beta
The product

One workspace for the work behind the tree.

Connect imported records to questions, sources, DNA clues, analysis, and publishing decisions—without turning a working hypothesis into a fact.

Apply for the private betaView on GitHub
A connected workspace

The research trail stays attached.

People, sources, cases, matches, and analysis are useful on their own. They become far more useful when you can see which question each item informs—and what remains uncertain.

Every example below is fictional. All Hartwell–Mercer names, dates, places, records, photographs, file names, and DNA values were invented for the demo and do not describe real people.
Version-pinned synthetic product tour

See the working product—without a single real family record.

Eight frames and one exact 90-second walkthrough follow the fictional Hartwell–Mercer archive from question to import, review, evidence, quality, API access, and export.

Read the 90-second transcript

  1. Family trees preserve conclusions. Kin Resolve preserves questions, records, uncertainty, and next steps. This tour uses only fictional Hartwell–Mercer data.

  2. Bring in a plain GEDCOM as a named, durable source. The original export is staged privately, processing state survives a refresh, and nothing enters the archive merely because a file was selected.

  3. Incoming additions, edits, conflicts, and deletions become an explicit review. Safe changes can be approved together; ambiguity requires a decision; remote deletion keeps the local record by default.

  4. Research stays organized around a question, not just a person. Evidence can strengthen or weaken competing hypotheses, confidence remains visible, and the case keeps the next search tied to the reason it matters.

  5. Source transcripts remain close to the people and cases they inform. Cohort one deliberately excludes binary source media, so the hosted boundary stays narrow, understandable, and enforceable.

  6. Quality and privacy checks run deterministically inside Kin Resolve. They prioritize date conflicts, source gaps, and sharing risks without sending the archive to an external AI provider.

  7. The developer preview uses scoped, expiring, archive-bound tokens. A secret is shown once, only its prefix remains visible, and revocation denies the next request immediately.

  8. The exit path stays visible: download a GEDCOM, keep the review trail, and request verified deletion. Apply without sending family records.

Kin Resolve synthetic Hartwell–Mercer dashboard showing active research cases and archive metrics.
01

A private investigation dashboard

A clearly labeled fictional archive turns people, sources, cases, and next actions into one private research view.

Kin Resolve synthetic GEDCOM source with a durable refresh queued for private review.
02

A durable GEDCOM source

A named GEDCOM source keeps its durable processing state; selecting a file never silently changes the archive.

Kin Resolve review screen showing incoming synthetic GEDCOM changes and policies for conflicts and deletions.
03

Review every change before apply

Additions, edits, conflicts, and deletions are grouped under explicit review policies before apply.

Kin Resolve fictional Mercer–March identity case showing competing hypotheses, confidence, and a reviewable research trail.
04

Keep evidence and uncertainty together

The question, evidence, competing explanations, confidence, and next useful search stay together.

Kin Resolve fictional Hartwell–Mercer source transcripts linked to private research context.
05

Keep source transcripts in context

Searchable transcripts remain close to the people and cases they inform; cohort one excludes binary source media.

Kin Resolve quality report prioritizing synthetic archive issues with no external AI used.
06

Check quality without an external AI provider

Deterministic date, source, and privacy checks run inside the Kin Resolve deployment without an external AI provider.

Kin Resolve developer API controls showing scoped expiring archive tokens without revealing a token secret.
07

Create scoped, revocable API access

Create archive-bound, scoped, expiring tokens; secrets appear once and revocation denies the next request.

Kin Resolve archive portability panel offering a full GEDCOM export and reviewable reversible imports.
08

Keep an exit path

Download the archive as GEDCOM, preserve a review trail, and keep rollback and verified deletion paths visible.

01 / Archive integrity

Import without flattening the record.

Preview a GEDCOM before it changes the archive. Kin Resolve preserves raw records, xrefs, custom tags, notes, source references, and checksums, then shows reviewable changes on re-import.

  • Preview before apply
  • Reviewable re-import differences
  • Pre-import recovery snapshot
  • Full GEDCOM 5.5.1 export
Import review

hartwell-mercer-fictional-demo.ged

New people16
New families7
New sources4
Fictional demo interface
02 / Focused research

Work a question, not just a person.

Cases hold the question, evidence, hypotheses, confidence, and next actions together. The tree remains a record of conclusions; the case preserves how you got there.

  • Evidence linked to people and sources
  • Competing hypotheses
  • Confidence and rationale
  • Reviewable next-step queue
Active case

Mercer–March passenger mystery

Evidence items3
Hypotheses2
Open tasks1
Fictional demo interface
03 / Sources in context

Keep citations close to the work they support.

Search source records and transcripts, connect them to people and cases, and make gaps visible before a conclusion or public profile is treated as finished.

  • Source register and search
  • Transcripts and archive details
  • Person and case links
  • Coverage-gap reporting
Source review

Fictional Lantern Bay civil register: Nora Hartwell

Linked people1
Linked cases0
TranscriptReviewed
Fictional demo interface
04 / DNA as a clue

Triage matches without turning a score into a fact.

The source product can import match CSVs, rank useful leads, record shared-match context, and connect promising matches to a research case. Hosted DNA is excluded from the proposed first cohort.

  • CSV import and match scoring
  • Surname and place clues
  • Shared-match context
  • Case evidence links
DNA lead

M. Alder (fictional)

Shared DNA86 cM
TreePartial
Estimate3C or 3C1R
Fictional demo interface
05 / Optional analysis

Use AI as an analyst, not an authority.

Deterministic structural checks work without an AI key and are proposed for cohort one. The source product can connect an OpenAI-compatible provider, but external AI is excluded from the proposed hosted cohort.

  • No-key structural checks
  • Operator-selected provider
  • Referenced workspace context
  • Saved runs and staged suggestions
Analysis run

Mercer–March identity check

Context records3
Identifiers2 independent
ConfidenceModerate
Fictional demo interface
06 / Deliberate publishing

Review before sharing.

The source product combines manual person publication with living-person and privacy gates. Publication-readiness checks are proposed for cohort one, while real-data public publishing remains disabled.

  • Manual person publication
  • Living and privacy gates
  • Readiness blockers
  • Anonymous public profiles
Publishing review

Nora Elise Hartwell

PrivacyPublic
Living statusDeceased
Public facts4
Fictional demo interface
Private beta applications open

Private beta applications are open.

Invitations have not started; hosted access begins only after the launch gates pass.

Implemented in source
  • Single-archive private research workspace
  • GEDCOM import preview, review, apply, rollback, and export
  • People, source, case, evidence, hypothesis, and task workflows
  • Deterministic quality and privacy checks
  • Private object storage and durable background jobs

This is a code-state claim, not a hosted-availability claim.

Proposed after launch gates
  • A synthetic demo before any private family data
  • One isolated plain-GEDCOM pilot after every real-data gate
  • Founder-operated onboarding, export, deletion, and support
  • A scoped, read-only API preview after its separate launch gate

Each item still depends on its applicable approval and production evidence.

Disabled or excluded
  • DNA uploads or triage
  • External-provider AI
  • Media packages or binary source attachments
  • Real-data public publishing
  • Open signup, billing, or shared multi-family hosting

These are server-enforced cohort boundaries, not omissions hidden only in the interface.

Hosted invitations have not started, and the API preview is not yet available. “Excluded” is a cohort-one boundary, not a claim that the source capability is absent. Read the beta boundary, review the data practices, or follow progress in the public repository.

Prefer a no-sign-in puzzle first? Test your genealogical skills in the fictional research challenge.

Try the working product

Work the fictional Hartwell–Mercer mystery in Kin Resolve.

Start in a temporary fictional workspace, then investigate thirty synthetic record images and transcripts across five immersive cases.

Try Kin Resolve Apply for the private beta