... action gates. Comment from Rabnoor Singh(@rabnoor_s): Reach is the right axis and the reason is that irreversibility over-fires and under-fires at the same time. It stops an agent writing a log line and waves through a migration you can only roll back with downtime. But there is a second thing hiding inside reach that most gates miss: it is cumulative, not per action. Every individual call can be correctly scoped and legitimate, and the damage still ... ... that got me. Some of the worst reach comes from actions that are trivially reversible AND technically correct. Writing a number into a notes file is fully undoable. It touches nobody. Any blast-radius check waves

... closest thing that's slipped into your ship-it pile? Comment from Chalermpon Ananwattanakit(@vollos): My version of that split fell apart on the ship-it side. A database view feeding a public page, the sort that gets waved through, turned out to expose every user's email. When I asked the AI about it, it called that 'partial user data'. So now I sort by what data the code can reach instead of which feature it sits in. Pure ... ... head right now which isn't great for consistency. Comment from King Joshua Marcos(@moddy): Honestly just trial and error early on. Let it fully own something low stakes, watched what broke, adjusted from there. The billing/auth vs