Sure, but that's not quite what I was getting at. Maybe I wasn't clear enough.

The sort of copy-paste condos you see all in one place are still a single development project by a single property developer. They're all signed off on as one job-lot, and then the materials are allocated to build all of them, a pool of workers are hired and reused between all the projects (where they might be working on condo #14 one day, and then condo #26 the next), etc. Maybe some more are added a few years later, and maybe those are across town—but this is still the same ongoing "project", by the same architect, the same construction firm, under the umbrella of the same sign-off from the same urban planners and engineers.

Whereas, what doesn't seem to exist, is a sort of approach to architecture that resembles software engineering. One where "a building blueprint" is like "a software library": a reusable thing, sold or shared between different companies, or maybe even open-sourced. A world where your first condo project, as a developer, might involve constructing a building to a blueprint that existed long before your company did, even a blueprint your rival firms are also using.

In such a world, you'd expect the components that go into such "common blueprints" to become standardized. You'd see a separation-of-concerns where these components get prefabricated not by the development company's contractors (as part of a "house in a box" or "condo in a box", the way you see today) but as part of an ecosystem of parts that enable these separate development-companies working off the same plans to work more quickly/efficiently. You'd have the Apples of the construction world buying full kitchen-assemblies or pre-plumbed-and-electrified-and-insulated-walls or whatever from the Samsungs of the construction world.