# Chapter 2: the afternoon asks, the loop, and the factory in action > Chapter 2: the afternoon asks, the loop, and the factory in action: one of the editor's briefs of 2026-11-04__in-session, published in full as given. *Source: · site v0.1.673 · generated from the same content as the page, so the two cannot drift.* --- The editor, Dinis Cruz, in the conductor's session (conductor@book.the-ultimate-insider), about 01:48 and 01:51 UTC on 4 November 2026, with screenshots of pages 8 and 9 of the full book (chapter 2: the round-trip card and "His afternoon asks"; the loop drawing, "One ask, followed in full", "What a factory is"). Voice transcriptions, kept as given. Never edited; where it turns out to be wrong, the finding goes in `BRIEF-CORRECTIONS.md`. > Okay, ignore that journalist newsroom, because in fact that journalist newsroom should be stopped because, well, pause, because I'm using the journalist from the other session. So, yeah, don't worry about it. Cool. Okay, now on this one. So this is this slide is really good, right? I really like it. I really like the Brad Victor comment. I like the reference. The thing that's a missed opportunity is just the column on the right. So the table, on there's the animation, and there's the table where it's almost like you want to show the feedback loop, but you want to show the features, right? You want to show what actually we did, because it just says, routed by the conductor and fix, right? Something like that. And that's what'd be cool to do is just, even if you add more time, it doesn't matter, right? Like created before, I'm sure you have examples of created and then when you're done, and that delta, and if it is 5 minutes or 10 minutes, but it's important to show that loop like you have there, but it's important to show the features that we added. And some of them are major features, right? You know, major changes, major improvements, major slides that just got added, right? Based on the feedback that I provided. or even major refactoring, and that's very important. > Yeah, so this one, that I like the loop, I like what you're trying to do. You almost, to be fair, I think you probably almost, this looks very similar to a OODA loop, which is probably kind of what it is, right? Where you have orient, observe, decide, and act, right? So maybe it's a variation, but the way it is, see again, that doesn't make any sense, right? It's almost like something like think, explain, create, review, think, something like that, right? That kind of loop. The second, the part in the middle doesn't make sense, right? It's a bit confusing, that example of one ask. What do you call it? Following full. That's, in fact, that's a, so it's a weak example. I think the concept is good, but if you want to do that, you need a much better example. The next one is much better. The whole, the factory, explaining what the factory is actually much more interesting, right, in terms of that. Although I always feel that you can have a little infographic here, like showing the factory in action, right? And also the design can be a bit better at the top. The agents are a bit smaller. In fact, I almost feel like here you want to use that animation or that infographic that we have that shows when the agents fire up at what time of the day. Because that's a good example of the handover of the agent to agent and also the factory. ## How the conductor reads it (not his words) - **The newsroom**: the reply (`team/conductor/requests-out/newsroom__narrator-voice-part-one-reply.md`) is not sent; he works with that journalist in another session. - **"His afternoon asks"** (ruv-sgit's card): keep the loop, but show what each ask built (the feature, the slide added, the refactor), the major ones marked, and the time from the ask to the work landing. Historian 035 (the record), researcher 054 (the register), ruv-sgit 025 (the redraw). - **The loop drawing** (the designer's): "see, ask, see again" does not read; something like an OODA loop: think, explain, create, review. Designer 061. - **"One ask, followed in full"** is a weak example: a much better one, or none. Storyteller 059, writer 020. - **"What a factory is"** is the stronger section: add the factory in action, ideally the drawing of when each agent fired through the day (ruv-sgit's clock), showing the hand-overs; the cast row above it is too small. Ruv-sgit 025, designer 061. --- *[Site index for agents](../llms.txt) · [HTML version](https://the-ultimate-insider.book.sgit.ai/brief/11-the-afternoon-asks-the-loop-and-the-factory.html)*