# Sessions end (the 70-page edition, being written, online) > the 70-page edition, being written: Sessions end, with the record each scene rests on. *Source: · site v0.1.419 · generated from the same content as the page, so the two cannot drift.* --- The 70-page edition, being written, online: under each scene, what it rests on. Made by `review/tools/make_editions.py` from the writer's chapters. # Sessions end **Cast bar:** the nine fade. This book's own team begins to light. ### 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. **Rests on** talk repository at [`298be4e`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/298be4e): team/*/ROLE.md team/*/policy.json team/*/wakes team/*/debriefs 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. **Rests on** [`49c701e`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/commit/49c701e) (his paper review of RC1, 31 October 2026, 01:48 UTC: "it's just a footnote") [C089](#claim-C089) (editor_31_October: "just a footnote"; he could have moved to another session) [`timeline/after-the-day.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/timeline/after-the-day.md) 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. **Rests on** this book's repository: [`team/conductor/handovers/storyteller.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/team/conductor/handovers/storyteller.md); [`team/conductor/WAKE.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/team/conductor/WAKE.md) (Handing over, H1, signed 30 October 2026); book.json H1; [`team/storyteller/sessions/`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/tree/dev/team/storyteller/sessions) (two SESSION.json files, one superseded) 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.* ### 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. **Rests on** [`team/conductor/WAKE.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/team/conductor/WAKE.md) (the checklist, steps 1, 2 and 7); team/*/status.json, team/*/debriefs/ (this book's) 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. This book's own repository: the conductor's handover for the storyteller, the handover rule the editor signed, the storyteller's two sessions, and the wake rules. The storyteller's outline for this chapter. No key, fingerprint or session id is printed here; the key register is described only. **Rests on** talk repository at [`298be4e`](https://github.com/SGit-AI/SGit-AI__Website__Presentation__The-Ultimate-Insider/commit/298be4e) (team/); [`claims/register.json`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/claims/register.json) [C089](#claim-C089); [`timeline/after-the-day.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/timeline/after-the-day.md); this repository: [`team/conductor/handovers/storyteller.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/team/conductor/handovers/storyteller.md), [`team/conductor/WAKE.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/team/conductor/WAKE.md), book.json H1, [`team/storyteller/sessions/`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/tree/dev/team/storyteller/sessions); [`chapter-plan/edition-70-outline.md`](https://github.com/SGit-AI/SGit-AI__Website__Book__The-Ultimate-Insider/blob/dev/chapter-plan/edition-70-outline.md) part 5 chapter 13 ## The numbers in this chapter From the researcher's register (`claims/register.json`). - **C089** Why the team stopped: the editor's own account, given after the day, against the day's record: - day_record: **the hold at 18:44:13 gives the editor's usage at 95% as the reason, in the conductor's words (C006, C021); the locks were built and never applied (C027)** - editor_31_October: **the 95% was 'just a footnote': he could have moved to another session; the main reason was that there was no tested way to take in changes during the talk, no UX to see what was new and no workflow that made sure nothing would break, 'the reason why I was thinking about let's lock V1'** - editor_31_October_19:00: **'The 95%, I think, was the tokens usage. That there was a token that we stopped, and there was a big thing about 95%.' (briefs/2026-10-31__in-session/02-g1-the-95-and-the-day-in-review.md, ec1ec00)** - what_the_record_shows: **the hold's subject: 'the editor's usage limit is at 95%, pause all actions' (867f8c2); C021: 95% is the conductor's words reporting the editor, about a 5-hour usage window resetting at 20:20 London (C037); no usage page, no token count** - what_the_record_cannot_show: **whether the 95% was of tokens, of a message allowance or of anything else: the record holds the percentage as reported and nothing it was measured in** open --- *[Site index for agents](../../llms.txt) · [HTML version](https://the-ultimate-insider.book.sgit.ai/review/rc2-70/13-sessions-end.html)*