Archived
The image every module in the scripted toolchain is compiled on top of is registered as a module so the mesh can build, version and depend on it. It is not one: nothing about it belongs on a machine. Assigning it succeeded, the machine was sent a declaration containing nothing of it, and everything reported success — the operator had said run this here and the mesh had agreed to something it cannot do. A module whose resources are worked out per node is asked about separately, so it stays assignable, which is the point of it.