Wire the model registry into the “task selector”, effectively enabling configure-on-demand for rule based task declarations. Rather than eagerly “realize” the whole task container and its contents, we now only realize the container itself. This means that we know of all the tasks that will exist without actually creating them. If a task (declared by rules) is not needed for a build (i.e. not selected, not depended on) it will not be created.
However, our rule based plugins at this time contain coarse rules that don't allow this feature to be leveraged. Benefits will only be seen right now for contrived domains.