Episodes · an open format for episodic memory
You don’t reconcile the past.
An open format for what happened: when and where, from whose point of view, and where the record of it lives. Beliefs about an event change; the event doesn’t. Written by harnesses and connectors, reviewed by people through git. An early draft, with a reference implementation.
After Kierkegaard: “Life can only be understood backwards; but it must be lived forwards” (Journals, 1843, tr. Dru). Episodes hold the backwards, what Heidegger calls having-been (Being and Time, §65).
One conversation, two fates
You tell your assistant you renewed the certificate on Tuesday afternoon. Later, something is believed because you said it. When that belief is questioned, what can it point to?
The thing a claim most often comes from is the one thing it can’t cite.
Chat history
Proprietary, per account, and invisible to every other harness. The place most of what a person tells their assistant ends up, and the one place nothing else can point to.
A belief about it
Written into a knowledge base, the event becomes a claim, open to reconciliation, contradiction and synthesis, none of which apply. You don’t reconcile a past event, only beliefs about it.
The plan for it
A planning format holds what a person means to do. A retrospective account of what they did is, by its own say-so, not its job.
Whose memory is it?
Two people live through the same meeting and take different things from it. So every episode says whose experience or record it is, and every turn of a conversation says who spoke it. Nothing downstream can recover that if it isn’t written down.
It records. It never interprets.
An episode carries nothing that is a judgement: no topics, no confidence, no sentiment, no summary, no claim that it went well. Each of those is a reading, and a reading belongs to another format, where it cites the episode. Episodes are not revised. A better transcript is a new episode, not an edit of the old one, and forgetting is always explicit: a person can withdraw what was said, and the record keeps its place and says who removed what, when and why.
Read by a second reader
A reference implementation was written from the specification. Implementing it raised eighteen points where the draft hadn’t decided; ten are now settled in the text, and eight are open. Below is that binary’s own output on the example workspace in this site’s repository: Jane’s email saying a certificate expires on Friday, the conversation in which Ada said she had renewed it, the act she asked to have logged, and the email gone from the mailbox by Friday.
Start in your terminal
Install the CLI, make a workspace, and record what happens: a conversation as it is spoken, an act only when you ask for it, a trace of anything that already has a home.
$ brew install nodelogicau/tap/episodes
$ episodes init ./memory --author you --zone Australia/Melbourne
$ cd memory
$ episodes conversation start --standpoint you \
--text "I renewed the certificate this afternoon, from two until half past."
$ episodes act --label "Renewed the certificate" --basis stated \
--occurred 2026-11-17T14:00:00+11:00 --end 2026-11-17T14:30:00+11:00 --via <turn>
$ episodes record ref --kind email --standpoint jane \
--ref "mail:inbox/4471" --occurred 2026-11-16T09:12:00+11:00 --basis stated
$ episodes list
$ episodes query certificate
Every file is one episode, in plain YAML, so what was recorded about you is something you can read, review through git, and withdraw.
Today: an early draft of the specification, with nothing yet declared, and a reference implementation, episodes-cli v0.2.0, that writes, recalls and validates it. · Open: the questions the specification lists, among them how large a conversation episode should be, and how a claim cites a span of a source rather than the whole.