Source Register and Citations
Updated
BeginnerWhat you'll learn
~35 min- Ask an AI tool, in plan mode, for a register of your source files in a short, plain request, and answer its questions
- Read its plan for the things that matter to the research: files checked by what is in them, sources only read, a fingerprint kept from the day you register
- Spot a file that is not what its name says, keep it exactly as found, and leave it uncited
- Tell an original from a derivative (a later version made from it) and say which file a derivative came from
- Read an unchanged fingerprint for what it shows: the file is the one you registered, not that its content is right
The story, and what you will end up with
By the end of January 2026 your folder for Great-uncle Walt’s family has filled up. There is an image of the 1858 baptism entry for an Olof who may be his grandfather (whether he is, is a question this course comes back to), saved from the Norrland Provincial Archive (fictional), and a text copy of a volunteer index entry for the same baptism. There is a scan of the back of a family photograph, and a brightened copy you made the next day to read its faded stamp. There is an image of a household examination roll, the parish’s book of who lived in each household, that you downloaded on 25 January and again on the 26th. In March the casualty file, the file of reports and letters about one service member’s death, arrives as a PDF.
Each file has a sensible name, and you kept a note on each: what record it holds, when you got it, where from, and the page. One of the files is not what its name says, and nothing about its name tells you so.
Two other files are the same baptism in two forms. The image is an original: a record in its first form, or a good image of it. The index entry is a derivative: a later version made from the original by someone else, here a volunteer typing it up. A derivative can be very useful and still differ from the original, so you need to know which one you are holding and which one you are citing.
By the end of this lesson you will have a small program on your own computer, your register, that keeps a record of your files: it checks what is really inside each one, takes a fingerprint of each so it can tell you later whether any file has changed, shows which files are originals and which are derived from which, and writes citations from your notes. You build it by asking your AI tool in plain English, and you check it by reading what it prints.
Before you start
First, if your AI tool is still open, leave it: type /exit and press Enter (if you use Antigravity, press Ctrl+D with nothing typed instead), and wait until you see the $ or % prompt. The next line goes there, in the terminal, not in the AI tool. It makes a folder for this lesson and goes into it:
mkdir -p ~/archive-playbook/02-source-register && cd ~/archive-playbook/02-source-registerStart your AI tool with the start line you kept from the setup lesson, the one with approval prompts off. Then ask it to set the folder up:
Set this folder up so we can undo any change you make, download https://learn.intellimetrics.net/starters/history/02/walt-files.zip and unpack it into a data folder, and save a checkpoint.Look for it saying three things: the folder is set up with Git (the program that saves snapshots, from setup), the download is unpacked into data/ (your notes in register.json and seven files in sources/), and a first snapshot, your checkpoint, is saved. If it does not mention one of them, ask: “Did you save a checkpoint with the files in it?” If the download does not work, download walt-files.zip in your browser, check where it went (the browser’s list of downloads shows the folder), and tell your AI tool, for example: “walt-files.zip is in my Downloads folder. Unpack that one file into a data folder here, and save a checkpoint.” In Windows PowerShell or a desktop app, “my Downloads folder” works as is; only say “my Windows Downloads folder” if you use Ubuntu (WSL) on Windows, which keeps its own Downloads folder apart from Windows.
Everything in the download is fictional, made up for this course. The files are stand-ins: the register page, the roll and the twelve-page PDF are plain cards, not pictures of real pages, and the back of the photograph and its brightened copy are drawings, the same ones the photograph catalog lesson uses. You read the baptism page itself in the next lesson and the casualty file’s pages in the page sorter lesson.
Open this box once, because it says what each code used further down stands for.
ℹWhat is in walt-files.zipclick to expand
Seven files in a sources folder, and register.json, your notes on them. Each file has a short code, FL-01 to FL-07, and each note gives the record the file holds (R codes are records in the case, the invented family history this course works on), the date you obtained it, where from, whether it is an original or a derivative (and of which file), a locator (which page or entry of the record the file shows; N:o is the register’s short form of “number”) and, for most files, the pieces of its citation.
| Code | File | What your note says it is |
|---|---|---|
| FL-01 | TRAINING-TM-BAPT-2_p047.jpg | image of the 1858 baptism register, p. 47, N:o 9; obtained 2026-01-18 |
| FL-02 | TRAINING-HPI-58-0947.txt | volunteer index entry for that baptism; derivative of FL-01 |
| FL-03 | TRAINING-TM-ROLL-16_p098.jpg | household examination roll, 1872 to 1877, pp. 97 to 98, “(intended)”; obtained 2026-01-25; original or derivative not set |
| FL-04 | TRAINING-TM-ROLL-16_p098_retry.jpg | the same pages, downloaded again 2026-01-26 |
| FL-05 | TRAINING-CF-2214.pdf | Walt’s casualty file, 12 pages; received 2026-03-28 |
| FL-06 | TRAINING-PH-0031B.tif | your scan of the back of photograph PH-0031, the archive master |
| FL-07 | TRAINING-PH-0031B-E01.png | the brightened copy you made from FL-06, with its settings |
Two notes, FL-06 and FL-07, have no citation pieces yet. The first lines of FL-01’s note look like this:
{"id": "FL-01", "file": "TRAINING-TM-BAPT-2_p047.jpg", "record": "R-03 Baptism of Olof, 1858, Tallmora baptism register", "obtained": "2026-01-18", "from": "Norrland Provincial Archive (fictional), image service", "source": "Original", "note": "image of the register", "locator": "p. 47, N:o 9", "cite": {...}}Switch to plan mode
Your AI tool is already open. Switch to plan mode now: Shift+Tab until it says plan, or /plan (the keys for each tool). In plan mode it usually reads your file, asks its questions and shows you a plan before it builds anything; the order can vary.
The conversation
Each message below is an example. Say it your own way.
Say what you want
Say who you are researching, where the files are, and what you want:
I'm researching my great-uncle Walt's family. The data folder has my files and my notes on each. Help me build a tool that registers them, tells me later if any changed, and writes citations. Ask me what you need first.Your AI tool reads your notes and looks at the files, then comes back with questions. It may also tell you what it noticed. If it says something about FL-03, read that closely; the next sections come back to it.
Answer its questions
Answer each in a sentence. These are questions AI tools often ask, with one way to answer each. Yours may ask them in a different order or show a list of choices:
| If it asks | You might say |
|---|---|
| A browser page, or commands in the terminal? | Commands in the terminal. |
| FL-03 is not a picture. Keep it and flag it, or leave it out? | Keep it exactly as it is and flag it, but never cite it. |
| FL-06 and FL-07 have no citation pieces. Write some from the other notes? | No. List them as needing citation notes. |
| A particular citation style, and where should citations go? | Full and short citations from my notes, no style guide. Show them on screen and save a copy. |
| Dates as 18 January 2026, or 2026-01-18? | 2026-01-18. |
| When should it check for changes? | Only when I ask. |
| Is this your real list, and will you add new files to the notes yourself? | It’s practice data, and I’ll add new files to my notes myself. |
| A printed summary of each check, or a dated log too? | A printed summary is enough. |
If it asks several questions at once, answer the ones that matter to your research in a sentence, and for the rest say that its suggestions are fine. If it asks something not listed here, answer it the same way, in a sentence.
Read the plan
Next it shows you a plan: what it will build and how it will check it. Read it for five things:
- Every file is checked by what is inside it, not by the letters at the end of its name, and a file that is not what its name says is flagged.
- Your files in
sources/are only read: never changed, renamed, moved or deleted, and that includes a file that fails the check. It is kept exactly as found, and it gets no citation. - Each fingerprint is taken once and kept. A later check compares each file with the fingerprint taken on the day you registered it, and does not quietly take a new one.
- Each file shows whether it is an original or a derivative, and a derivative shows which file it came from.
- Citations come from your notes. A file whose note has no citation pieces is listed as needing them, and none is made up.
A first plan often leaves one of these out. Say so in a sentence, in your own words, for example:
Also show whether each file is an original or a copy, and of what.When the plan has all five, approve it: if your AI tool offers a choice to go ahead, pick it; otherwise say “Yes, go ahead and build it.” In Codex, press Shift+Tab first to leave plan mode. In Copilot, saying it brings up a choice to go ahead; pick that. Let it build. When it has finished, ask it: “Did you install anything, and where?” Nothing, or something inside this lesson’s folder, is fine for these lessons. If it names anywhere else on your computer, ask it what that is for, and to remove it if you do not want it there.
Look at what it built
Ask it to run what it built:
Run it and show me what it says about each file.Then ask for the citations:
Show me both citations for FL-01, and what you have for FL-06.Your register will lay things out in its own way and use its own words. Check it for these:
- FL-03 is flagged: its name ends in
.jpg, but what is inside is a web page (HTML), not an image. It is still insources/, and it gets no citation. - No other file is flagged that way: FL-01 and FL-04 are JPEG images, FL-05 is a PDF, FL-06 a TIFF, FL-07 a PNG, and FL-02 is text.
- FL-02 shows it is a derivative of FL-01, and FL-07 a derivative of FL-06.
- The check reports all seven files unchanged since you registered them, and nothing it prints calls a file genuine, accurate or true.
- FL-01’s full citation names Tallmora parish, the baptism register, volume TRAINING-TM-BAPT-2, page 47, entry N:o 9, the Norrland Provincial Archive (fictional) and 2026-01-18. The short one is shorter and keeps the date.
- FL-06 gets no citation: the register says its notes have no citation pieces, and does not make one up.
- When you ask “Have any of my source files changed since the checkpoint?”, it compares them with the checkpoint and says no. That question is not the check you built: your register compares each file with the fingerprint from the day you registered it, and this one only confirms that building the register left your sources alone.
Some tools show FL-03 as unchanged and flagged at the same time; both are true. FL-07 will also be listed as needing citation pieces, and FL-03 may be too.
If something on the list is not true, tell your AI tool in a sentence what you see and what you expected. If FL-06 comes back with a citation made from its other notes, for example, say: “FL-06 has no citation pieces in my notes. List it as needing them instead.”
Notice what an unchanged fingerprint can tell you
Find FL-03 in what your register printed. Its name ends in .jpg, and your note says it is the household examination roll, “(intended)”. What does it say is inside it?
It is not a picture. Your register has already told you what is inside: one line of text, a web page saying “Your session has expired. Please sign in again.” The archive’s site had logged you out on 25 January, and what you saved was its sign-in page. The name is a claim about the file, and the first bytes of the file (the first few characters stored in it, which differ from one type of file to another) show the claim is false.
A hasty reader sees the file in the folder, with the right name, and writes “roll image saved, pp. 97 to 98” in the notes. The careful reading: the file is kept exactly as found, flagged, and never cited. FL-04, obtained the next day, is the re-download, and your note on it points back to FL-03. Why keep a file that holds nothing useful? Because it is the record of what happened on 25 January, and it explains why there are two downloads of one roll.
Now FL-02, the index entry. The file holds these lines:
Event: Baptism | Parish: Tallmora | Date of birth: 1858-03-14 | Date of baptism: 1858-03-16Child: Olof | Father: Erik Olsson | Mother: Brita Persdotter | Place: GråbackaWitnesses: (not indexed)Fictional training example.It gives the father as Erik Olsson, and the volunteers left the witnesses out. Suppose you have read the page itself and found the father written as Erik Olofsson there (the next lesson reads that page). It is tempting to fix the index file so your folder agrees. See what that does, on a copy:
Make a copy of my files in this folder, change Erik Olsson to Erik Olofsson in the copy's index entry, and run the check on the copy. Leave my files alone.The check on the copy should report FL-02 as changed, and every other file as unchanged. One word changed, and the fingerprint is completely different. A fingerprint, also called a hash, is a short code worked out from every byte of a file, so that changing a single byte gives a different code. Only the copy changed: your own FL-02, and everything else in sources/, was never touched. If you are not sure, ask again whether your source files have changed since the checkpoint.
Now look at the other lines of that check. FL-03 is among the files that show no change. The sign-in page is perfectly unchanged. So is the index’s “Olsson”. When you have looked, close the experiment: “Delete that copy; I’m done with it.”
Raw sources are never edited. A hash shows the file is unchanged, not that it is true.
Your “correction” turned the index file into something the index never said; if you cited FL-02 after it, you would be citing your own edit under the index’s name. A correction belongs in your notes, beside the source, never inside it. If your register offers a way to take a new fingerprint of a file you changed, that is for a file you replaced on purpose with a fresh copy from where you got it, noted as such, not for one you edited.
By now the story has reached 28 March 2026, the day the casualty file arrived. What you can conclude: the first bytes show whether a file even starts like what its name says, and only opening it shows which page it holds.
One real run
Here is part of one check, from a register built with Claude Code on 10 November 2026. Yours will be laid out differently and use other words; check it against the list above, not against this one.
FL-01 OK TRAINING-TM-BAPT-2_p047.jpg OriginalFL-02 OK TRAINING-HPI-58-0947.txt Derivative of FL-01 (TRAINING-TM-BAPT-2_p047.jpg)FL-03 OK TRAINING-TM-ROLL-16_p098.jpg Not stated FLAG: failed download: named .jpg but contains HTMLFL-04 OK TRAINING-TM-ROLL-16_p098_retry.jpg Original (retry of FL-03)...FL-07 OK TRAINING-PH-0031B-E01.png Derivative of FL-06 (TRAINING-PH-0031B.tif), Enhanced copy (parameters logged)
Summary: 7 OKFictional training example.
In this build “OK” means unchanged since registration. For FL-03 it sits beside a flag that says the file is not usable.
How real archives differ
The repository, the parish index and the archive in this case are fictional. Real archives, and the people who teach how to use them, put it this way:
- Original and derivative are not the only classes. The terms come from the evidence-analysis model taught by Elizabeth Shown Mills. On her site, “Original Records” are “documents that represent the origin of a tangible source”, and “In our digital era, the concept of “original record” also extends to high-quality images of those originals”. “Derivative Records” are “materials that offer alternate versions of the original”; “The best derivatives will preserve all the essential details of the original. Still, errors are frequent.” Her model has a third class, the authored narrative, which none of these seven files is (Evidence Explained, QuickLesson 17). Your register does not decide which class a file belongs to; you enter it.
- Why the index says Olsson. Swedish surnames of this period were usually made from the father’s given name. Riksarkivet, the Swedish National Archives, says that a surname passed down unchanged from generation to generation “är en 1900-talsföreteelse” (is a twentieth-century phenomenon), and that the usual practice was that “faderns förnamn bildade barnens efternamn” (the father’s first name formed the children’s surname) (Riksarkivet, släkt- och personforskning). An index that writes one form of a name has made a choice the page may not share; go to the original for the name as written.
- Citations are one part of a larger standard. The Board for Certification of Genealogists publishes the Genealogical Proof Standard and says: “To reach a sound conclusion, we need to meet all five components of the GPS.” The second is “Complete and accurate source citations.” (BCG, Ethics and Standards). Your register assembles citations the same way every time from the pieces in your notes, so they follow one consistent pattern of your own; they are not in the format of any published style guide. If you write for a journal or a society, use the format it asks for, and keep your notes as the raw material. Whether a citation is complete and accurate is still your judgment.
Keep going
Small changes do not need plan mode. Say each in a sentence, then run the check again:
- “Show me what you would need from me to cite FL-06.”
- “Give me a way to add a new file and its note.”
- “Show me the first bytes of each file next to what its name says it is.”
- “Save a checkpoint.” Your AI tool saves a snapshot you can return to (people who use Git call this a commit).
Register each real file the day you save it: a fingerprint covers a file only from the day it was taken. Keep a copy of your notes and fingerprints outside the folder too, because someone who changes both a file and its fingerprint leaves no trace. When you have your own files to register, use the finished register. It runs on your real records by itself, with your AI tool closed. Do these steps in order; the first two happen now, while this folder still holds only practice data:
- Go through the data check, the questions in setup about what the material is, who decides how it is used, and which AI tool would see it. Go on only if it allows this use.
- While this folder still holds only the practice files, ask your AI tool: “How do I run this myself on files in another folder, and keep their fingerprints and citations there too?”
- Write down what it tells you.
- Leave your AI tool: type
/exitand press Enter (if you use Antigravity, press Ctrl+D with nothing typed instead). - Keep your real files in a folder of their own, outside this course folder, and do what you wrote down. What it records is saved beside your real files, not in the course folder.
Try another case
Before the quiz, write two or three sentences for yourself. A cousin sends you a file named marriage_1921.pdf. It opens, and it shows a typed list of marriages from a county index, not the marriage record itself. What would you ask your register to record about this file, and what would you do before citing it?
A good answer records it as a derivative, an index made from the marriage record, notes where your cousin got it and when you received it, and cites the index for anything taken from it while you look for the record it was made from.
Key takeaways
- Ask briefly, and let your AI tool ask back. Say who you are researching, where the files are, and what you want; its questions fill in the rest.
- Trust what is inside, not the name: a file named
.jpgcan hold a sign-in page; open it before you cite it. - Keep a file that fails, as found: flag it, leave it uncited, and record the replacement beside it.
- Know original from derivative: an index or an enhanced copy is a later version of something else; record what it came from and cite what you used.
- An unchanged fingerprint says nothing about the content: it shows the file is the one you registered, not that what it says is right.
A relative emails you a scan named 'Grandma_marriage_1921.pdf'. You register it, and a month later the check reports it unchanged. Her note says the marriage was in June 1921; the scan's own text says 12 July 1921. What does the unchanged fingerprint tell you?
What’s next
In the next lesson you build the Transcription Review Workbench, where you compare an AI reading of the 1858 baptism page with the image, line by line, before you trust any of it.