The brief · 2026-10-31__rc1-paper-review · briefs/2026-10-31__rc1-paper-review/batch-05-pages-10-to-13.md

Batch 5: pages 10 to 13: Wardley maps, the publisher, the sources, and the book as JSON

The editor, in the conductor's session, 31 October 2026. Kept as he gave it.

Okay, so now page 10. Again, all of this stuff is logistics, right? You know, not that relevant. And the page 10. Open that up to see what that is. Let me see page 10. Okay. Okay, so actually this is page 11, sorry. So the thing about this, right, is that, yeah, it's, the thing about the worldly maps, right, and I have another comment below, but I think the way to do the worldly maps, and by the way, there's some amazing content here, and I'm going to have a comment in a bit about it. But the thing about worldly maps is I think we need to introduce it without explaining it. We should mention worldly maps. We should mention that, by the way, this is the concepts that you're going to see here. And if you ever, as you start reading about, you know, Genesis and custom build and town planners, maybe, again, put a little side note, maybe with a couple of examples, a good example of the kind of side notes that we can have on the side of the page, right? But I think we need to start showing and telling the story using smaller, simpler worldly maps. Maybe we even show a graph and then let's say we position it a bit, right? So it's kind of like, let's start introducing the concept of worldly maps and then we kind of introduce them more into how it works. And then we also start talking about the explorers, town planners and mapping about, right? Now, the other thing that I feel here is that I think we have a should section in the end. I think we mentioned this on this page 11 about a publisher, but I think we should be talking about we want a publisher, right? And again, we should explain. So this is a good example, right? But to explain the concept that the original presentation is an explorer, this book is a villager, and the publisher that we want to hire or we want to contract to is a town planner, that requires a lot of understanding of worldly maps. That's like advanced worldly maps kind of concept, right? If you're still getting the concept of worldly maps, that's not going to make any sense. So again, that should come a bit later. And again, that should come more with the diagram than anything else. Okay, now page 13. How to read a map. You know, this idea here is, for example, actually not just this part, this is where it came from section, right, that you have, right? This whole section makes sense, but it's a good example of something that is too detailed and too light at the same time. It's too detailed because the people reading this, like, what, how do I consume? It's a wall of text, where does it go? None of these makes any reference, right? Even the commits, right? But on the other hand, it's not enough because it doesn't link to where it goes, right? So this is why this kind of stuff should only be existing in this augmented reality kind of world, right? And ironically, this is how I start to think about this idea of having this online iPad PDF kind of mode application or view that has that augmented capability, right? So, And this is a good example. Like, of course, that we should be showing the provenance of every idea, every page, every paragraph, and we have to capture, and that's the graph that we have all this. But here, we shouldn't be having that. Actually, on this topic, unless you have it done already, but the content of the entire book should be in JSON, and you should have a projection into Markdown. Right now, look at what we did in the look at what we did in the books.sgraph.ai, because we started to do an experiment on this already there, and I think it was working quite well. So it's worth you getting the team to do research, because it means that you start to move the content natively into JSON. It means that immediately you have a separation between code and formatting. And we immediately start to have that different projections, right, about the content and the structure. And everything becomes a lot more hyperlinked, because we need to also get to the point where every idea, every concept, everything that is in the book is linked somewhere, right? So you have all this set of JSON files for every chapter, for every section, for everything, even every infographic is all in JSON. So you should not really have content in, that is original in Markdown. You should have a projection into Markdown. Hopefully that makes sense. And I think we've done a lot of this stuff in that graphs.sgit.ai already. Okay,