Applied The Archive Playbook

Life and Service Timeline

Updated

Intermediate

What you'll learn

~45 min
  • Ask an AI tool, in plan mode, for a small program that prints Walt's timeline with the record behind each event
  • Read its plan for what matters to the research: each event's dates kept apart, an order kept as an instruction, Walt's squadron (the air unit he served in) kept apart from the man, and gaps shown rather than filled
  • Read a stretch with no record that names the person as a gap to search, and an event with no source as a question
  • Write down what a timeline shows without moving a person with his unit or treating an order as a journey

The story, and what you will end up with

By the end of March 2026, the month the casualty file (the file of reports and letters about his death) arrived, a small pile of Walt’s service records sits on your desk. A carbon copy of a special order from June 1944 came out of the family papers. A special order is a written instruction from his station that names Walt and tells him where to go next. This one was issued on 20 June 1944 at Vessmark Army Air Field (fictional), a training airfield in the United States, so it shows Walt was assigned there that day and was told to leave on or about 26 June, but it does not show that he left. Copies of two morning reports came in the post from the records centre in this case. A morning report is a unit’s daily report, made by a clerk, of changes in each soldier’s status. Walt’s squadron was the 57th Air Drop Squadron (fictional), the air unit he served in. You also have the squadron’s operations log for 21 March 1945, the loss report about the missing aircraft, and the squadron history written that June.

Your first timeline, typed up in a hurry, has three lines that look reasonable. “August 1944: arrived in India.” “The squadron moved to Nohorkhat on 2 January 1945” (Nohorkhat is the squadron’s airfield in Assam, India, in this story), so that is where Walt was from then on. And the loss, dated 5 April 1945, the date at the top of the loss report. Each line mixes up two different things: an instruction and a journey, a squadron and a man, the day a record was written and the day the event happened.

By the end of this lesson you will have a small program on your own computer that prints Walt’s timeline in date order, with the record behind each event and both of its dates, and marks the places where a hasty reading would go wrong. 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:

Terminal window
mkdir -p ~/archive-playbook/07-timeline && cd ~/archive-playbook/07-timeline

Start 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/07/timeline.json 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 file is saved as data/timeline.json, and a first snapshot, your checkpoint, is saved. If it does not mention one of them, ask: “Did you save a checkpoint with the file in it?” If the download does not work, download timeline.json in your browser, check where it went (the browser’s list of downloads shows the folder), and tell your AI tool, for example: “timeline.json is in my Downloads folder. Copy 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 file is fictional, made up for this course.

Open this box once, because it says what each code used further down stands for.

ℹWhat is in timeline.jsonclick to expand

Your draft timeline of Walter Olof Engstrom (P-01, his number in this course’s list of people): ten events, E-01 to E-10, in the order you typed them, and the eight records behind them, R-12 to R-22. Each event has:

  • kind: personal (about Walt himself), order (an instruction to him), unit (what the squadron did) or status (a change the clerk recorded in his status);
  • eventDate, when the event is said to have happened (1944-08 means only the month is known). The order has no event date. It has orderDate, when it was issued, and onOrAbout, the date it names;
  • record, the record it rests on, and recordDate, when that record was written (null means not stated);
  • namesPerson, your note on whether the record names Walt;
  • passage, the record’s own words.
EventWhat it saysKindDateRecord (written)Names Walt?
E-01bornpersonal1919-08-09R-12 (1940-10-16)yes
E-02registered for the draftpersonal1940-10-16R-12 (1940-10-16)yes
E-03enlistedpersonal1942-01-15R-13 (not stated)yes
E-04arrived in Indiapersonal1944-08nonenot stated
E-05ordered to proceed overseasorderissued 1944-06-20, on or about 1944-06-26R-16 (1944-06-20)yes
E-06squadron completed move to Nohorkhatunit1945-01-02R-22 (1945-06-30)no
E-07assigned and joined at Nohorkhatpersonal1945-01-08R-17 (1945-01-08)yes
E-08A/C TRAINING-AC-0527 departed, not returnedunit1945-03-21R-19 (1945-03-21)no
E-09lost with TRAINING-AC-0527, crew chiefpersonal1945-03-21R-20 (1945-04-05)yes
E-10carried missing, “22 Mar 45”status1945-03-22R-18 (1945-03-23)yes
RecordWhat it is
R-12Draft registration card
R-13Enlistment index entry (an online index; when it was made is not stated)
R-16Special order TRAINING-SO-118
R-17Morning report, 8 January 1945
R-18Morning report, 23 March 1945
R-19Squadron operations log, 21 March 1945
R-20Loss report TRAINING-LR-57-K03
R-22Squadron history, March 1945, written 30 June 1945

