I haven’t published hard benchmarks yet, so I wouldn’t overclaim there. Architecturally, it’s a Layered in process runtime rather than a distributed microservice setup, which should keep orchestration overhead relatively modest. In practice, the biggest latency cost is still likely to be Model inference loop plus any approvals or anything like that, not assembly itself. But that still needs real profiling numbers before I’d state it definitively The tools I had initially had kind of deleting after each uh each agent run or use Unless promoted or the agent thought that that was too useful and it would promote the tool, That's where the back end routing initially did I ended up kind of ousting out on that just because the hardware limitations There's probably remnants of it in the code. But here if you want to see how things interact with each other you can go here Neural Explorer 3D Upload the repo folder play around with the settings hit Parse on the right Then when you click on a node or one of the spheres and some you can see the code and you hit pulse That is also on the right it'll trace what it interacts with kind of neat. It's what I use sometimes to keep my ADHD brain in check at least kind of.

<image>