Monorepo dates back two decades and was a way of unifying development across multiple teams so that they could work more efficiently together. Several large companies advocated its use -- and when, in certain companies, it scaled beyond a single machine's capacity, they created all sorts of "interesting" tooling to support its growth because they valued the benefits a monorepo brings. Polylith is a useful way to structure a monorepo that builds multiple applications from a bunch of shared "subprojects". The core premise of a monorepo is that teams work together across multiple "subprojects". If you have teams that don't work well together, you can either fix the teams, or revert to multiple repos and deal with all the coordination problems that adds. Either way, it's out of scope for Polylith, in my opinion.