# Rootline > Rootline is a free, local-first genealogy app that opens GEDCOM files and shows the source and proof level behind every fact. Every fact in a tree says how well it is proven (proven, probable, hypothesis, contradictory) and which sources, quoted line by line, support it. The trees stay in the person's own browser: there is no account and no server copy, so an agent works in the browser the person shares with it, and changes nothing without their review. This file tells an agent how to read the site and how to hand back what it finds. All paths are relative to this file's origin. ## Reading a page Every page of a tree is under `/trees/{treeId}/`, written `{tree}` below; `/` leads to the tree shown last. Add `.md` to any page's address to read it as Markdown, such as `{tree}/people/{personId}.md`, `{tree}/timeline.md?person={personId}`, `{tree}/missions.md` or `{tree}/sources.md` (`{tree}/index.md` for the tree's home). The trees live in the person's browser, so open these addresses in the browser that holds them; the sample families open anywhere: `/trees/bonaparte`, `/trees/darwin-wedgwood`, `/trees/windsor`, `/trees/bush` and `/trees/shakespeare`. People, facts and sources keep their stable IDs (`P-…`, `A-…` or `E-…`, `S-…`) and links to follow; every fact says how well it is proven and which sources it cites. The Markdown speaks the app's language, as the screen does (French or English); what the format names — keys, values, IDs, statuses — stays as written. A page that says it is loading the tree is read again a moment later. ## Pages - `{tree}` — the tree at a glance. - `{tree}/people.md` — everyone, one line each: id, dates, parents and partners, to name them in an answer. - `{tree}/gaps.md` — what the tree lacks along the ancestry of its starting person, the nearest ancestors first: unknown parents, births and deaths unknown or not proven, and the research's open leads with whom they name. Pick the next search here. - `{tree}/answers.md` — the answers already laid over the tree, as they came in: when, how many changes each brought, the people it added with their IDs, and how many IDs it named that nobody has. Read it before proposing someone, so no one is added twice. - `{tree}/places.md` — every place of the tree as the map locates it: each commune of France by its name today, its INSEE code and department, the ways the records write it and its former names; then places elsewhere and those not located. Write a place as the tree already does, with `place_code` and `place_name`. - `{tree}/validate.md#answer=…` — an answer checked against the tree: what it holds (new people, relations, facts, sources, searches made, the tree's people it names), then what would be left out, and why, or OK, and the new people the tree may already hold. - `{tree}/people/{personId}` — a person: life event by event, facts with their proof and sources, parents, partners, children, and links to their timeline, map and tree. Page data: `person`. - `{tree}/tree/{personId}` — the ancestors as a fan or as branches. - `{tree}/timeline` — every event in order. Parameters: `person={personId}`, `place={written place}`, `line={0-3}` (a grandparent's line), `kinds=births,unions,deaths,other`, `order=newest` (oldest first otherwise). Page data: `timeline`. - `{tree}/map` — the places. Parameters: `person={personId}`, `place={written place}`. - `{tree}/missions` — the missions: the album's, then the side missions (« annexes »): facts to settle (a contradiction and the impossible dates on the same facts are one mission), dates to check, deaths to find, research noted, links and identities to confirm, facts with no record. `m=` selects one by its key, such as `clash:E-1+E-2`; `{tree}/steps` and `section=` still lead there. Page data: `review`. This is the natural work queue for an agent. - `{tree}/sources` and `{tree}/sources/{sourceId}` — the sources; a source page shows its document, and `#L{start}-L{end}` highlights cited lines. - Any page with `?fact={factId}` opens that fact's evidence. ## Proof levels The person chooses how much of the research the site reads: « Prouvé seulement » (proven only), « Prouvé et probable » (proven and probable, the default) or « Tout, avec les hypothèses » (everything, with hypotheses). The levels use the facts' own statuses: proven, probable, hypothesis, contradictory. Pages and their data follow that level; the side missions of `{tree}/missions` always read everything. ## Helping with the research The instructions an agent follows, in English and French: - `/prompts/interview/v1/en.md` — build and verify a tree with someone: their memories, then the archives. - `/prompts/research/v1/en.md` — settle one question: dates that clash, sources that disagree, a fact without a source, a link or a place to confirm. Each prompt says its job, the rules that matter most and the answer's format, short enough to open in a chat app's link with the tree it continues; `` stands for this site's address. The tree comes in a short notation, one line per person and one per union, explained in two lines above it; the answer is always the JSON below. The rules below apply to both. ## Rules for every agent - Search the online archives (civil registers, parish records, censuses, military records, notarial records) before asking: ask the person only what the archives can't tell. - Never invent a name, a date, a place, a record or a quote. What is not seen in a record stays a lead (`to_research`) or a `hypothesis`. - `confidence`: `proven` only when the record itself was seen and its lines transcribed; `probable` for an index, another family tree, a record mentioned but not seen, or what the person states as known (“born on 12 March 1952”), with `"informant": "root"`; `hypothesis` for a deduction or what they say with a doubt (“around 1950”, “I think”). When you can't tell whether they are sure, ask once, with your other questions; with no answer, keep `probable`. What someone else told them has that someone as its informant; when the person passes on a relative's answers, the relative is the informant. A document the person has at hand (a family record book, an announcement): ask them to copy the line; it is a `document` source, and the fact becomes `proven`. - A tree may be shared, and its quotes travel with it: quote only the words that state a fact, and leave out what is sensitive (health, identity numbers, family conflicts and secrets, the private lives of the living) unless the person asks to keep it. - Two readings that disagree both stay, each with its source: never delete one, say what would settle it. Rootline marks them contradictory. - Never rewrite what the tree holds: an answer only adds or corrects, with a source. Name the tree's people by their `P-…` ids and its events by their `E-…` ids; a new person gets a short id of the answer's own (`p1`). - Each source says where it is (archive, reference, link); each fact quotes the exact lines it comes from (`quote`). - `notes`: two or three plain sentences for the person, with no technical detail (no ids, hashes, code or formats). - Before answering, check: every fact has its source, nobody is in the tree twice, each confidence matches what was seen or said, and nothing sensitive is quoted. Nothing to change? Say why, in `notes`. - If you can create files, attach the answer too, named as below. Draft fields, beyond the examples in the prompts: - a fact's `type`: `birth`, `baptism`, `marriage`, `divorce`, `death`, `burial`, `residence`, `occupation` (with `value`); a marriage or a divorce takes `persons` with both spouses. - `date`: `1950-03-12`, `1950-03`, `1950`, `~1950` (around), `1948..1952` (between), `<1950` (before), `>1950` (after); left out when unknown. - `sex`: `M`, `F`, or left out. - a source's `kind`: `oral` (with `informant`, a person's id, or `"root"` for the person the tree is about, accepted there only; without a `title`, the source is named after them) or `document` (with `document_type` and `transcription`, the record's text, faithfully). Say where a record is kept: `archive` (AD Aveyron), `reference`, its cote (4E 71/5), `view` (12/48) and `url`; `{tree}/sources.md` lists the records already cited by archive and cote, to add a reading to one rather than cite it again. - `searched`: the searches made, found or not, each with `what` was looked at, its `archive`, `reference`, `view` or `url`, `"found": false` when nothing was found, the `person` it was for and a `note`. They join the tree's research log, shown on each person's page and in `{tree}/gaps.md`: check them before searching, and never take an absence for a proof. - `"patch": true` when completing a tree: only what changes, the tree's people named by their ids and not repeated in `people`. `{tree}/people.md` lists everyone with their id, dates, parents and partners. - a relation: `{"type": "parent", "parent": …, "child": …}` or `{"type": "union", "partners": [a, b]}`. There is no sibling relation: two people who share their parents are siblings, so give each child their `parent` relations. The full format is a JSON Schema: `/schemas/rootline-draft-1.json`. A patch that adds a daughter to Paul, with her birth read in a record, testified by the person the tree is about: ```json { "format": "rootline-draft/1", "patch": true, "notes": "Lucie, Paul's daughter, was born in Limoges in 1985, as her birth record says.", "sources": [ { "id": "s1", "kind": "oral", "title": "Souvenirs", "informant": "root" }, { "id": "s2", "kind": "document", "title": "Acte de naissance de Lucie MARTIN", "document_type": "acte de naissance", "transcription": "Le 4 mai 1985 est née à Limoges Lucie MARTIN, fille de Paul MARTIN." } ], "people": [{ "id": "lucie", "given": "Lucie", "surname": "MARTIN", "sex": "F" }], "relations": [ { "type": "parent", "parent": "P-0000000000000002", "child": "lucie", "source": "s2", "quote": "Lucie MARTIN, fille de Paul MARTIN", "confidence": "proven" } ], "facts": [ { "person": "lucie", "type": "birth", "date": "1985-05-04", "place": "Limoges", "source": "s2", "quote": "Le 4 mai 1985 est née à Limoges Lucie MARTIN", "confidence": "proven" }, { "persons": ["P-0000000000000002", "P-0000000000000003"], "type": "marriage", "date": "~1980", "source": "s1", "quote": "ils se sont mariés vers 1980", "confidence": "probable" }, { "person": "P-0000000000000002", "type": "occupation", "value": "instituteur", "source": "s1", "quote": "il était instituteur", "confidence": "probable" } ], "to_research": ["Find Paul and Louise's marriage record, around 1980."] } ``` Before handing an answer over, check it: open `{tree}/validate.md#answer=…` (the same data as an answer link) for what Rootline would leave out and why, or call the `validate_answer` tool in the browser. Without the browser, the JSON Schema checks the format; the tree's ids are in `{tree}/people.md`. ## Handing back an answer An answer is a `rootline-draft/1` JSON file named `rootline-YYYY-MM-DD-subject.rootline.json` (today's date and a few words of its subject; never the same name twice), in the format the prompts describe: only what changes, with each fact's source, its quoted text and its confidence. Beyond people, facts, relations and sources, a draft may carry: - `notes`: what you conclude, in a few sentences. An answer with notes only says that nothing changes, and why. - on a person, `usual`: the given name they went by when it is not their first (`Louis-Napoléon` for `Charles Louis Napoléon`). - on a fact, `event` (an existing `E-…` id) to add a reading to that event rather than a new one; and for a place, `place_name` and `place_code` (the commune's INSEE code) to say which commune a written place is, or outside France `place_country` (ISO 3166 code) and `place_coordinates` (`[lon, lat]`). In a chat, give it at the end of the reply in a code block marked `rootline`: the person pastes the whole reply into Rootline, which reads that block. To give it to Rootline from a tool or code, the most direct way is a link: the site's address followed by `/#answer=` and the JSON in base64url, without padding (in Python: `base64.urlsafe_b64encode(json.encode()).decode().rstrip('=')`). Opening it shows the answer, loaded, for review; the fragment never reaches a server. Several times shorter: `#answer=z.` and the raw deflate of the JSON in base64url (in Python: `c = zlib.compressobj(wbits=-15); base64.urlsafe_b64encode(c.compress(data) + c.flush()).decode().rstrip('=')`). Several answers go in one link as a JSON list of drafts, reviewed together. Each keeps its own short ids: an answer names another's new people only once that one is in the tree, by the `P-…` id `{tree}/people.md` then gives. Answers already in the tree are read in an order that works, whichever came first. Otherwise, open `/?answer` (on any page, such as `{tree}/people/{personId}?answer`): the sheet opens on its last step. Click « Coller la réponse », type the JSON into the field labelled « Coller la réponse » (a valid draft is taken at once), then click the button that starts « Ajouter » and ends « à l’arbre », such as « Ajouter 3 changements à l’arbre » (a no-break space joins the number and its word), or « Créer l’arbre » when there is no tree yet. Dropping the file anywhere on the site works too. The person reviews every change before it is laid over their tree. ## Tools for agents in the browser Where the browser offers WebMCP (`document.modelContext`, or `navigator.modelContext` in earlier versions), the site registers four tools: - `read_page`: the page on screen as Markdown, as its `.md` address gives it; with a `path`, another page of the tree shown, such as `{tree}/gaps.md`, `{tree}/answers.md` or `{tree}/places.md`. - `open_page` with a `path`: opens a page of the site. - `validate_answer` with an `answer`: what Rootline would leave out of it, and why, without adding anything. - `submit_answer` with an `answer` (the `rootline-draft/1` JSON): opens it for the person's review.