I submit the following proposal, entitled "Simultaneous Rule Changes Fix", with
an adoption index of 3:
===
Amend Rule 105 ("Rule Changes") by replacing the following text:
---
A rule change is any effect that falls into the above classes. Rule changes
always occur sequentially, never simultaneously. If a specification would ever
be interpreted as causing multiple changes to happen at once, it is instead
interpreted as attempting to cause them to occur separately, in the order they
are listed in the specification.
---
With the following text:
---
A rule change is any effect that falls into the above classes. Rule changes
always occur sequentially, never simultaneously. If a specification would ever
be interpreted as causing multiple changes to happen at once, it is instead
interpreted as attempting to cause them to occur separately, in the order they
are listed in the specification. If no such order can be inferred, then the
specified rule changes are void and without effect.
---
===
Obviously inspired by CFJ 4147. This is, according to ais523, how the rules
work already, but it doesn't seem like any rule actually explicitly says so.
Rule 105 goes on to say that "any ambiguity in the specification of a rule
change", singular, causes that rule change to fail, but obviously individual
rule changes do not have orders. This would clear up any ambiguity.
- Galle
