On Tue, Feb 10, 2009 at 10:25 PM, Kerim Aydin <[email protected]> wrote: > A rule specifically allowing a proposal text to change is no more > difficult to accept than one changing chamber, AI, etc. But what's > important is what is needed to actually *adopt* a Proposal. That is > defined under Agoran Decision rules, not proposal rules.
No, it's not. The mechanism for a proposal taking effect is defined in Rule 106. > Specifically, in R107 and elsewhere, an Agoran Decision is a decision on > a "matter" to be decided on, which I argue could be defined as referring > to a particular and specific version of a text, not a different version > which later bears the same ID number. The specific matter must be in the > initiation notice for the decision[*]. The matter is R106 "determining whether to adopt a proposal". Not any specific version of a proposal, but 'a proposal'. The other language in R106 does not indicate that any specific text or version of a proposal takes effect, but rather the proposal itself: "If the option selected by Agora on this decision is ADOPTED, then the proposal is adopted... its power is set to the minimum of four and its adoption index, and then it takes effect."

