From: Jeremy D. Selengut (selengut_at_nih.gov)
Date: Thu Aug 23 2001 - 06:06:40 PDT
167:17 > >>>>>> >Future rules' codes must be made in two ways only: > >Old Fashioned Way: >Your rule must have a VALID rule and an INVALID rule as parents. Put >the rules' genetic codes in either order, then remove every other letter >to be left with your starting code for your rule. > >Cloning: >Pick one rule either VALID or INVALID for a parent, reproducing its >exact code. > >Then put in any genetic material from words spliced in accordance with >previous rules. You now have your code for your rule. "Our overworked >Judge must be informed" which rules are the parent(s) or it is >invalidated for not having proper documentation. > >>>>>>> > >Aron Wall Jusgement: VALID. Note that "informing the Judge" must be done _within_ future rules. The Judge cannot make decisions on the validity of a rule based on content (or lack thereof) not contained within the rule itself. The extent to which a rule is in compliance with all restrictions must be transparent (determinable, even if craftily hidden within a rule) to all players. Thus, private messages to the Judge cannot be required for the validity of a rule. To put this in the context of the R.O.'s: The Judge must determine whether a _rule_ is consistent with all previous valid rules and declare it INVALID if it is not (R.O. #6). Whether or not a _player_ has sent notification to the Judge before or after the fact in a separate message publicly or privately, the _rule_ did not include the required information and so would be judged INVALID. Style: This restriction seems a bit tough for the first week of the round, and not applying it to this rule as an example of how it can be done was a bit wimpy. On the other hand, the concept here is exemplary - Aron has at a stroke brought the round closer to the theme, given purpose to the genetic codes and created a great splicing mechanism that corrects the unintended weaknesses in 167:8. +2.0 -TWJ -- Rule Date: 2001-08-23 13:07:25 GMT
This archive was generated by hypermail 2.1.5 : Thu Nov 24 2011 - 10:48 PST