> I don't think the solution is to regulate architects more, but rather to create a system where contracts actively provide feedback, so that processes can be iterated upon.
I really recommend Christopher Alexander's work to you because of these views. He explores how past buildings have managed to be built and how the architect <-> contractor feedback loop can be effective.
It's not quite the same though. You are operating in uncharted waters and writing the rules with a feedback loop between theoretical and experimental. But the only bounds are what can practically be achieved given today's technological limits and understanding. Whatever both groups are working on, it stays between those 2 groups of experts.
In civil engineering you add a thick layer of regulation. Because what the architect theorizes about, and what the engineer ends up building will be directly populated or operated by the general population. An architect delivering something that isn't actionable as-is or an engineer implementing approximations that don't do the job will sit somewhere between worthless, fraudulent, and maybe even to criminal.
I don't think this back and forth is what happens between architects and contractors. Contractors are not paid to produce knowledge, and they have no incentive to better conform to regulations. So I expect the convergence between architects and contractors is very slow.
I don't think the solution is to regulate architects more, but rather to create a system where contractors actively provide feedback, so that processes can be iterated upon.