this module is a thriving, multi-use community of interacting concerns and responsibilities. yes, it would be more legible to central administrators like us if

this module is a thriving, multi-use community of interacting concerns and responsibilities. yes, it would be more legible to central administrators like us if we evicted all the requirements and implementation details, paved it over, then redeveloped it into a high modernist Corbusian hexagonal microservices architecture. but truly, who would want to live or work inside such a bleak module structure, where instead of simply nipping downstairs to share surplus resources with unrelated business logic in the parent stack frame, you would have to traverse through endless tiers of serialization, transit, deserialization & be subjected to endless authoritarian checkpoints for authorisation by central authorities?