On Thu, 14 Jan 2010, ais523 wrote:
> On Wed, 2010-01-13 at 19:58 -0800, Kerim Aydin wrote:
> So to answer the original question: A rule banning doing X does not ban
> other methods to achieve the same effect. However, nearly all security
> rules do explicitly ban other methods to achieve the same effect, so it
> isn't a problem.

"Nearly all".  I think we're in agreement then, and you're actually
arguing my point -- the immediate problem is that voting is not part 
of the "nearly" for ratification.  The first two paragraphs of the 
power-3 R2034 explicitly claims precedence over all rules (including 
ratification) for whether votes can be changed or considered to be 
changed for the purposes of resolution.  The later paragraph of R2034
describing the self-ratification doesn't itself claim precedence.
Add to that the last paragraph of R208, which claims precedence over 
all methods of resolution as being tied to a *valid* tally of votes.
So a correct tally has precedence over a self-ratified incorrect
tally.  The ratification rules don't actually claim any precedence, 
so don't win these battles.

In a greater sense, here's my conceptual problem with ratification.
We've said (I think in a court case?) that if a ratification occurs on
a report describes a state that is IMPOSSIBLE in a continuous sense 
(e.g. setting an asset to a negative quantity) then the reality 
"reasserts" itself.  However, once a vote is cast and past the voting
period, it is equally IMPOSSIBLE factually to change it (change the
past) so why doesn't reality reassert itself in this case, too?

This brings it back to my original question.  What ratification is
ask us to act as if the IMPOSSIBLE were true.  So if the rules were
changed such that ratification of an IMPOSSIBLE state was the only way 
to adopt proposals, it would still mean rules changes were 
IMPOSSIBLE, but just that we accept that the impossible happened
through self-ratification.   So would R1698 act to keep such said
changes from happening?  This question may be wholly a semantic one,
but it's a semantic interpretation that affects the operation of R1698.

-G.

 

Reply via email to