The brief · 2026-10-31__rc1-paper-review · briefs/2026-10-31__rc1-paper-review/batch-10-page-45.md

Batch 10: page 45, the last of this series: the code that maintains the site, and a guided tour first

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

Okay, this next one is the last one of this particular series here, is on page 45. And again, like you mentioned admin build validate.py, right? This is another major piece of the puzzle that we have. We have all these JavaScript, sort of Python code that runs, that maintains stuff, that there's a huge amount of work here. And like even there, right? Like, you know, even look at this description, there must be a much better visual way to represent this. But we haven't introduced what these Python guys go. Like, where do they run? Do they run on a server? Do they run by Claude? Do I need to run them locally? Right? Do I need to explain, again, the power of these files and the power that, again, Claude now has, where we can work together to create all these sort of tests that make sure that you know, the expectation exists on what, you know, you're creating, which is something that we never really had before. Right? So in this case, explain what this Python code is. And, you know, we should be sandboxing this thing too, right? But that's a different topic, right? Yes, and then at the bottom of that page, we have dev's role, field, as one more thing, the later chapters, the table, header, reach. Again, this was all done before we even introduced the ABPs, right? So, and then look at how I did it in the presentation, right? I talked about stuff, and suddenly I started to say, hey, now let's talk about how to contain this. Let's talk about how to prevent execution and control the behavior. And then you have the ABPs, and then we can connect that to the, you know, Sharna's AI, right? And I actually feel that, I think I mentioned this before, right? I think we should probably start the book with a guided tour of the admin side and the non-functional requirements, right? To show the amazing stuff that was created, the animations, like, you know, okay, we're going to get either QR code or we actually replicate them a bit. And in a way, not just what it was, you know, what was there, but how it was created. And I think nobody's going to ask how it was created until they're impressed with what we created. So I think this is a good example of, let's see if we can show them something that they impressed or they like, or they go, hey, I want to do that. Then you go, how do you do it? And that's when we give a solution. So if somebody's not asking how you do it, there's no point of giving them the solution, right? And again, like, we've created this powerful, ridiculous environment from Claude and roof.skit, right? And it's already working quite well. And you're using it already, right? So it's a crazy success story, right? Of using RUV with skit, right? And I have another comment here on 45, which is, after the concept of gate, when you talk about before the skills, Claude MD, short loser, blah, blah, blah, find your role, ask the editor. So this is a really good line, but in a way, this is kind of where we probably want to start some of this stuff, with real world examples, right? And so also in our article, also explain how to use Markdown, you know, and actually we should be using Markoa, right? Which is the native to there. So we should be mapping that. And that's it.