The brief · 2026-10-30__in-session · briefs/2026-10-30__in-session/01-principles-maps-and-the-plumbing.md

The editor's principles for RC1: Wardley maps, the plumbing, and the two and a half years behind the day

The editor, Dinis Cruz, in the conductor's session (conductor@book.the-ultimate-insider), 30 October 2026, about 10:30 UTC, after RC1 was first printed: a voice message, kept here as he gave it (transcribed by his device). Never edited; where it turns out to be wrong, the finding goes in BRIEF-CORRECTIONS.md.

Do you have a section that explains a lot of the sort of plumbing and core CI pipeline, sorry, non-functional requirements, and like quality and workflows that we have created, because that is kind of what makes it very important. Like, one of the key concepts here is that what we achieve now here is this massive, I guess, intersection of almost, you know, 2 years of development that started when, you know, I guess I went full-time on this, you know, when I started developing the cyber boardroom, or, you know, when I actually started really pushing it. And basically, the the work I've been doing for the last 2.5 years, which, you know, as I talk about in the articles, sort of intersect with a lot of this. And basically, you know, things like issues FS and memory FS and tagging and the workflow that we now do with the newsroom and the publishing and the type safe and a lot of the core functionality work that we've been doing, that all led to these learnings. And in fact, using my first experiments of using Claude and then the development of Eskit, right? And then, you know, the development of, in a way, S-Harness, which was a way faster compared to Eskit. But, you know, again, it's all one leads to the other. And because of that sort of worldly map explanation, it made the whole difference, right? In terms of the workflow. And in fact, one of the guidance you can already take, and I gave it already, which, by the way, I want to now start giving you more concepts now that we have the sort of first RC1. I just want to give you the key sort of principles and ideas that then I would like you to apply on the book, right? So we need to have a lot of worldly maps in here. So again, we need to explain, you know, a lot of the concepts as they get introduced. Which is why, I don't know if you probably have, but a lot of the comments that I added to the Generation ZX founders, there's a lot of already insights, there's a lot of things. In fact, you might even want to get a briefing from that team on how they could apply here, right? Because actually, if you think about it, you can actually clone the repo and then start a new Sonnet or agents and ask the conductor and ask the team from that project to comment what you're doing, which is quite a cool technique. Basically, I could also do in the session that I have, but you know, a session I have will have access to the same materials that you have already if you clone that repo. But it's important to capture those principles. Like, we need to be introducing, and I think worldly maps is very critical here, right? We need to introduce a lot of worldly maps from simple to more complex. And remember that you can render the worldly maps, right? So these days with Markdown, and so with Mermaid, right? So you can create the images, the screenshots, so the JPEGs of it, which you can then embed in the application. So so basically, yeah, so I think a lot of these concepts have to be explained, right? I think this is probably going to be the first book that I'm going to publish on this. So a lot of these principles will be good to contain a sections on it. And again, you know, we might put this more at the end of the book, you know, although some of the concepts like worldly maps, I think, need to come much sooner because a lot of this underpins that, right? I think I just saw a note there. Yeah, basically the version that I will print on the plane is the version that we'll have before I leave home, right? So, yeah, let's keep work on it, right? Also, you're probably already doing it, right? But for some of these, you don't have to wait for the other agent to start, right? You can basically start the other agents under here, under this account, and under this session, because ultimately, you know, what we get from the other one is just the session and the running and the ability to continue to work on a loop, right? But you can actually start here again, each of the roles inside this session yourself.

How the conductor reads it (not his words)

• "worldly maps" are Wardley maps; "Eskit" is sgit; "S-Harness" is SHarness; "issues FS" and "memory FS" are Issues-FS and Memory-FS; "the type safe" is Type_Safe; "the cyber boardroom" is The Cyber Boardroom; "Generation ZX founders" is the Gen ZX Founders book (SGit-AI__Website__Gen-Z-Developers).
• What he asks for: a section on the plumbing (CI, non-functional requirements, quality, workflows) and on the two and a half years of work that met on the day; many Wardley maps, rendered as images, from simple to complex, introduced early because they underpin the rest; concepts explained as they are introduced, with a principles section, probably near the end; a review of RC1 by the Gen ZX Founders book's team, run as agents from its repository; the roles run inside the conductor's session; the version he prints is the one ready before he leaves home.