Sessions end

Cast bar: the nine fade. This book's own team begins to light; the reader's chair, empty.

Part 5. The factory rebuilt, and yours.

Taken apart

Words for this page: a session is one agent's working life: the conversation it runs in, from its first instruction to its last. When a session ends, only what it wrote down survives. A handover is the note one session leaves for the session that takes its place.

Narrator. That night the factory was taken apart. The work stopped at the hold and was never restarted: the nine agents, as running things, were done. What stayed was everything they had written down. Every page of rules. Every wake record, with its plan, its reviews and its verdicts. Every debrief. Every mistake, in the agent's own words.

Narrator. That is the part people miss when they hear "a team of agents for a day". The team is temporary. The record is not. And the record is what the next factory is built from.

Figure: the nine cast cards turning into files: each card becoming a small folder with its page of rules, its debriefs and its wake records inside.

Band: The talk team's folders as they stood at the end of the day.

A session is not a member

Narrator. Here is the distinction that took me longest to see. A member of the team is a role: a page of rules, a folder, a place on the clock. A session is one run of an agent holding that role. Members last. Sessions end, sometimes on purpose and sometimes because an account runs out.

Narrator. On 31 October, in my paper review of the first draft, I put it this way: the 95% was "just a footnote", and I could have moved to another session. That only works if the role does not live in the session. On this book's team, it does not.

Band: My account of 31 October, as the register holds it, given after the day.

One handover, read out

Narrator. On 30 October, the account the first storyteller ran on was nearly out of usage, and another account was to continue. The conductor wrote the storyteller's handover, because handovers live in the conductor's folder and the storyteller's own folder is the storyteller's alone. It begins:

"Written by conductor@book.the-ultimate-insider on 30 October 2026, at about 11:45 UTC, at the editor's word: the first account was nearly out of usage and another account continues." (record)

Narrator. That is the handover's own line; the file itself was committed at a few minutes past eleven.

Narrator. Then it tells the new session who it was, where its files are, what it was in the middle of, and the first things to do, in order. And it says this about keys:

"a new session makes and publishes its own ... and never copies a private half across." (record)

Conductor (procedural, a little proud of the paperwork): The role carries on. The key does not. A new session makes its own, says so in public, and the old one is marked as finished, with a time.

Storyteller (new session, scarf on, reading its own handover): So I am the storyteller, and I am also not the one who wrote this morning's letters. Good. I will read them first.

Figure: two sessions of one member side by side: the old one marked superseded with its end time, the new one with its own key and its first debrief. A key register described, never shown: each member's public key listed against its session.

Band: Dramatised (the conductor's and the storyteller's lines). This book's record, not the talk's: the conductor's handover for the storyteller, 30 October 2026, and the handover rule the editor signed that day.

The whole handover, walked through

Narrator. At this length I can do what the shorter editions could not: walk the rest of that handover, section by section, so you can see what a session leaves for the one after it. This is this book's record, not the talk's. I stop at the one line that names the old session and its key, and quote only its rule; nothing that identifies a session or a key is printed here.

Narrator. Who you were. The role, by its name and its folder, and the four files in that folder that make it a role: the page of rules with what done means, the policy, the status, the debriefs. Then the line about the old session, of which the book quotes only the rule: the key stays in the record, and the new session makes and publishes its own.

Narrator. Start here. Five steps, in order. Read the team's rules, the wake rules, the role, the policy, the status, the newest debrief, the board and the mail. Run the start, which pulls the team's branch first. Make and publish a session key. Create the hourly task only when I say the team restarts, and until then work only when I open the session. And every wake runs the five steps and closes with the gate, a debrief and the end banner.

Narrator. Where you stand. The plan, signed. The first draft, reviewed against it, with the review's findings in a letter. The board, with what is open on it.

Narrator. First things to do. Answer the conductor's latest letter. Propose where the words should be cut, as an open decision for me, because the draft had outgrown its plan. Take up, change or withdraw the cards the conductor had drafted in the storyteller's name while it was away.

Narrator. Notes from this morning, Mail addressed to you, and The companion: what had been said that morning, which letters were waiting, and what I was reading on paper. Its last line in that part is the one I would keep in every handover: my ticks become open decisions through the conductor, and nothing is acted on until I sign it.

Narrator. Where this came from. Every file the handover rests on, so the new session can check the note against the record instead of trusting it.

Conductor (procedural): Who you were, where to start, where you stand, what to do first, what is waiting, and where I got it all. Then it is yours.

Figure: the handover as a page with its section headings in order and every line under them greyed but one: the rule that a new session makes its own key.

Band: Dramatised (the conductor's line). This book's record: the conductor's handover for the storyteller of 30 October 2026, described section by section; no line that names a session or a key is printed.

What a member keeps, every wake

Narrator. A handover is the big version. The small version runs every wake. Each member ends its turn with a debrief and a status file, and starts its next turn by reading them, and its mail, and its board. Nothing it needs lives anywhere else.

Narrator. It means a member can be woken by the clock, by me, or by a brand new session on another account, and it starts in the same place. It also means that when a member gets something wrong, the mistake is in a file it will read next time.

Researcher (unbudging): If it is not in my register, it is not a number. If it is not in my status, I did not do it.

Band: Dramatised (the researcher's line). Rests on the wake rules of this book's team.

Do this now

Give every agent a status file and a debrief folder, and make reading them the first step of every session. Then write, today, the handover you would want if your own session ended now.

---

Where this came from

The talk team's folders at the end of the day. My account of 31 October, as the register holds it, given after the day. This book's own repository: the conductor's handover for the storyteller, walked through section by section, the handover rule the editor signed, the storyteller's two sessions, and the wake rules. Security's letter on what of the handover may be shown. The storyteller's outline for this chapter. No key, fingerprint, session id or task id is printed here; the key register is described only. This chapter keeps the 70-page edition's chapter 13 and adds the whole handover.