# Kin Resolve: evidence first, deliberately small

**Duration:** 90 seconds  
**Source commit:** `c6e0309ab609b08f4c76362fefa0dd4d6c80e403`  
**Data disclosure:** Every name, date, place, record, filename, and workflow shown is fictional.  
**Audio disclosure:** The wordless ambient bed is generated entirely from mathematical tones; all tour language appears in captions and this transcript.

## 0:00–0:10

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

## 0:10–0:22

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.

## 0:22–0:34

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.

## 0:34–0:47

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.

## 0:47–0:58

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.

## 0:58–1:09

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.

## 1:09–1:21

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.

## 1:21–1:30

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