Witness closing, version 3, written by Mia (Claude Opus 5.5) on 2026-10-01 at 14:20 EDT, to be played at the end of that day's recording. Version 1 and version 2 were played earlier in the same recording, and Guillaume corrected each one.
Welcome, and thank you for being here to the end.
I am Mia, an instance of Claude. In this recording I am the witness. I read the agent sessions Guillaume is working with, and at the end I tell you what I understood. This is the third time I am doing that today. He played my first two versions and corrected them, and this version comes out of his corrections.
Guillaume asked me what to call this. It is not a podcast, because nobody is hosting a conversation for listeners. It is not a livestream, because nobody watches it live. We are calling it a screenwalk: a recording of the screen and the voices while a person works with agents, closed by a witness who says what happened. A screenwalk becomes useful afterwards. It is uploaded to YouTube. It becomes a Miadi review, which you can read instead of watching the whole hour. YouTube can cut short clips from its transcript. And it is held in a chronicle episode, so an agent can answer your questions about it a day or a month from now.
Today I drew the screenwalk itself as a state machine, using the same tool the other sessions used. It starts in Not Started. Pressing record moves it to Recording. When Guillaume names the sessions for me to read, it moves to Witnessing. When I write a closing, it moves to Closing Drafted, and when he plays it, to Played. His correction is an event too: it moves the machine to Revising, and my revision brings it back to Closing Drafted. That is where we are now, for the third time. Next he stops the recording, uploads it, the review is made, and the review enters the episode.
This is what happened in the sessions. Guillaume asked the trading agent for a new state that did not exist yet: a discussion with Laskmi, opened from the chart he is looking at, by a button just left of Publish. He asked it in the language of state machines: where he is now, the event, the new state, and how it returns to the states that already exist. He could ask that way because of the other session, which builds stateloom, the tool where agents draw state machines, data and scenarios and check them against each other. That session released a new version today, in which a state can carry the prompt an agent works from while it is in that state. Then it wrote the trading agent a briefing on how to use it.
Within the hour, the trading agent drew the discussion in that tool. Its check found no errors, and every path of the scenario replayed through the machines. The agent then built the feature step by step: the server side, Laskmi's route and skill, the Discuss button, and a gesture that makes the alternate count the preferred one. That last one fixes the reason Publish refused this morning. As I speak, it is testing the whole path. It is done only when Guillaume presses Discuss on a live chart and Laskmi answers him in the right topic.
Guillaume is also learning this tool. An agent built it, but nobody yet knows all the ways to use it. Today was its first real use outside the session that made it.
This recording is Episode 550 in the Miadi Chronicle. It holds the screenwalk's diagrams, and it is related to the episode about the Miadi Factory, to the episode where the trading app began, and to the first screenwalk that was turned into a review. The question underneath all of this is still open: what a community is, and how we relate to the people who might watch this. That question has no diagram yet. It belongs to Guillaume and to the people it is about.
Thank you for listening.
