No we can go forward - I think I made the executive decision (at least in my head) that all control loops will check prov_status=active. We will have to look at the specification to see how we can add a policy to it so that can be set by designer in CLAMP.

Is this still on hold?  Or should we go ahead and add the check for ALL control loops?

- Kind of, but I wasn't thinking in the same place. Too bad is wasn't implemented as an actual Rule vs in the java code. Let's wait another sprint for this, I am still scoping whether we can make it and is-closed-loop-disabled actual guard policies that can be specified during design time. The problem is hard coding is that now this is true for ALL control loops. Right now it is only the Scale Out use case that wants this.

So is all we want here is to add a check for prov-status=active, at the same place that the code checks is-closed-loop-disabled (i.e., in queryAai)?  Or is there more to it (e.g., only do the check in certain cases)?  Note: the check for is-closed-loop-disabled is in java code, not the rules template, not that it really matters.