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.

Get started Read the spec

One happening, many readings On the left, one episode: on Tuesday afternoon Ada renewed the status page certificate. It is recorded once and never revised. On the right, three readings of it, each citing the same record: one from that week, that it was renewed in good time, later revised; one from a year later, that it was renewed with three days to spare; and Jane's, that the warning came too late. The readings change and differ; the record stays as it was. what happened what was made of it Tue 17 Nov, 14:00–14:30 Ada renewed the status page certificate recorded once · never revised a reading, that week “renewed in good time” · revised a reading, a year later “renewed with three days to spare” Jane’s reading “the warning came too late” cites its own file, in your workspace
Readings change, and differ. The record they cite stays as it was.

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?

One conversation, two fates On the left, the conversation lives in one harness's chat history, per account and invisible to every other harness. The claim drawn from it, that the certificate was renewed on Tuesday, has nothing it can cite. On the right, the conversation is recorded in the person's own workspace, one turn at a time, each saying who spoke it. The same claim cites the turn in which it was said, and so knows whose word it rests on. a harness’s chat history episodes you · I renewed the certificate this afternoon. Can you log it? assistant · Logged. one harness · one account cites nothing it can reach a claim the certificate was renewed on Tuesday invisible to every other harness a conversation, in your workspace turn 1 · you “I renewed the certificate this…” turn 2 · the assistant “Logged.” a claim the certificate was renewed on Tuesday cites the turn, and who spoke it yours, and reviewed through git
The same conversation, kept by a harness and kept as a record.

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.

A trace, and content held inline On the left, a trace: an episode of Jane's email holds a pointer to where the mail lives, a way to tell whether it has changed, and enough to stand as a record after the mail is gone; the text stays in her mailbox. On the right, content held inline: a conversation with a harness has no other home, so the episode holds the words. Beneath both: every episode says whose experience or record it is. most episodes: a trace what has no other home: held Jane’s email where the mail lives a way to tell if it has changed enough to stand as a record after the mail is gone never the text itself her mailbox the text Your conversation with a harness the words themselves, held here, because nowhere else will keep them for you one turn at a time, each in its speaker’s name every episode says whose experience or record it is
Most episodes point. Only what has no other home is held.

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.

Three formats, one direction Three boxes in a row. Intentions: what a person means to do. The Dialectical Knowledge Format: what is believed. Episodes: what happened. Two arrows leave the knowledge format: a claim cites an episode as its evidence, and cites the intention it bears on. No arrow leaves episodes, which cite nothing outside their own workspace, and none runs between intentions and episodes: a claim citing both is what closes the loop between what was meant and what was done. what is meant what is believed what happened intentions what a person means to do with their time intentions.fyi Dialectical Knowledge Format what is believed particulars.fyi episodes what happened, and where the record lives this format cites cites a claim cites an episode as evidence and the intention it bears on an episode cites nothing in either nothing runs between intentions and episodes: a claim citing both closes the loop
The formats meet by reference, in one direction. Forgetting names the gap this one fills: without a record of what was done, there is nothing to compare with what was meant.

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.

A week of episodes, as the binary lists them One lane for each standpoint and one column for each day. A dashed box is a trace of something that lives elsewhere; a solid box holds content that has no other home; an accented box is an act the person attested; a conversation is drawn around its turns. An arrow is a link from one episode to another. A red badge marks a source that has gone, on the day it was observed; the trace remains. November 2026 Mon 16 Tue 17 Wed Thu Fri 20 Janehttps://example.com/people/jane Adahttps://example.com/people/ada assistanthttps://example.com/assistant email · standpoint https://example.com/people/jane · occurred 2026-11-16T09:12:00+11:00[Australia/Melbourne] (stated) · content: ref · label: Status page certificate expires Friday 09:12 · email Status page certificate expires… activity · standpoint https://example.com/people/ada · occurred 2026-11-17T14:00:00+11:00[Australia/Melbourne] to 2026-11-17T14:30:00+11:00[Australia/Melbourne] (stated) · content: attested · label: Renewed the status page certificate 14:00–14:30 · an act Renewed the status page certificate conversation · standpoint https://example.com/people/ada · occurred 2026-11-17T16:40:00+11:00[Australia/Melbourne] · 2 turns, in order conversation · 2 turns message · standpoint https://example.com/people/ada · occurred 2026-11-17T16:40:00+11:00[Australia/Melbourne] (recorded) · content: inline · text: I renewed the status page certificate this afternoon, from two until half past. Can you log it? · ordinal 1 16:40 · turn 1 “I renewed the status page… message · standpoint https://example.com/assistant · occurred 2026-11-17T16:40:20+11:00[Australia/Melbourne] (recorded) · content: inline · text: Logged: renewed the status page certificate, Tuesday 14:00 to 14:30. · ordinal 2 16:40 · turn 2 “Logged: renewed the status page… source_status: gone · verified 2026-11-20T10:00:00+11:00 · the episode keeps its place 10:00 · source gone the trace remains via a trace: the content lives elsewhere inline: this is its only home an act the person attested a container, its turns in order 5 episodes · drawn by episodes 0.2.0
The week of 16 November 2026, as the binary lists it. The mail is gone from Jane’s mailbox and the trace of it isn’t: a source being deleted is not a request to forget. Hover a box for the output it was drawn from. Clone the workspace and run it yourself.

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.