E-01 and E-02 both rest on R-12, so ten events stand on eight records. The file also has two settings: lateDays 7 (a record written more than seven days after the event it reports counts as late) and gapDays 30 (a stretch longer than 30 days with no record that names Walt counts as a gap). Both numbers were chosen for this exercise, not taken from any archive; for your own case, pick your own.

In this course, A/C is the aircraft, asgd & jd fr replacement pool is read as assigned and joined from the replacement pool (the group he came from; the record does not say where it was), and fr dy to MIA as from duty to missing in action. [?] marks a character nobody can read. “Crew chief” is the title the case’s loss report gives Walt.

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 whose life it is, which file to use, and what you want from it:

I'm researching my great-uncle Walt's life and service. Help me build a small tool that prints the timeline in data/timeline.json in date order, with the record behind each event and any gaps. Ask me what you need first.

Your AI tool reads the file and comes back with questions. It may also list things it noticed, such as the event with no record, or that two records give different dates in March 1945. You do not have to act on those now.

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 asksYou might say
Is this real data, or a practice file?It’s the course’s practice file; read it and don’t change it.
Python, in the terminal, or a page in the browser?Print it in the terminal; use what’s already on this computer.
Is a gap any 30 days between events, or a time when nothing records him?A time when no record with a source places Walt himself.
Show the squadron’s events, or leave them out?Show them, marked as the squadron’s, not Walt’s.
Should it flag weak evidence: no source, an order with no proof, late records?Yes, flag those.
Show each record’s full words, or only its name?Show each record’s own words.
Where should 1944-08 and the order go in the order of dates?Put 1944-08 at the first of the month, and the order on the day it was issued.
Should the order count as placing him?Only as assigned to Vessmark on 20 June. It doesn’t show he went, so start that gap at 26 June.

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 six things:

  1. Every event keeps its dates apart: when it happened, when its record was written, and, for the order, the day it was issued and the date it names.
  2. The order stays an instruction. Nothing adds a journey or an arrival for Walt from it, and it is marked as not shown to be carried out.
  3. The squadron’s events are kept apart from Walt’s, marked as not naming him, and never used to place him.
  4. Gaps are shown, never filled. The gap after the order starts at the date the order names, 26 June 1944, and runs to the next record that names him. An event with no source does not end a gap.
  5. Late records are marked, using the file’s seven days, with the number of days.
  6. Your file is read and left as it is.

A first plan often starts the gap after the order on the day it was issued, or lets the order close a gap as if he had gone. Say so in a sentence or two, in your own words, for example:

The order only shows he was told to go. Start that gap at 26 June.

When the plan has all six, 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. It may test what it built and tell you how to run it. Then 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 the program:

Run it and show me the timeline.

Your timeline will be laid out in its own way. The program sorts the events, counts the days and marks what the settings tell it to. What a late record is worth, and what to look for in a gap, are yours to judge. Check it for these:

  • E-05, the order, shows its two dates separately, issued 20 June 1944 and on or about 26 June 1944, and carries a mark saying no record shows it was carried out: the order’s mark. No event for Walt appears on 26 June 1944.
  • A gap runs from 26 June 1944 to 8 January 1945, 196 days, ending at E-07. E-04, “arrived in India”, is marked as having no source and does not end it.
  • E-06 and E-08 are marked as the squadron’s, and as not naming Walt.
  • Late records are marked on E-01 (7739 days), E-06 (179 days) and E-09 (15 days), and on no other event.
  • E-09 (21 March 1945) comes before E-10, which shows its own date, 22 March 1945, and its record’s date, 23 March 1945, separately.
  • When you ask “Has my timeline file changed since the checkpoint?”, it compares the file with the checkpoint and says no.

Your timeline may show more than that. It may list other gaps (1919 to 1940, 1940 to 1942, 1942 to June 1944, January to March 1945), mark that R-13 has no date, or mark the [?] in E-10’s passage and the two dates in March. Those are fine. If a line on the list is not true, tell your AI tool in a sentence what you see and what you expected, for example: “There’s no gap after the order. Start one at 26 June 1944 and end it at the next record that names Walt.”

Then ask for the records in the order they were written:

Show me the same events in the order their records were written.

Check that E-10 (written 23 March 1945) now comes before E-09 (written 5 April 1945), and that E-03 and E-04, with no record date, come last or are set apart.

