It's like bad software architecture. Imagine we already have a security module responsible for deciding what requests are properly authenticated and authorized.

It's like bad software architecture. Imagine we already have a security module responsible for deciding what requests are properly authenticated and authorized. And we have a service module responsible for some of the processioning of requests. Now someone comes along saying they think the security module isn't doing a good enough job - and their proposed solution isn't to fix the security module, it's to let the service module do request authorization too. And not even by asking for input from the security module about what should be authorized, or having a shared definition of authorization rules that they both rely on, but by letting the service module decide on its own what it thinks should be authorized. You'd tell whoever proposed that, our system already has that responsibility living in a single place, and spreading it out to multiple places is how you turn your code base into an unmaintainable mess, thankyouverymuch.