“If you give it access to workflows on GitHub, it will be able to apply still. It will find some way to do things that you didn't maybe intend it to do. So at the architectural level, it shouldn't be possible even to do things you don't want it to do.”

All of it. And we have a good open source guide, infrastructure agents guide on GitHub that goes through all the levels. But basically, there is around 13 or let's say 10 realistic levels that you need to think through when using or designing your system for agentic use. And all starts with architecture. How do you architect actually the whole way of the system, the agentic system? And in those levels, you decide, okay, what kind of agents you're going to use and how do you orchestrate them? Where are you going to source them? Because that also brings certain kinds of questions about data privacy, depending on where you source them. Then where do you get your tools, CLIs, skills? How do you actually enable agent to do those things that we want them to be able to do? How these agents run, right? Sandbox environments or running versus running on your desktop. Of course, by definition, if you run it in sandbox, it's going to be safer. There is less likely that it will find some SSH file on your desktop to gain keys to your systems that…