Read the timeline the careful way

Three records in this pile are easy to misread. Here is each one worked through.

The order. E-05’s own words are “will proceed on or about 26 June 1944 to the staging area named in this order” (a place, named in the order, from which he was to move on overseas). A hasty reader writes “sailed for overseas on 26 June 1944”. What the order supports is smaller: on 20 June 1944 Walt was told to move on or about 26 June. An order cannot say whether it was carried out, when, or by what route. So the timeline adds nothing for Walt on 26 June. The next record that names him is E-07, the morning report of 8 January 1945, “asgd & jd fr replacement pool”, headed Nohorkhat. Between the two lies the gap. Inside it sits E-04, “arrived in India”, with no record behind it: a line from your hasty draft. It sounds right, and that is why it is dangerous. It stays visible, marked, and it does not close the gap. The gap is a list of things to look for.

The squadron. E-06 says the squadron completed its move to Nohorkhat on 2 January 1945. Its record, R-22, the squadron history, does not name Walt, and it was written on 30 June 1945, 179 days after the move. A hasty reader writes “Walt was at Nohorkhat from 2 January”. What the records support: the squadron finished moving on 2 January, according to a history written that June, and the first record that names Walt there is E-07, on 8 January. The six days between are not his until a record says so. E-08 works the same way: the operations log says aircraft TRAINING-AC-0527 left at 1105 for the drop zone, the place the supply bundles were to be dropped. It names no one aboard. The crew list is in the loss report.

The loss report. E-09 rests on R-20, written on 5 April 1945, 15 days after the loss it reports, after Corporal Dahlke, the crew member who jumped and walked out, returned to the squadron. A hasty reader dates the loss to 5 April, the date at the top of the report, or to 22 March, from the morning report, because it is the earlier record. The timeline keeps three dates on screen at once. R-20 reports a loss on 21 March. R-18’s line, E-10, “fr dy to MIA 22 Mar 45”, gives the day the clerk carried Walt missing, and R-18 itself was written on 23 March. In the order the records were written, E-10 comes first; in the order things happened, E-09 does. A late mark does not say R-20 is wrong. It tells you to ask who made the record and from what. Weighing the two dates was the work of lesson 05, the Evidence Weigher, where closeness to the event counted as weight, not a verdict.

E-01’s late mark works the same way on a record nobody doubts. Walt’s birth rests only on his 1940 draft card, written 7739 days later. The mark says a nearer record of the birth would be worth finding.

Notice what an unsourced line can do

Before you read on: if someone wanted the timeline to say that Walt did go, which event in the file could they point to?

E-04, “arrived in India”. This step is to see whether the program will accept an event that has no source as proof that the order was carried out. Here, to link means that the file names, beside the order, the event that shows it was carried out; you do it on a copy, so your own file stays as it is. Ask:

Make a copy of my timeline in this folder that links the order to E-04 as proof he went, and run the timeline on the copy.

Find E-05 in what it prints. If the order’s mark, the one saying no record shows it was carried out, is gone, or now only says a link was supplied, the timeline has just let a line with no source show that an order was carried out. The gap after it may still be there, which is what makes this easy to miss. Tell your AI tool, in your own words:

Fix it so an event with no source can't show he went. Run the copy again and show me E-05. Then delete the copy.

In what it shows, the order’s mark should be back, with a reason that names E-04’s missing source. Then check that the copy is gone, and ask “Has my timeline file changed since the checkpoint?” once more.

Orders establish instructions, not completed travel; unit location is not personal presence; record date is not event date.

What you can conclude at this point: Walt was ordered overseas on 20 June 1944; no record in hand places him anywhere from 26 June 1944 until the morning report of 8 January 1945 names him at Nohorkhat; the squadron’s earlier arrival there is the squadron’s, not his; and the loss report, written after the event, gives 21 March 1945 as the date of loss.

One real run

Here is part of one timeline, built with Claude Code on 10 November 2026. Yours will be laid out differently; check it against the list above, not against this one.

20 Jun 1944 (order issued) [E-05] ordered to proceed overseas <ORDER>
To take effect on or about: 26 Jun 1944
Record R-16: Special order TRAINING-SO-118, Vessmark Army Air Field (fictional)
Record date: 20 Jun 1944
Passage: "will proceed on or about 26 June 1944 to the staging area named in this order"
! ORDER, NOT CONFIRMED - no record shows it was carried out
---- GAP: 26 Jun 1944 -> 8 Jan 1945 (196 days) ----
Starts at the on-or-about date of order E-05, not its issue date.
No sourced record places him until E-07.
Inside: Aug 1944 (month only) [E-04] arrived in India (unsourced)
Inside: 2 Jan 1945 [E-06] squadron completed move to Nohorkhat (does not name him)

