Don't get me wrong, I think it's good to have clear boundaries for your rules and to enforce them unfailingly, for exactly the reasons you mentioned. My origina

Don't get me wrong, I think it's good to have clear boundaries for your rules and to enforce them unfailingly, for exactly the reasons you mentioned. My original comment was more about how if you have those kind of boundaries and rules, it's probably better to err on the side of overcommunicating them and to optimize for not having to enforce them in the first place. You know, something as simple as, "hey, don't forget this meeting coming up, if you miss it you'll be removed from the program" as a reminder. It's good to have boundaries, but it's even better to help prevent people from crossing them in the first place. But of course I'm just an outside observer reading a one-sided account of things, so maybe there's more to it, or that's just how they prefer to run things which is fine too I suppose. It's the same reason we have "Are you sure?" dialogs for destructive or irreversible actions in software.