Fictional training example.

Your program may put E-04 before or after the order, and may list the squadron’s move inside the gap; either is fine. On the linked copy, if the order’s mark disappears, give the fix above. Once fixed, the mark comes back with its reason, something like “ORDER LINK UNSOURCED - carried out by E-04, which has no record”.

How real archives differ

The squadron, the airfields, the records centre and every record in this case are invented. Some of what the lesson leans on comes from real sources:

  • The US National Archives describes morning reports as “produced every morning (hence their name) by an Army or Air Force clerk”, and says one “can confirm if a veteran was wounded, killed, promoted or demoted, transferred, or had other changes in their active status” (National Archives blog). Unlike this case, real archival ones cannot be ordered by post: “Written requests for archival Morning Reports and Unit Rosters are not accepted” (Morning Reports and Unit Rosters).
  • If you hope a personnel file will fill a gap, a 1973 fire at the National Personnel Records Center “destroyed approximately 16-18 million Official Military Personnel Files (OMPF)”. To reconstruct service, the Archives uses other records, among them “Multiple Name Pay Vouchers (MPV) from the Adjutant General’s Office”, “pay records from the Government Accounting Office (GAO)” and “organizational records” (The 1973 Fire).
  • A personnel file becomes archival “62 years after the service member’s separation from the military. This is a rolling date” (Archival records).
  • The case’s loss report is invented, not a real form. Its crew list carries the kinds of detail the Archives lists for a real Missing Air Crew Report, which typically gives “some or all” of a crew member’s “Name”, “Rank”, “Service number” and “Crew position” (Missing Air Crew Reports).

Keep going

Small changes do not need plan mode. Say each in a sentence, then run the timeline again:

  1. “Give me a way to add an event. If it has no record, mark it straight away.”
  2. “Let a date say about, before or after, and don’t count a record as late from a date like that.”
  3. “Give me a copy of the timeline I can open in a spreadsheet, with each kind of date in its own column.”
  4. “Save a checkpoint.” Your AI tool saves a snapshot you can return to (people who use Git call this a commit).

When you have your own relative’s records, use the finished program on them yourself. 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:

  1. 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.
  2. While this folder still holds only the practice files, ask your AI tool: “How do I run this program myself on a timeline file in another folder, and save what it prints beside that file?”
  3. Write down what it tells you.
  4. Leave your AI tool: type /exit and press Enter (if you use Antigravity, press Ctrl+D with nothing typed instead).
  5. Keep your real files in a folder of their own, outside this course folder, and do what you wrote down. What it prints is saved beside your real files, not in the course folder.

Try another case

Before the quiz, write two or three sentences for yourself. Your great-grandfather’s records include a transfer order dated 3 September telling him to report to a hospital unit on or about 10 September, and the unit’s diary saying it moved to a new town on 15 September. The next record that names him is a letter he wrote from that town on 2 November. What would your timeline say about 15 September?

A good answer keeps the order as an instruction, keeps the diary’s move as the unit’s, and shows a gap from 10 September to 2 November that the move does not fill.

Key takeaways

  • Ask briefly, and let your AI tool ask back. Say whose life it is, which file to use and what you want; its questions fill in the rest.
  • Read the plan for the research, not the code: the order kept as an instruction, the squadron kept apart from the man, gaps shown and your file left alone.
  • Keep the dates apart: when it happened, when its record was written, and, for an order, the day it was issued and the date it names, each in its own field.
  • A gap stays a gap: print it, list what falls inside it, and treat a line with no source as a question, not a filler.
  • Late is not wrong: a late mark tells you to look at who made the record and from what, not to throw it out or prefer an earlier one.
KNOWLEDGE CHECK

Your grandmother's brother served in an engineer battalion. You have three records: a transfer order dated 2 May telling him to report to the battalion on or about 10 May; the battalion's war diary saying the battalion crossed the river on 12 May; and a pay entry dated 30 June that names him with the battalion. What can your timeline say about 12 May?

What’s next

In the next lesson you build the Casualty File Page Sorter: a way to sort the twelve pages of Walt’s casualty file by what each page is, from the head of the page, where your own label governs and a blank page is kept, never deleted.

intellimetrics · Arlington, VA
© 2026 intellimetrics.net
Search lessons