THE LOGICAL RULESET Rules are listed as follows, where NNNN represents the Rule Number. ---------------------------------------- Rule NNNN (MI=Mutability Index of the Rule) Title of Rule Rule Text Annotation: as required by Rule 789. These include a list of Relevant Rules: [Note: annotations enclosed in brackets are my own and are entirely unofficial. They have no legal force in and of themselves.] History: Some Rules include a complete or partial history. An ellipsis (...) indicates that the history is incomplete. ---------------------------------------- There are currently 268 Rules: 18 with MI=3 4 with MI=2 246 with MI=1 Highest Rule Number assigned so far: 1621 ======================================= Table of Contents: The Game of Agora Definitions The Rules The Players Officers Making Proposals Voting on Proposals The End of the Voting Period Referenda and Elections Petitions The Clerk of the Courts Calling for Judgement Selecting a Judge Delivering Judgement Overturning Judgement Rule Violations Crimes and Infractions The Distributor and the Assistant The Registrar The Rulekeepor and Archivist Patent Titles Degrees and Theses Currencies The Scorekeepor and Points Marks and the Banker Extra Votes Powers Style Points and the Wizard Winning a Game, and the End of the Game Blots and the Immaculate Changing Speakers Subordinate Legal Codes Organizations The Notary Groups and Contests Contracts Honour ---------------------------------------- ======================================= The Game of Agora This Category includes Rules applying to all aspects of this Nomic. ---------------------------------------- Rule 1020/0 (Semimutable, MI=3) Name is Agora The Official Name of this Nomic shall be Agora. History: Created by Proposal 913, date unknown Transmuted from MI=1 to MI=Unanimity by Proposal 1020, Sep. 4 1994 Mutated from MI=Unanimity to MI=3 by Proposal 1484, Mar. 15 1995 ---------------------------------------- Rule 101/0 (Semimutable, MI=3) Obey the Rules All Players must always abide by all the Rules then in effect, in the form in which they are then in effect. The Rules in the Initial Set are in effect at the beginning of the first game. The Initial Set consists of Rules 101-116 (Immutable) and 201-219 (Mutable). [CFJ ???: "abide by all the Rules" means the Rules as a whole, not necessarily each individual Rule. CFJ 24: Players must obey the Rules even in out-of-game actions. CFJ 825: Players would have to obey the Rules even if 101 were repealed.] History: Initial Immutable Rule 101, Jun. 30 1993 Mutated from MI=Unanimity to MI=3 by Proposal 1480, Mar. 15 1995 ---------------------------------------- Rule 116/0 (Semimutable, MI=3) Permissibility of the Unprohibited Whatever is not prohibited or regulated by a Rule is permitted and unregulated, with the sole exception of changing the Rules, which is permitted only when a Rule or set of Rules explicitly or implicitly permits it. History: Initial Immutable Rule 116, Jun. 30 1993 Mutated from MI=Unanimity to MI=3 by Proposal 1483, Mar. 15 1995 ---------------------------------------- Rule 1011/2 (Semimutable, MI=2) Game Entities May Not Be Arbitrarily Changed No property of any entity shall be changed except in accordance with procedures specified by the Rules, when that entity possesses that property solely by the virtue of the Rules defining that property. [CFJ 700: Neither nicknames nor Players are "created by the Nomic Rules, and exist only within the context of Agora Nomic." CFJs 815 & 816: If an amendment is made which changes the properties of an Entity, the Entity changes to conform to the new Rule, rather than the destruction of the old Entities. If the old Entity has the same name as the new Entity, that implies continuity of that Entity if at all possible.] History: Created by Proposal 450, Sep. 10 1993 Amended by Proposal 1011, Sep. 5 1994 Amended by Rule 750, Sep. 5 1994 Mutated from MI=1 to MI=2 by Proposal 1593, Jun. 2 1995 Amended(1) by Proposal 2042, Dec. 11 1995 Amended(2) by Proposal 2546, Mar. 22 1996 ---------------------------------------- Rule 1619/0 (Mutable, MI=1) Names shall be Unique No two Nomic Entities (including Players) shall have the same name or nickname. History: Created by Proposal 2546, Mar. 22 1996 ---------------------------------------- Rule 1527/0 (Mutable, MI=1) Timing of Multiple Events in One Message Whenever a message contains more than one notification, report, or other communication in which the Rules place some legal significance, the communications in that message shall be taken to have been sent sequentially, separated by infinitesimal increments of time, in the order which they appear in the message. History: Created by Proposal 1750, Oct. 21 1995 ---------------------------------------- Rule 1600/1 (Mutable, MI=1) Standard Mathematics Except where the Rules explicitly state otherwise, any mathematical term in the Rules shall be construed to have the definition usually given to it in standard mathematics. In particular, "number" shall mean "real number." History: Created by Proposal 2495, Feb. 16 1996 Amended(1) by Proposal 2547, Mar. 27 1996 ---------------------------------------- Rule 754/2 (Mutable, MI=1) Spelling and Grammar Errors Differences in spelling, grammar, or dialect, or the substitution of a word or phrase by a synonym or abbreviation, are inconsequential in all forms of Nomic communication, as long as there is no ambiguity in meaning. In other words, the meaning or validity of such communication is not altered in any way by such discrepancies. This Rule defers to all other Rules which do not contain this sentence. [CFJ 712: This includes referring to a Player by a method other than eir name or nickname, as long as it is unambiguous. CFJ 744: In the context of Rule Changes, text in an existing Rule must be quoted exactly in order to be unambiguous.] History: Created by Proposal 435, Aug. 30 1993 Amended by Proposal 754, Dec. 1 1993 Amended by Rule 750, Dec. 1 1993 Amended(1) by Proposal 2042, Dec. 11 1995 Infected and Amended(2) by Rule 1454, Dec. 17 1995 ---------------------------------------- Rule 795/2 (Mutable, MI=1) Accurate Quoting Shall Not Be Penalized When a Player quotes a Rule, Proposal, Statement, Judgement, the words of another Player, or other references, that Player shall not be penalized in any way for the terminology or grammar used in those quotes. For the purpose of this Rule, a gain or loss of Kudos by any means shall not be construed as a punishment. This Rule takes precedence over any other Rule which specifies terminology or grammar. History: ... Amended(1) by Proposal 1507, Mar. 24 1995 Amended(2) by Proposal 1756, Oct. 21 1995 ---------------------------------------- Rule 1497/3 (Mutable, MI=1) Truth in Advertising A Player who presents as correct information which e believes to be incorrect as part of any message sent to the Public Forum or in response to a request for information which that Player is required to provide commits the Crime of Misrepresentation, a Class C Crime. A Player who presents as correct information which e believes to be inccorect as part of evidence in a Claim of Error, Call for Judgement, or Judgement commits the Crime of Perjury, a Class B Crime. A Player shall never be convicted of both Misrepresentation and of Perjury for the same act. [CFJ 827: If it is not clear that information is *not* presented as correct, it is. Attempting an illegal move can, if the Player reports the move and knows it to be illegal, be a violation of this Rule.] History: Created by Proposal 1667, Aug. 18 1995 Infected and Amended(1) by Rule 1454, Dec. 10 1995 Amended(2) by Proposal 2043, Dec. 11 1995 Amended(3) by Proposal 2548, Mar. 22 1996 ---------------------------------------- ======================================= Definitions This Category includes definitions of terms which do not readily fall into any other Category ---------------------------------------- Rule 1586/0 (Mutable, MI=1) Definition and Continuity of Entities A "Nomic Entity" is any entity which has no discernible existence without the Rules, only existing by virtue of the Rules defining it to exist. When the Rules defining a given Nomic Entity are repealed or amended such that they no longer define that entity, that entity ceases to exist, along with any properties it may have possessed. When the Rules defining a given Nomic Entity are amended such that they still define the Entity but in a different way or with different properties, that entity and its properties continue to exist to whatever extent is possible under the new definition. History: Created by Proposal 2481, Feb. 16 1996 ---------------------------------------- Rule 478/6 (Mutable, MI=1) The Public Forum The "Public Forum" is any medium legally designated as such by the Distributor. The Distributor is permitted to designate a medium as a Public Forum only if, to the best of the Distributor's knowledge and under normal circumstances, any message transmitted via that medium will be received by all Players. In addition, sending a message, by any medium or combination of media, to every Active Player, is equivalent to sending it to the Public Forum, provided that the message bears a clear indication that it is intended to be a message to the Public Forum, and it is verifiable that the message was in fact sent to every Active Player. It is the responsibility of each Active Player to ensure that e is able to receive messages sent to every medium which the Distributor has designated as a Public Forum. The temporary inability of a Player to receive a Public Forum does not deprive that medium of any legal significance as a Public Forum. [CFJ 707: Something sent to the PF is effective at the moment it is received by the listserver. CFJ 752: Something sent to a Player who is obligated to send it to all Players is sufficient for sending something to the PF. CFJ 813: A Player need not prove that e can receive the PF. CFJ 831: The Date: header of a message is not necessarily the time at which the message takes effect.] History: Created by Proposal 478, Sep. 20 1993 Amended(1) by Proposal 1477, Mar. 8 1995 Amended(2) by Proposal 1576, Apr. 28 1995 Amended(3) by Proposal 1610, Jul. 10 1995 Amended(4) by Proposal 1700, Sep. 1 1995 Amended(5) by Proposal 2052, Dec. 19 1995 Amended(6) by Proposal 2400, Jan. 20 1996 ---------------------------------------- Rule 1602/0 (Mutable, MI=1) Definition of Post and Synonyms Thereof Whenever the Rules calls upon some Player to "announce", "post", or "distribute" some communication or notification, this shall be accomplished by posting the communication or notification to the Public Forum. This Rule defers to any Rule which specifies some other means of announcing, posting, or distributing a communication or notification. History: Created by Proposal 2504, Mar. 3 1996 ---------------------------------------- Rule 459/0 (Mutable, MI=1) The Nomic Week The Nomic Week begins at midnight, GMT, each Monday. Any automatic change in the state of the Game which must occur weekly occurs at the beginning of the Nomic Week unless otherwise stated in the Rules. Any activity which must occur at least weekly must occur at least once each Nomic Week. History: Created by Proposal 459, Sep. 15 1993 ---------------------------------------- Rule 1274/1 (Mutable, MI=1) Definition of Indices Let there be a class of Entities known as "Indices" (singular: "Index"). An Index shall have a value, which is either a non-negative real number or the special value "Unanimity". An Index of Unanimity is greater than any other Index. When comparing other Indices, the Index which is numerically greater is the greater Index. History: Created by Proposal 1274, Oct. 24 1994 Amended(1) by Proposal 2053, Dec. 19 1995 ---------------------------------------- Rule 1023/6 (Mutable, MI=1) Definition of "As Soon As Possible" Whenever a Player is required to perform a certain action "as soon as possible", then: (i) if the action is one that a Player is required to perform in the course of carrying out Official duties, then the Player is required to perform the action within a week, and no earlier than any other action which the performance of the duties of that Office already requires em to perform as soon as possible; otherwise, (ii) e is required to perform that action within a week, and no earlier than any other action e is already required to perform as soon as possible which is not an action performed in the course of carrying out Official duties. Failure to observe these time requirements is a Class D Crime. However, activity of a purely discussionary nature is excluded from the ordering requirement, and may be conducted at any time. This Rule does not deprive actions which do not conform to its requirements of whatever effects they would otherwise have. Rather, this Rule defines the latest time at which actions to be performed "as soon as possible" may be performed without incurring a Penalty. It takes precedence over other Rules which define a later latest time for the performance of these actions. Other Rules may impose earlier latest times, and if so, this Rule defers to them. This Rule defers to Rules which describe the responsibilities of Players who are On Hold. History: Created by Proposal 805, date unknown Amended by Proposal 907, date unknown Amended by Rule 750, date unknown Amended by Proposal 1023, Sep. 5 1994 Amended by Rule 750, Sep. 5 1994 Amended(1) by Proposal 1413, Feb. 1 1995 Amended(2) by Proposal 1434, Feb. 14 1995 Amended(3) by Proposal 1682, Aug. 22 1995 Amended(4) by Proposal 1727, Oct. 6 1995 Amended(5) by Proposal 2042, Dec. 11 1995 Amended(6) by Proposal 2489, Feb. 16 1996 ---------------------------------------- Rule 1079/1 (Mutable, MI=1) Definition of "Random" When a rule requires a random choice, that choice shall be made among all the possible choices with equal probability. Because of the impossibility of finding a truly random test, "equal", for the purposes of the above statement, shall mean "reasonably close to equal". It is up to common sense to determine what is reasonably close to equal; however, the burden of proof of a method's randomness lies with the Player who used the method. The probability of a Platonic solid or coin, which is not specially weighted, falling on any given face is, for the purposes of this Rule, close enough to equal to satisfy the above requirement. [CFJ 832: The dice-roll server at dice@danpost4.uni-c.dk meets these requirements.] History: Created by Proposal 1079, ca. Oct. 11 1994 Amended(1) by Proposal 1648, Aug. 6 1995 ---------------------------------------- Rule 1538/2 (Mutable, MI=1) Definition of Violation If a Player performs an action which is prohibited by any Rule, or any other body of text which is defined to have the same force as a Rule, that action shall be known as a Rules Violation. Before a body of text is permitted to have the same force as a Rule with regards to a particular Player, said body of text shall have previously been made available to that Player. History: Created by Proposal 1760, Oct. 21 1995 Amended(1) by Proposal 2288, Dec. 29 1995 Amended(2) by Proposal 2453, Feb. 6 1996 ---------------------------------------- ======================================= The Rules This Category includes Rules about the Rules. (See also "Making Proposals" which includes some Rules concerning Rule Changes, even in the absence of Proposals; See also "The Rulekeepor and Archivist" which includes Rules regulating the Logical Ruleset and Rule Titles) ---------------------------------------- Rule 1021/3 (Mutable, MI=1) Mutability Indices Let there be, associated with each Rule, an Index called that Rule's Mutability Index. The Mutability Index of a Rule is a part of that Rule, and cannot be changed except by the application of a Rule Change of a type that the Rules state can change a Rule's Mutability Index. The Mutability Index of a Rule can never be changed such that it is less than 1 or greater than 4; any Rule Change which would do so does not have legal effect. A Rule whose Mutability Index is 1 is known as a "Mutable" Rule. A Rule whose Mutability Index is Unanimity is known as an "Immutable" Rule. All other Rules are known as "Semimutable" Rules. [CFJ 769: The "MI of a Proposal" is meaningless.] History: Created by Proposal 1021, Sep. 4 1994 Amended(1) by Proposal 1280, Oct. 24 1994 Amended(2) by Proposal 1526, Mar. 24 1995 Amended(3) by Proposal 2551, Mar. 22 1996 ---------------------------------------- Rule 114/0 (Semimutable, MI=3) Rules Can Always Be Changed There must always be at least one Rule with a Mutability Index of 1. Any Rule Change which would result in this condition becoming false shall not have any legal force. The Adoption of Rule Changes shall never become completely impermissible. History: Initial Immutable Rule 114, Jun. 30 1993 Mutated from MI=Unanimity to MI=3 by Proposal 1077, date unknown Amended by Proposal 1277, Oct. 24 1994 Renumbered from 1077 to 114 by Rule 1295, Nov. 1 1994 ---------------------------------------- Rule 1482/0 (Semimutable, MI=3) Precedence Between Rules with Unequal MI's In a conflict between Rules with different Mutability Indices, the Rule with the higher Mutability Index takes precedence over the Rule with the lower Mutability Index. History: Created by Proposal 1603, Jun. 19 1995 Infected, but not Amended by Rule 1454, Dec. 2 1995 ---------------------------------------- Rule 1030/3 (Mutable, MI=1) Precedence Between Rules with Equal MI's If two or more Rules with the same Mutability Indices conflict with one another, then the Rule with the lower Number takes precedence. If at least one of the Rules in conflict explicitly says of itself that it defers to another Rule (or type of Rule) or takes precedence over another Rule (or type of Rule), then such provisions shall supercede the numerical method for determining precedence. If all of the Rules in conflict explicitly say that their precedence relations are determined by some other Rule for determining precedence relations, then the determinations of the precedence determining Rule shall supercede the numerical method for determining precedence. If two or more Rules claim to take precedence over one another or defer to one another, then the numerical method again governs. History: Initial Mutable Rule 202, Jun. 30 1993 Amended by Proposal 1030, Sep. 15 1994 Amended by Rule 750, Sep. 15 1994 Amended(1) by Proposal 1527, Mar. 24 1995 Amended(2) by Proposal 1603, Jun. 19 1995 Amended(3) by Proposal 2520, Mar. 10 1996 ---------------------------------------- Rule 1513/0 (Mutable, MI=1) Authority of Non-Rule Entities It is legal for the Rules to grant the power to require Players to perform (or not perform) actions to Nomic Entities created in accordance with the Rules. Such Entities shall have whatever power is granted to them by the Rules. In the event that the requirements of such an Entity conflicts with the Rules, the Rules shall always take precedence. If two or more such Entities conflict with one another, then the relative precedence of the respective Rules which grant coercive Power to the Entities in conflict shall determine which requirements take precedence. If two or more Entities which are authorized by the same Rule conflict, then the Entity which was created first under the authority of that Rule takes precedence over the others. History: Created by Proposal 1704, Sep. 1 1995 ---------------------------------------- Rule 1454/2 (Mutable, MI=1) The Virus There is a Nomic Entity called the Virus which has the effect of altering the texts of Rules, in the manner and under the conditions set out below. This process is known as "infection". The effect of the Virus on a Rule, when it has an effect, is that of a non-Proposed Amendment to that Rule. Thus, the Virus can only be effective inasmuch as it satisfies the Rules for the effectiveness of non-Proposed Rule Changes. The selection of the Rule to be infected by the Virus occurs as follows: as soon as possible after the beginning of each Nomic Week, the Rulekeepor shall select a random integer in the range [M,N], where M and N are, respectively, the numbers of the lowest and highest numbered Rules at the beginning of that week. Call a number selected in this way a Virus Number. If the Virus Number selected is the number of a Rule, then that Rule is infected as described below, and no further Virus Numbers are selected in that week. If the Virus Number is not the number of a Rule, then a new Virus Number is selected as above, unless five such Virus Numbers (none of which is the number of a Rule) have already been selected in that week. In that case, the Virus is ineffective and no Rule is infected in that week. The Rulekeepor shall publish the results of the selection process in the Public Forum within 24 hours of the completion of that process. If a Rule has been infected, e shall announce the number of that Rule. If no Rule has been infected, then e shall announce that no Rule has been infected. An infected Rule is amended in the following way, given that other Rules permit it: if the Rule does not already contain the sentence "This Rule defers to all other Rules which do not contain this sentence.", then that sentence is appended to the Rule. If the Rule already contains the sentence, then the sentence is deleted from the Rule. There is one exception to the above: if this Rule is the infected Rule, then this Rule automatically Repeals itself. History: Created by Proposal 1573, Apr. 28 1995 Amended(1) by Proposal 1712, Sep. 12 1995 Amended(2) by Proposal 1781, Nov. 13 1995 ---------------------------------------- ======================================= The Players This Category includes Rules defining and classifying Players. ---------------------------------------- Rule 869/3 (Mutable, MI=1) Registered Players A Player is any person who is registered as a Player. A person is Registered to play when e sends a message to the Public Forum requesting Registration, unless another Rule forbids that person from Registering. No person may be registered as a Player more than once concurrently. If a Player has to be identified for whatever purpose, then the use of that Player's Agora nickname is preferred, but not obligatory: *any* unambiguous way of identification is allowed. [CFJ 805: "Person" here means a natural person, not a legal person (such as a corporation) or something named "person."] History: Created by Proposal 498, Sep. 30 1993 Amended by Proposal 869, date unknown Amended by Rule 750, date unknown Amended(1) by Proposal 1313, Nov. 12 1994 Amended(2) by Proposal 1437, Feb. 21 1995 Amended(3) by Proposal 2040, Dec. 11 1995 ---------------------------------------- Rule 1432/0 (Mutable, MI=1) Player Uniqueness If a Person becomes a Player, then ceases to be a Player, then becomes a Player once again, the Person becomes the same Player as e was previously. History: Created by Proposal 1438, Feb. 21 1995 ---------------------------------------- Rule 113/1 (Semimutable, MI=3) Players May Always Forfeit A Player may always deregister from the Game rather than continue to play or incur a Game penalty. No penalty worse than deregistration, in the judgment of the Player to incur it, may be imposed. CFJ 826, Nov. 15 1995: Rule 113 should be interpreted such that, even if a Player considers a penalty to be worse than deregistration, e is still subject to it unless e actually deregisters or is deregistered. Relevant Rules: 113 CFJ 853, Feb. 2 1996: Rule 113 should be interpreted such that it does not allow a Player to deregister retroactively. Relevant Rules: 113 CFJ 856, Feb. 20 1996: Rule 113/1 should be interpreted to mean simply that a Player may always deregister from the Game rather than continue to play. The other language in the Rule is merely a gloss on that basic content, illustrating some of its implications;it does not change the essential meaning of the Rule. Relevant Rules: 113 [CFJ 854: The mere belief that a penalty is worse than deregistration is not sufficient to cause deregistration.] History: Initial Immutable Rule 113, Jun. 30 1993 Mutated from MI=Unanimity to MI=3 by Proposal 1290, Oct. 27 1994 Amended(1) by Proposal 1304, Nov. 4 1994 ---------------------------------------- Rule 103/0 (Semimutable, MI=3) The Speaker and Voters At any time, each Player shall be either a Voter or the Speaker; no Player may simultaneously be a Voter and a Speaker. At any time, there shall be exactly one Speaker. The term "Player" in the Rules shall specifically include both the Voters and the Speaker. History: Initial Immutable Rule 103, Jun. 30 1993 Mutated from MI=Unanimity to MI=3 by Proposal 1481, Mar. 15 1995 ---------------------------------------- Rule 494/0 (Mutable, MI=1) Speaker Makes Random Determinations The Speaker shall make all random determinations required by the Rules except when the Rules specify another party to make the determination. [CFJ 834: If something is described as a Player's choice, and that Player chooses to make it random, it is that Player's responsibility to make the random determination.] History: Initial Mutable Rule 218, Jun. 30 1993 Amended by Proposal 411, Aug. 26 1993 Amended by Proposal 494, Sep. 29 1993 ---------------------------------------- Rule 104/0 (Semimutable, MI=3) First Speaker The Speaker for the first game shall be Michael Norrish. History: Initial Immutable Rule 104, Jun. 30 1993 Mutated from MI=Unanimity to MI=3 by Proposal 1482, Mar. 15 1995 ---------------------------------------- Rule 1016/8 (Semimutable, MI=2) Putting Oneself on Hold At any time, each Player shall either be On Hold or Off Hold. This status shall not be changed except as specified in the Rules. When a Player registers (or reregisters), e is Off Hold. An Off Hold Player becomes On Hold when e posts a message to the Public Forum stating that e wishes to be On Hold. An On Hold Player becomes Off Hold when e posts a message to the Public Forum stating that e wishes to be Off Hold, provided that e has been On Hold for at least 96 hours. [CFJ 718: Because of Rule 1011, a Player may not be placed On Hold except as specified in the Rules.] History: Created by Proposal 366, Aug. 10 1993 Amended by Proposal 464, Sep. 20 1993 Amended by Proposal 870, date unknown Amended by Rule 750, date unknown Amended by Proposal 1016, Sep. 4 1994 Amended by Rule 750, Sep. 4 1994 Amended(1) by Proposal 1337, Nov. 22 1994 Amended(2) by Proposal 1374, Jan. 17 1995 Mutated from MI=1 to MI=2 by Proposal 1407, Jan. 29 1995 Amended(3) by Proposal 1618, Jul. 10 1995 Amended(4) by Proposal 1700, Sep. 1 1995 Amended(5) by Proposal 1735, Oct. 15 1995 Amended(6) by Proposal 2042, Dec. 11 1995 Amended(7) by Proposal 2464, Feb. 16 1996 Amended(8) by Proposal 2479, Feb. 16 1996 ---------------------------------------- Rule 1584/0 (Semimutable, MI=2) Absolvement of Duty for On Hold Players An On Hold Player is not permitted to Vote on Proposals, make Proposals, or hold Office, and cannot be required by the Rules to perform any duty or action, unless that Rule specifically states that it can require On Hold Players to perform actions. This Rule takes precedence over every other Rule. History: Created by Proposal 2479, Feb. 16 1996 ---------------------------------------- Rule 1043/1 (Mutable, MI=1) Deregistration A Voter may deregister from Agora by sending a message to the Public Forum announcing eir deregistration. A Voter who deregisters in this fashion ceases to be a Player effective at the time date-stamped on that message, and e may not reregister as a Player until a new Game has begun. Other Rules may define other conditions under which Voters may be deregistered. [CFJ 810: If a Player deregisters as well as doing other things in the same message, Rule 1527 applies.] History: Created by Proposal 474, Sep. 28 1993 Amended by Proposal 1043, Sep. 21 1994 Amended by Rule 750, Sep. 21 1994 Amended(1) by Proposal 1305, Nov. 4 1994 ---------------------------------------- Rule 1042/4 (Mutable, MI=1) Deregistration Due to Inactivity A Voter shall be deregistered when any Player correctly reports to the Public Forum that one of the two conditions exists: a. The Voter in question is not On Hold and has not sent a message to the Public Forum or to any Player of a nature which must be recorded in a Report which then becomes publically available during the fourteen day period immediately preceding the posting of a message which announces that fact, or b. The Voter in question has been On Hold for the entire two month period immediately preceding the posting of a message which announces that fact. Upon the posting of any such message, the Registrar, or, in eir absence, the Speaker, shall, as soon as possible, determine if the claim is correct or not, and announce eir determinations to the Public Forum. If the Registrar fails to make a report within seven days, the Speaker shall make the required verification and announcement instead. This Rule takes precedence over any Rule which might prevent a Player from being deregistered against eir own will. History: Created by Proposal 460, Sep. 15 1994 Amended by Proposal 1004, ca. Aug. 25 1994 Amended by Rule 750, ca. Aug. 25 1994 Amended by Proposal 1012, Sep. 4 1994 Amended by Rule 750, Sep. 4 1994 Amended by Proposal 1042, Sep. 21 1994 Amended by Rule 750, Sep. 21 1994 Amended(1) by Proposal 1338, Nov. 24 1994 Amended(2) by Proposal 1466, Mar. 1 1995 Amended(3) by Proposal 1597, Jun. 2 1995 Amended(4) by Proposal 2506, Mar. 3 1996 ---------------------------------------- ======================================= Officers This Category includes Rules applying to Officers in general. ---------------------------------------- Rule 1006/5 (Mutable, MI=1) Defaults for Officers An Office is a position of authority or responsibility established by the Rules and held by a Player, who is called an Officer. At any time, for each Office there shall be exactly one Officer who holds it. A position of responsibility or authority is only an Office if the Rules specifically designate it as such. An Office only exists as long as there is a Rule in force which specifies that it exists. If the Rule or Rules which mandated the existence of an Office are changed such that they no longer do so, that Office ceases to exist. A given Office has whatever duties, responsibilities, and privileges that the Rules assign to it. History: Created by Proposal 386, Aug. 16 1993 Amended by Proposal 733, Nov. 24 1993 Amended by Proposal 881, date unknown Amended by Rule 750, date unknown Amended by Proposal 1006, ca. Aug. 25 1994 Amended by Rule 750, ca. Aug. 25 1994 Amended(1) by Proposal 1336, Nov. 22 1994 Amended(2) by Proposal 1582, May 15 1995 Amended(3) by Proposal 1699, Sep. 1 1995 Amended(4) by Proposal 1763, Oct. 31 1995 Amended(5) by Proposal 2442, Feb. 6 1996 ---------------------------------------- Rule 1064/4 (Mutable, MI=1) Freedom of Information Act If a Player is mandated by the Rules to maintain a set of records, these records must be available for public perusal, unless such records are designated by the Rules as private. A Player who maintains such records must provide a copy of these Records to any other Player upon request within one week. If e fails to so provide a copy of the requested records within one week, e commits a Class D Crime, unless the Records are unavailable for reasons beyond eir control and e reports this fact, with explanation, within one week. For the purpose of this Rule, all records pertaining to Votes currently in progress, excluding the text of the Proposals under consideration, are designated as private until the end of the Voting Period. History: Created by Proposal 488, Sep. 29 1993 Amended by Proposal 1064, ca. Oct. 11 1994 Amended by Rule 750, ca. Oct. 11 1994 Amended(1) by Proposal 1344, Nov. 29 1994 Amended(2) by Proposal 1672, Aug. 22 1995 Amended(3) by Proposal 1682, Aug. 22 1995 Amended(4) by Proposal 2042, Dec. 11 1995 ---------------------------------------- Rule 1431/5 (Mutable, MI=1) Claims of Error Any Player (hereafter the Claimant) who believes that any message posted to the Public Forum makes a claim about the Game State which is in error is permitted to, at eir discretion, post to the Public Forum alleging that that message contains an error. Such an allegation is a Claim of Error, and to be legal must also specify the nature of the alleged error. As soon as possible after a legal Claim of Error is posted, the Player who posted the message which contains the alleged error (hereafter, the Respondant) shall investigate the allegation of error and report to the Public Forum the results of this investigation. If the investigation determines that the original claim was in error, the Respondant shall retract that claim, replacing it with the corrected version. A Player who is not on Hold who fails to complete such an investigation within seven days when required by this Rule commits a Class C Crime. The determinations of such an investigation may be challenged by a Call for Judgement alleging that the original (or revised) claim is in error. A Player who is determined by CFJ to have posted an erroneous claim to the Public Forum commits an Infraction, the penalty for which is 1 Blot, to be reported by the Judge of the CFJ. This penalty only applies if a legal Claim of Error was made upon the erroneous claim, and that Claim of Error was either not investigated by the Respondant, or was investigated and found to be without merit, and finally if the erroneous claim was not retracted prior to the making of the CFJ. A Claim of Error is not legal and has no effect if: a) another Claim of Error has previously been made alleging the same error; b) the message containing the alleged error was posted more than 21 days prior to the making of the Claim of Error; c) the claim alleged to be in error has already been withdrawn or retracted; or d) the Player posting the message alleged to contain the error is the same as the Player making the Claim of Error. History: Created by Proposal 1431, Feb. 7 1995 Amended(1) by Proposal 1491, Mar. 15 1995 Amended(2) by Proposal 1643, Aug. 1 1995 Amended(3) by Proposal 1754, Oct. 21 1995 Amended(4) by Proposal 2424, Jan. 30 1996 Amended(5) by Proposal 2492, Feb. 16 1996 ---------------------------------------- Rule 1550/0 (Mutable, MI=1) Vote of Confidence Directive There is a Directive known as a Vote of Confidence (VOC). A Proposal containing a VOC Directive has an Adoption Index (AI) of one, or greater if another Rule requires a higher AI for the Proposal. A VOC Directive must unambiguously specify a valid Official Document of Agora Nomic, as specified in other Rules. If a VOC Directive specifies a Document that is not valid, or a Document that is no longer valid at the time of the Adoption of the Proposal containing the Directive, the Directive shall have no effect, even if its Proposal is Adopted. When the Rules refer to the "Adoption" of a VOC Directive, they mean that the VOC Directive was contained in a Proposal that was Adopted, and that the VOC Directive was allowed to have effect by this and other Rules. History: Created by Proposal 2425, Jan. 30 1996 ---------------------------------------- Rule 1551/0 (Mutable, MI=1) Adoption of a VOC Directive Adoption of a Vote of Confidence (VOC) Directive conforms the Game State to what it would be if the valid Official Document specified within the VOC Directive was completely true and accurate at the time of the Document's publication in the Public Forum. i.e. the State of the Game upon Adoption becomes that specified within the Document, plus all subsequent legal changes between the time of its publication and the Adoption of the VOC Directive. All Game State changes due to a VOC Directive occur upon passage of the Directive. A VOC Directive does not have retroactive effects. A Document specified within an Adopted VOC Directive is true and accurate. The Game State it references may not be retroactively modified prior to the time it was published in the Public Forum, even to reflect a prior mistake, retracted or illegal move, or an Injunction. This Rule takes precedence over any Rule that would allow such retroactive alterations or corrections to the Game State. In no way does a VOC Directive invalidate, reverse, alter or cancel any prior moves or transfers, even unrecorded or overlooked ones. Nor does a VOC Directive change the legality or illegality of any prior move. A VOC Directive only adjusts the actual Game State to conform to that perceived by the Players and Officers in Official Documentation. After a Document is subject to the adoption of a VOC Directive, the Player in charge of maintaining that Document shall annotate all subsequent publications of that Document with the date of the last such publication that was subject to the adoption of a VOC Directive. i.e. the date the subject Document was published in the Public Forum, not the date the VOC Directive was Adopted. History: Created by Proposal 2425, Jan. 30 1996 ---------------------------------------- Rule 1552/0 (Mutable, MI=1) Documents Subject to VOC Directives In order for an Official Document to be valid for the purpose of a Vote of Confidence (VOC) Directive, it must satisfy all the following criteria at the time the VOC Directive is Proposed: i) The Rules require some specific Player to produce and/or maintain the document. ii) The Rules required it to be published in the Public Forum. (A requirement that it be sent to all Players fulfills this criteria.) iii) It is not currently subject to a Claim of Error. (COE) iv) It is not currently subject to a pending Call for Judgement (CFJ), or a pending Appeal of a CFJ. v) The information within the Document has not been superseded by a subsequent Document. vi) The Document is not the Ruleset. The Ruleset is specifically excluded from all VOC Directives. Further, a Document can become invalid during the Voting Period of a VOC Directive if any of the following occurs: i) The Document is superseded by a subsequent Document which contradicts the information in the prior Document. This does not apply if there is a COE alleging the contradiction is an error, and the error is admitted before the end of the VOC Directive's Voting Period. ii) A COE is made on the Document, and the COE has not been denied before the end of the VOC Directive's Voting Period. iii) The Document becomes subject to a pending CFJ or a pending appeal of a CFJ. If another Document is issued during the Voting Period of a VOC Directive that does not contradict the prior Document it does not alter the validity of the prior Document. History: Created by Proposal 2425, Jan. 30 1996 ---------------------------------------- Rule 1555/0 (Mutable, MI=1) Resignation of and Removal from Offices When an Officer resigns from or is retired from an Office, e ceases to hold it in the normal fashion, but continues to hold the Office temporarily. When an Officer is removed from Office, the Speaker shall become the temporary holder of that Office, unless another Rule specifies a different Player who is to become the temporary holder of that Office. History: Created by Proposal 2442, Feb. 6 1996 ---------------------------------------- Rule 1556/0 (Mutable, MI=1) Terms of Service for Offices Unless otherwise specified, the Term of Service for an Office shall expire on the first day of the third month following the month in which the Officer in question was elected to that Office. At the exhaustion of an Office's Term of Service, the Officer holding that Office shall be retired from that Office. This Rule defers to Rules which specify a different Term of Service for specific Offices. History: Created by Proposal 2442, Feb. 6 196 ---------------------------------------- Rule 880/3 (Mutable, MI=1) Resignation of Offices An Officer is permitted to, at any time, remove eirself from any Office e holds, provided e specifies another Player to succeed em, who then becomes the temporary holder of that Office. For this appointment to be valid, this Player must either explicitly and publically consent to becoming the new holder of that Office within seven days of such appointment, or be the Speaker. The Speaker can be appointed to hold an Office temporarily without consenting, and may not refuse such an appointment. A change in the identity of the Speaker does not automatically cause the transfer of any Offices being held by the former Speaker to the new Speaker. History: Created by Proposal 405, Sep. 3 1993 Amended by Proposal 880, date unknown Amended by Rule 750, date unknown Amended(1) by Proposal 1582, May 15 1995 Amended(2) by Proposal 1631, Jul. 17 1995 Amended(3) by Proposal 2442, Feb. 6 1996 ---------------------------------------- Rule 1557/0 (Mutable, MI=1) On Hold or Deregistered Officers If an Officer goes On Hold, deregisters, or is deregistered, e shall immediately be removed from every Office e holds. History: Created by Proposal 2442, Feb. 6 1996 ---------------------------------------- Rule 790/5 (Mutable, MI=1) Filling Vacant Offices An Office is "held in the normal fashion" if and only if the Officer holding that Office was elected to that Office and has neither resigned from it nor been retired or removed from it. An Office which is not held in the normal fashion is said to be held temporarily. As soon as possible after it occurs that there is an Office which is being held temporarily, and for which no Election is already being conducted, the Registrar shall initiate an Election to fill that Office, as described elsewhere. However, if the Office in question is that of the Registrar, the Speaker shall instead initiate the Election. The winner of that Election shall then hold that Office until e resigns or is retired or removed from that Office. History: ... Amended(1) by Proposal 2042, Dec. 11 1995 Amended(2) by Proposal 2442, Feb. 6 1996 Null-Amended(3) by Proposal 2454, Feb. 6 1996 Infected and Amended(4) by Rule 1454, Feb. 28 1996 Amended(5) by Proposal 2564, Apr. 6 1996 ---------------------------------------- Rule 1486/1 (Mutable, MI=1) Procedure to Impeach An Officer This Rule defines the "Procedure To Impeach An Officer". This Rule applies only to certain Offices, as defined by other Rules. An Officer is Impeached when a Referendum calling for the Impeachment of the Officer passes. Any Active Player is permitted to call such a Referendum at any time, by requesting such to the Public Forum. The Referendum must list both the Office and the Player holding this Office by name. If upon passage of the Referendum the named Player is holding the named Office, then that Player is immediately removed from that Office. For this Referendum the default procedure for referenda is modified as follows: Vote Collector is the Player who called for the Impeachment Referendum. Voting Entities do not include the Officer under consideration for Impeachment. Adoption Ratio is 2. History: Created by Proposal 1638, Jul. 25 1995 Amended(1) by Proposal 2442, Feb. 6 1996 ---------------------------------------- Rule 1487/0 (Mutable, MI=1) Impeachment of Assessor and Promotor It is permissible for the "Procedure To Impeach An Officer", as defined in another Rule, to be used for the Offices of Promotor and Assessor. History: Created by Proposal 1639, Jul. 25 1995 ---------------------------------------- Rule 1585/0 (Mutable, MI=1) Official Duties upon Officer Change Whenever the holder of an Office changes, any duties which the Rules had imposed upon the prior holder of that Office as a consequence of holding that Office which have not been fulfilled must instead be fulfilled by the new holder of that Office, as soon as possible and in the same order in which the prior holder of that Office had been required to fulfill them. The former holder of the Office is absolved of performing all such duties. History: Created by Proposal 2480, Feb. 16 1996 ---------------------------------------- Rule 1553/0 (Mutable, MI=1) Officer Transition Whenever a Player ceases to hold an Office, that Player shall make a reasonable effort to ensure that all materials necessary for the conduct of that Office, including any records the holder of that Office is required to maintain, are made available to the next Player to hold that Office. A Player who fails to do so violates this Rule, and commits a Class C Crime. History: Created by Proposal 2429, Jan. 30 1996 ---------------------------------------- Rule 1007/6 (Mutable, MI=1) Default Salary of Officers At the beginning of each Nomic Week, each Officer shall receive the designated salaries for the Office(s) e holds, provided that e has held them for the entire five days preceding without interruption. If the Rules pertaining to an Office require that Officer to publish a document at least once per Nomic Week, that Officer's Salary for a given Week shall be forfeited if that document has not been distributed in the previous Week. The Registrar shall detect and report all transfers resulting from the payment of fixed weekly Salaries. Unless otherwise specified, the salary for an Office is 3 Points. History: ... Amended by Proposal 1007, ca. Aug. 25 1994 Amended by Rule 750, ca. Aug. 25 1994 Amended(1) by Proposal 1582, May 15 1995 Infected and Amended(2) by Rule 1454, Aug. 28 1995 Amended(3) by Proposal 1705, Sep. 4 1995 Amended(4) by Proposal 1754, Oct. 21 1995 Amended(5) by Proposal 2442, Feb. 6 1996 Amended(6) by Proposal 2560, Apr. 6 1996 ---------------------------------------- ======================================= Making Proposals This rather large Category includes Rules regulating the submission and distribution of Proposals. ---------------------------------------- Rule 1483/1 (Mutable, MI=1) Definition of Proposals A Proposal is created whenever a Proposing Entity delivers some collection of text to the Promotor with the clear indication that that text is intended to become a Proposal. The collection of text thus delivered is a new Proposal, and the Proposing Entity which delivered it its Proposer. A collection of text is said to be Proposed when it becomes a Proposal. The delivery of the text of an existing Proposal which was Proposed less than three weeks previously does not cause that text to become another Proposal, unless there is a clear indication that that text is intended to become a duplicate of a prior Proposal. In this case, the Proposing Entity must specifically acknowledge that the intended new Proposal is a duplicate of an existing Proposal. Further, the Promotor's distribution of previously undistributed Proposals never causes the Proposing of new Proposals. [CFJ 762: Anything contained in a Proposal is part of that Proposal, unless the Rules or Game Custom specifically says otherwise.] History: Created by Proposal 1619, Jul. 17 1995 Amended(1) by Proposal 2522, Mar. 10 1996 ---------------------------------------- Rule 105/0 (Semimutable, MI=3) What Is a Rule Change? A Rule Change is any of the following: 1) the enactment of a new Rule (a "Creation"). ; 2) the amendment of an existing Rule (an "Amendment"); 3) the repeal of an existing Rule (a "Repeal"); 4) the modification of an existing Rule's Mutability Index (a "Mutation"). Additional Rule Changes may be created by appropriate legislation. No Rule Change may directly change any part of the Game State other than the Rules. No Rule may be changed except by the means of a Rule Change of a type specified in the Rules. [CFJ 708: An Amendment of a non-existing Rule is not a legal Rule Change.] History: Initial Immutable Rule 105, Jun. 30 1993 Mutated from MI=Unanimity to MI=3 by Proposal 1072, Oct. 4 1994 Amended by Proposal 1275, Oct. 24 1994 Renumbered from 1072 to 105 by Rule 1295, Nov. 1 1994 ---------------------------------------- Rule 115/0 (Semimutable, MI=3) Self-Referential Rules Allowed Rule Changes that affect Rules needed to allow or apply Rule Changes are as permissible as other Rule Changes. Even Rule Changes that amend or repeal their own authority are permissible. No Rule Change or type of move is impermissible solely on account of the self-reference or self-application of a Rule. [CFJ 700: Self-amending and self-repealing Rules are allowed.] History: Initial Immutable Rule 115, Jun. 30 1993 Mutated from MI=Unanimity to MI=3 by Proposal 1392, Jan. 24 1995 ---------------------------------------- Rule 107/0 (Semimutable, MI=3) Rule Changes Must Be Written Down Any proposed Rule Change must be written down (or otherwise communicated in print media) before it is voted on. If adopted, it must guide play in the form in which it was voted on. History: Initial Immutable Rule 107, Jun. 30 1993 Mutated from MI=Unanimity to MI=3 by Proposal 1391, Jan. 24 1995 ---------------------------------------- Rule 1339/3 (Semimutable, MI=3) Rule Changes There are two types of Rule Change. A Proposed Rule Change is a Rule Change which appears in a Proposal, and which, insofar as the Rules permit it to take effect, has the effect of Creating, Amending, Mutating, Repealing or otherwise changing a Rule as defined elsewhere in the Rules, directly as a result of the passage of a Proposal. A non-Proposed Rule Change has the same effect as a Proposed Rule Change, but insofar as the Rules permit it to take effect, it does so not as the direct result of the passage of a Proposal, but rather, indirectly, as the result of the effect or action of a Rule. All Rule Changes, of either type, are subject to the following constraints: An individual Rule Change must change exactly one Rule. Any Rule Change which affects an existing Rule must clearly identify the Number of the Rule to be affected. Any Rule Change which creates a New Rule may specify the Mutability Index of the New Rule; however, if the Mutability Index is specified it must be greater than or equal to 1. If the Mutability Index of any Rule created by a Rule Change is not specified, it shall be 1. Any Rule Change which creates a New Rule may specify the Category to which the New Rule will be assigned. If the Category specified exists, the Rule shall be assigned to that Category. If the Category specified does not exist, or no Category is specified, the Rulekeepor shall assign the Rule to an appropriate category of eir own choice. Any Rule Change which changes the Mutability Index of a Rule must clearly specify the new value of the Rule's Mutability Index. Any Rule Change which changes the text of a Rule must clearly and unambiguously specify the changes which are to be made. If the Rule Change quotes old text which is to be replaced with new text, then the quoted old text must match exactly with actual text in the Rule, with the exception of whitespace and capitalization. This takes precedence over Rules which would permit such differences, even if the differences would be considered inconsequential by such Rules. Any Rule Change which does not meet these criteria shall not have any legal force. [CFJ 822: Any Change to the Rules in a way other than the two methods described here is illegal.] History: Created by Proposal 1339, Nov. 29 1994 Amended(1) by Proposal 1414, Feb. 1 1995 Amended(2) by Proposal 1440, Feb. 21 1995 Mutated from MI=1 to MI=3 by Proposal 1532, Mar. 24 1995 Amended(3) by Proposal 1754, Oct. 21 1995 ---------------------------------------- Rule 594/2 (Mutable, MI=1) Proposals and Rule Changes A Proposal may contain one or more Rule Changes. If a Proposal containing Rule Changes is adopted, the Rule Changes contained in the Proposal shall take effect in the order they appear in the Proposal. Unless another Rule states otherwise, the Adoption Index of a Proposal shall be the minimum Adoption Index which would allow all Rule Changes and Directives within the Proposal to take effect, or 1, whichever is greater. In no case may a Proposal have an Adoption Index of less than 1. [CFJ 778: It is legal for a Proposal to contain zero Rule Changes.] History: Created by Proposal 594, Oct. 21 1994 Amended(1) by Proposal 1323, Nov. 21 1994 Amended(2) by Proposal 2399, Jan. 20 1996 ---------------------------------------- Rule 993/3 (Mutable, MI=1) Directives A Proposal is permitted to contain one or more Directives. A Directive, if it takes effect, causes some change in the Game State other than Changing a Rule. No Directive shall Change any Rule. A Directive takes effect if and only if: (i) the Proposal containing it is adopted; (ii) the Directive is of a type specifically defined by the Rules; and, (iii) the Adoption Index of the Proposal is at least the minimum Adoption Index necessary for such a Directive to take effect. Unless another Rule states otherwise, the minimum Adoption Index necessary for a Directive to take effect is 1. If a Proposal containing Directives which take effect is adopted, those Directives shall take effect in the order that they appear in the Proposal, and according to the Rule or Rules which define the type of each Directive in question. [CFJ 762: If a "Directive" is not defined by the Rules, it is not a Directive, but is still part of the Proposal. (This may or may not apply after the adoption of Proposal 2399.) CFJ 778: It is legal for a Proposal to contain zero Directives.] History: Created by Proposal 807, date unknown Amended by Proposal 891, date unknown Amended by Rule 750, date unknown Amended by Proposal 993, ca. Aug. 18 1994 Amended by Rule 750, ca. Aug. 18 1994 Amended(1) by Proposal 1330, Nov. 22 1994 Amended(2) by Proposal 1620, Jul. 17 1995 Infected and Amended(3) by Rule 1454, Aug. 21 1995 Amended(3) by Proposal 2399, Jan. 20 1996 ---------------------------------------- Rule 404/0 (Mutable, MI=1) Legality of Proposals As long as a Proposal satisfies all requirements in place at the time of its making for the proper making of Proposals, the act of making such a Proposal is legal regardless of its content. It is legal to propose a Rule which conflicts with other Rules or with itself, which is paradoxical, or which cannot be applied. History: Created by Proposal 404, Sep. 3 1993 ---------------------------------------- Rule 1605/0 (Mutable, MI=1) Proposing Entities Let there exist a type of entity called a Proposing Entity. Only Proposing Entities have the right to make Proposals, Each Player is a Proposing Entity. Other entities are Proposing Entities only if defined as such by the Rules. Any other Rule notwithstanding, in order to make a Proposal a Proposing Entity must either be a Player or have an Executor which is a Player, and must also possess a Treasury. History: Created by Proposal 2522, Mar. 10 1996 ---------------------------------------- Rule 1607/0 (Mutable, MI=1) The Promotor There shall exist the Office of the Promotor. The Promotor shall receive a weekly salary of 4 Points. History: Created by Proposal 2522, Mar. 10 1996 ---------------------------------------- Rule 1036/5 (Mutable, MI=1) Making and Distributing Proposals As soon as possible after the Promotor receives a new Proposal, e shall assign to it a Number as specified in other Rules. Within seven days of the receipt of a Proposal, and not later than any subsequently received Proposal, the Promotor shall distribute this Proposal to the Public Forum, accompanied by its Number, the identity of its Proposing Entity, and its Adoption Index. The failure of the Promotor to distribute any of the above accompaniments with a Proposal does not deprive the distribution of the Proposal of any legal effect. [CFJ 10: A Proposal remains a Proposal even if the Promotor changes before the Proposal is distributed. CFJ 776: There is no failure of distribution if the Promotor announces he has received no Proposals when in fact he has, unless it has been more than one week since the Proposals were sent to em.] History: Initial Mutable Rule 204, Jun. 30 1993 Amended by Proposal 415, Sep. 3 1993 Amended by Proposal 1036, Sep. 21 1994 Amended by Rule 750, Sep. 21 1994 Amended(1) by Proposal 1530, Mar. 24 1995 Amended(2) by Proposal 1546, Apr. 14 1995 Amended(3) by Proposal 2056, Dec. 19 1995 Amended(4) by Proposal 2451, Feb. 6 1996 Amended(5) by Proposal 2522, Mar. 10 1996 ---------------------------------------- Rule 109/2 (Semimutable, MI=3) Proposal Numbers The Promotor shall give each submitted Proposal a Number for reference. The Number of a Proposal shall be the least integer greater than all other Numbers previously assigned to a Proposal (including numbers assigned to Proposals later determined to have been incorrectly submitted), or 301, whichever is greater. History: Initial Immutable Rule 109, Jun. 30 1993 Mutated from MI=Unanimity to MI=3 by Proposal 1057, Sep. 20 1994 Amended by Proposal 1067, Oct. 4 1994 Amended by Rule 750, Oct. 4 1994 Renumbered from 1067 to 109 by Rule 1295, Nov. 1 1994 Amended(1) by Proposal 1435, Feb. 14 1995 Amended(2) by Proposal 1530, Mar. 24 1995 ---------------------------------------- Rule 1349/0 (Mutable, MI=1) Rule Numbering The Rulekeepor shall give each newly-enacted Rule a Number for reference when it is created. The Number of a Rule shall be the least integer greater than all other Numbers previously given to a Rule (including numbers assigned to Rules later determined to have been incorrectly enacted), or 301, whichever is greater. Once a Rule has been given a Rule Number, it shall not be changed except as specified in the Rules. History: Created by Proposal 1349, Nov. 29 1994 ---------------------------------------- Rule 748/0 (Mutable, MI=1) Blank/Required Lines Don't Count Whenever the length of a Proposal is determined, any blank lines within that Proposal shall not be counted towards the number of lines in that Proposal. In addition, any lines which are required by legislation, including a Title or a Declaration, shall likewise not be counted towards the number of lines in that Proposal. History: Created by Proposal 748, Dec. 1 1993 ---------------------------------------- Rule 1003/2 (Mutable, MI=1) No Coercive Proposals Proposals whose obvious and direct intent is to coerce a Player into voting against eir conscience shall not take effect even if adopted, any Rule to the contrary notwithstanding. [CFJ 756: This includes only those Proposals which penalize people based on their votes, even though the penalizing is indirect. However, it is only coercive if the threat is large enough to be effective.] History: Created by Proposal 822, ca. Feb. 18 1994 Amended by Proposal 1003, ca. Aug. 25 1994 Amended by Rule 750, ca. Aug. 25 1994 Infected and Amended(1) by Rule 1454, Jun. 4 1995 Amended(2) by Proposal 1623, Jul. 17 1995 ---------------------------------------- Rule 1065/8 (Mutable, MI=1) Discourages Too Many Proposals Whenever a Proposing Entity submits a Proposal, it shall lose 1 Mark for each Proposal, in excess of five, previously submitted by that Proposing Entity during the current Nomic Week. The Promotor shall detect and report this penalty, no later than the time the Proposal is distributed. History: Created by Proposal 843, Mar. 3 1994 Amended by Proposal 936, ca. Jul. 10 1994 Amended by Rule 750, ca. Jul. 10 1994 Amended by Proposal 1065, ca. Oct. 11 1994 Amended by Rule 750, ca. Oct. 11 1994 Amended(1) by Proposal 1270, Oct. 24 1994 Amended(2) by Proposal 1405, Jan. 29 1995 Amended(3) by Proposal 1530, Mar. 24 1995 Amended(4) by Proposal 1693, Sep. 1 1995 Amended(5) by Proposal 1750, Oct. 21 1995 Null-Amended(6) by Proposal 1763, Oct. 31 1995 Amended(7) by Proposal 2054, Dec. 19 1995 Amended(8) by Proposal 2522, Mar. 10 1996 ---------------------------------------- ======================================= Voting on Proposals This Category includes Rules regulating Voting on Proposals and other actions which take place during the Voting Period. ---------------------------------------- Rule 1449/2 (Mutable, MI=1) The Assessor There is an Office called the Office of Assessor. The Assessor has a weekly salary of 8 points. History: Created by Proposal 1531, Mar. 24 1995 Infected and amended(1) by Rule 1454, Jun. 18 1995 Amended(2) by Proposal 1776, Nov. 6 1995 ---------------------------------------- Rule 106/0 (Semimutable, MI=3) Adopting Proposals All Proposals made in the proper way shall be voted upon. A Proposal shall be adopted if and only if it receives the required number of votes and if Quorum is achieved. History: Initial Immutable Rule 106, Jun. 30 1993 Mutated from MI=Unanimity to MI=3 by Proposal 1073, Oct. 4 1994 Amended by Proposal 1278, Oct. 24 1994 Renumbered from 1073 to 106 by Rule 1295, Nov. 1 1994 Infected, but not amended, by Rule 1454, May 7 1995 ---------------------------------------- Rule 693/1 (Mutable, MI=1) Prescribed Voting Period The prescribed Voting Period for a Proposal is ten days, beginning at the time the Proposal is distributed to all Players. History: Initial Mutable Rule 205, Jun. 30 1993 Amended by Proposal 693, Nov. 12 1993 Amended(1) by Proposal 1564, Apr. 28 1995 ---------------------------------------- Rule 1451/3 (Mutable, MI=1) Disowning Proposals A Proposal is disowned when its Proposer sends a message to the Public Forum disowning it, provided that the Proposal in question either has not yet been distributed, or less than four days have passed since its distribution. Only the Proposer of a given Proposal is permitted to disown it. A Proposal which has been distributed is not permitted to be disowned if its Proposer is currently the Assessor or has been the Assessor at any time after that Proposal's distribution. When a Proposal is disowned, five Points are transferred from its Proposer to the Bank; this transfer is to be reported by the Assessor. All other transfers of Currencies or Blot Changes occuring as a result of the submission of, voting upon, or adoption of that Proposal do not take place, regardless of the outcome of the Vote on that Proposal. This Rule takes precedence over any Rule which would seek to transfer Currencies or cause Blot Changes as a result of the submission of, voting upon, or adoption of, a Proposal. History: Created by Proposal 1549, Apr. 14 1995 Amended(1) by Proposal 1700, Sep. 1 1995 Amended(2) by Proposal 2473, Feb. 16 1996 Amended(3) by Proposal 2522, Mar. 10 1996 ---------------------------------------- Rule 206/6 (Mutable, MI=1) Voting Entities and Votes A Voting Entity is an Entity which is generally authorized by the Rules to cast a vote or votes on a Proposal, although other Rules may withdraw this authorization from a Voting Entity in specific circumstances without that Entity thereby ceasing to be a Voting Entity. No Entity is permitted to vote on a Proposal unless it is a Voting Entity, and only those Entities designated by the Rules to be Voting Entities are Voting Entities. Players and Groups are Voting Entities. Each Voting Entity has two votes on a Proposal, unless another Rule says otherwise. However, no such Entity shall have more than five votes on any Proposal, regardless of what any other Rule may say to the contrary. The casting of any votes in addition to an Entity's first vote may only be achieved by the casting of Extra Votes, if that is permitted, as specified in other Rules. This Rule defers to all other Rules which do not contain this sentence. [CFJ 117: A Vote takes place when it is sent, not when it is counted. CFJ 707: One is allowed to change one's Vote during the Voting Period.] History: Initial Mutable Rule 206, Jun. 30 1993 Amended(1) by Proposal 1479, Mar. 15 1995 Amended(2) by Proposal 1553, Apr. 14 1995 Amended(3) by Proposal 1565, Apr. 28 1995 Amended(4) by Proposal 1641, Aug. 1 1995 Amended(5) by Proposal 1754, Oct. 21 1995 Infected and Amended(6) by Rule 1454, Nov. 14 1995 ---------------------------------------- Rule 452/7 (Mutable, MI=1) No Electioneering by the Assessor During the prescribed Voting Period of a Proposal, the Assessor is prohibited from making use of any knowledge of the current status of the vote on that Proposal which e would not have were e not the Assessor, in any attempt to influence the result of the vote on the Proposal. Doing so is a Class C Crime. This Rule shall in no way prohibit the Assessor from posting, at any time and to the Public Forum, a list of those Players who have already voted upon a given Proposal. Doing so is not a Crime, unless specified as such by another Rule. [CFJ 36: The Assessor may not use eir knowledge of the Votes to withdraw or disown a Proposal. CFJ 750: Only if the Assessor has the intent of influencing Votes is e in violation of this Rule. Influencing the number of Votes also counts as influencing the result of the vote.] History: Created by Proposal 452, Sep. 10 1993 Amended(1) by Proposal 1446, Feb. 21 1995 Amended(2) by Proposal 1531, Mar. 24 1995 Amended(3) by Proposal 1534, Apr. 4 1995 Amended(4) by Proposal 1584, May 15 1995 Amended(5) by Proposal 1686, Sep. 1 1995 Amended(6) by Proposal 1718, Sep. 19 1995 Amended(7) by Proposal 1752, Oct. 21 1995 ---------------------------------------- Rule 683/4 (Mutable, MI=1) Legal Votes Voting Entities may cast a vote of FOR, AGAINST, or ABSTAIN on any Proposal within its prescribed Voting Period. In order to be legally cast, a vote by a Player or a Group must be received by the Counting Assessor or posted to the Public Forum during the prescribed Voting Period. The conditions under which a Vote by a Voting Entity which is not a Player or a Group (if any such exist) is legally cast are described in other Rules. The Assessor will reveal the Votes cast by each Voting Entity only after the prescribed Voting Period has ended. History: Initial Mutable Rule 207, Jun. 30 1993 Amended by Proposal 683, Nov. 10 1993 Amended(1) by Proposal 1473, Mar. 8 1995 Amended(2) by Proposal 1531, Mar. 24 1995 Amended(3) by Proposal 1554, Apr. 17 1995 Amended(4) by Proposal 1641, Aug. 1 1995 ---------------------------------------- Rule 312/4 (Mutable, MI=1) A Point for Voting For each Proposal, and for each Player, if that Player casts a legal Vote on that Proposal, then that Player shall receive one Point at the end of the Voting Period of that Proposal. The Assessor shall detect and report these Point transfers, and shall do so no later than the time e announces the Voting Results of the Proposal for which the Player's Vote was cast. History: Created by Proposal 312, Jul. 15 1993 Amended(1) by Proposal 1554, Apr. 17 1995 Amended(2) by Proposal 1556, Apr. 17 1995 Amended(3) by Proposal 1579, Apr. 28 1995 Amended(4) by Proposal 1705, Sep. 4 1995 ---------------------------------------- ======================================= The End of the Voting Period This Category includes Rules regulating the adoption or failure of Proposals and other actions which take place at the end of the Voting Period or upon the announcement of Proposal results. ---------------------------------------- Rule 879/3 (Mutable, MI=1) Quorum Quorum for a Proposal is achieved if a vote is cast on that Proposal by 35% of all Players, or 50% of all the Players not On Hold, whichever is greater. Quorum for a Proposal is calculated using the number of Registered Players at the beginning of the prescribed Voting Period for that Proposal. History: Initial Mutable Rule 201, Jun. 30 1993 Amended by Proposal 879, Apr. 13 1994 Amended by Rule 750, Apr. 13 1994 Amended(1) by Proposal 1471, Mar. 8 1995 Amended(2) by Proposal 1554, Apr. 17 1995 Amended(3) by Proposal 1708, Sep. 4 1995 ---------------------------------------- Rule 208/2 (Mutable, MI=1) End of the Voting Period As soon as possible after the end of the Voting Period on a given Proposal, the Assessor shall publish all the Votes cast upon that Proposal. [CFJ 707: A Player may not change eir Vote after the end of the Voting Period.] History: Initial Mutable Rule 208, Jun. 30 1993 Amended(1) by Proposal 1401, Jan. 29 1995 Amended(2) by Proposal 1531, Mar. 24 1995 ---------------------------------------- Rule 955/3 (Semimutable, MI=3) Votes Required to Adopt a Proposal When the Voting Period for a Proposal has ended, the Votes which have been legally cast shall be counted by the Assessor. The Proposal shall then be assigned a Voting Index, as follows: the Proposal received no Votes opposed, and at least one Vote in favor, the Voting Index shall be Unanimity; if there are no Votes in favor, the Voting Index shall be zero; in all other cases, the Voting Index shall be the number of Votes in favor divided by the number of Votes opposed. If the Voting Index is greater than the Adoption Index for the given Proposal, or if both equal Unanimity, then that Proposal passes. Otherwise, it fails. History: Initial Mutable Rule 209, Jun. 30 1993 Amended by Proposal 396, Aug. 23 1993 Amended by Proposal 658, Oct. 29 1993 Amended by Proposal 761, Dec. 8 1993 Amended by Rule 750, Dec. 8 1993 Amended by Proposal 955, Jul. 25 1994 Amended by Rule 750, Jul. 25 1994 Amended(1) by Proposal 1279, Oct. 24 1994 Amended(2) by Proposal 1531, Mar. 24 1995 Amended(3) by Proposal 1723, Oct. 6 1995 Mutated from MI=1 to MI=3 by Proposal 2398, Jan. 20 1996 ---------------------------------------- Rule 1606/0 (Mutable, MI=1) Limits of Effectiveness of Adopted Proposals The effect of the adoption of a Proposal shall be limited to the application of those legally defined Rule Changes and Directives which are contained within the Proposal and which can be clearly identified as such. This Rule defers to any Rule which requires some event to take place as a consequence of the adoption of a Proposal. History: Created by Proposal 2522, Mar. 10 1996 ---------------------------------------- Rule 1322/2 (Semimutable, MI=3) Effectiveness of Rule Changes Every Rule Change shall have associated with it an Index, called its Power, which determines its ability to take effect. The Power of a non-Proposed Rule Change shall be the Mutability Index of the Rule in which the Rule Change is contained. The Power of a Proposed Rule Change shall be the Adoption Index of the Proposal in which the Rule Change is contained. No Rule Change may take effect unless its Power is not less than the current Mutation Index of the Rule it seeks to change, if any, and the Mutation Index that the Rule would possess after the change, if any. History: Created by Proposal 1322, Nov. 21 1994 Infected and Amended(1) by Rule 1454, Dec. 5 1995 Amended(2) by Proposal 2398, Jan. 20 1996 Mutated from MI=1 to MI=3 by Proposal 2398, Jan. 20 1996 ---------------------------------------- Rule 108/0 (Semimutable, MI=3) When May Rule Changes Take Effect? No Rule Change may take effect earlier than the moment of the adoption of the Proposal in which it is contained, if it is a proposed Rule Change, or the moment of the adoption of the current form of the Rule which requires the Rule Change, if it is a non-proposed Rule Change. No Rule Change may have retroactive application. [CFJ 1: This does not prevent Rules from being explicitly dependent on circumstances before they are enacted.] History: Initial Immutable Rule 108, Jun. 30 1993 ... Amended by Proposal 1276, Oct. 24 1994 Renumbered from 1074 to 108 by Rule 1295, Nov. 1 1994 ---------------------------------------- Rule 376/3 (Mutable, MI=1) When Proposals Take Effect A Proposal which is Adopted takes effect at the time date- stamped on the first message sent by the Assessor to reach the Public Forum announcing the results of the voting on that Proposal. If the message sent by the Assessor announcing the results of the voting on a Proposal also contains the results of voting upon other Proposals, all such Proposals shall take effect at the same time, but in order by increasing Proposal Number. History: ... Amended(1) by Proposal 1271, Oct. 24 1994 Amended(2) by Proposal 1490, Mar. 15 1995 Amended(3) by Proposal 1531, Mar. 24 1995 ---------------------------------------- Rule 1561/0 (Semimutable, MI=2) Illegality of Bonus Clauses Proposals which contain clauses awarding, penalizing, or otherwise changing the Currency holdings of the Treasury of any Voting Entity based on the vote cast by that Entity on that Proposal shall not take effect even if adopted, any Rule to the contrary notwithstanding. History: Created by Proposal 2449, Feb. 6 1996 ---------------------------------------- Rule 1069/1 (Mutable, MI=1) Amendment Numbers A Rule's Amendment Number is equal to the number of times a Rule having that Rule Number has been amended. The default Amendment Number is zero; this is the value of a Rule's Amendment Number when the Rule is Created, and it is the value of the Amendment Number of every Rule unless it is specified by the Rules to be otherwise. A Rule's Amendment Number shall be displayed in Official copies of the Ruleset, appended to the Rule Number, and separated by a forward slash. Responsibility is given to the Rulekeepor to accurately update Amendment Numbers. Amendment Numbers may be used for Official purposes and in Official documents to distinguish between old versions of a Rule and the Rule's current text. [CFJ 738: If no Amendment Number is present in a communication, it is assumed to mean the current version of a Rule.] History: Created by Proposal 750, Dec. 1 1993 Amended by Proposal 1069, Oct. 4 1994 Amended by Rule 750, Oct. 4 1994 Amended(1) by Proposal 1502, Mar. 24 1995 ---------------------------------------- Rule 833/3 (Mutable, MI=1) Reward or Penalty for Proposing At the end of the Voting Period for a Proposal, if a Proposal has received more FOR Votes than AGAINST Votes, the Proposer of that Proposal gains a number of Points equal to the number of FOR Votes less the number of AGAINST Votes. If, however, a Proposal has received more AGAINST Votes than FOR Votes, the Proposer loses a number of Points equal to the number of AGAINST Votes less the number of FOR Votes. If the number of FOR Votes and AGAINST Votes are equal, the Proposer neither gains nor loses Points as a result of this Rule. For the purpose of this Rule, Votes by Voting Entities which are not Players do not count, nor does any tiebreaking Vote cast by the Assessor. The Assessor shall report the transfers required by this Rule, and shall do so no later than the time e announces the Voting Results of the Proposal in question. History: ... Amended by Proposal 833, Mar. 1 1994 Amended by Rule 750, Mar. 1 1994 Amended(1) by Proposal 1554, Apr. 17 1995 Amended(2) by Proposal 1702, Sep. 1 1995 Amended(3) by Proposal 1705, Sep. 4 1995 ---------------------------------------- Rule 947/4 (Mutable, MI=1) Bonus for Repeal If there are more than 100 Rules, and a Proposal is adopted which, as part or all of its effect, repeals one or more Rules, that Proposal's Proposer shall receive 5 Points. This transfer shall be reported by the Rulekeepor, who shall do so as soon as possible after the Proposal's Adoption. History: Created by Proposal 947, Jul. 3 1994 Amended(1) by Proposal 1705, Sep. 4 1995 Infected and Amended(2) by Rule 1454, Oct. 2 1995 Amended(3) by Proposal 2047, Dec. 19 1995 Amended(4) by Proposal 2522, Mar. 10 1996 ---------------------------------------- Rule 1583/0 (Mutable, MI=1) Proposal Penalties Halved for New Players All penalties that are a direct result of voting on Proposals are halved if the Player receiving the Penalty registered for the first time as a Player within the past five weeks. This Rule take precedence over all other Rules pertaining to penalties that are a direct result of voting. History: Created by Proposal 2477, Feb. 16 1996 ---------------------------------------- ======================================= Referenda and Elections This Category includes Rules regulating voting on entities other than Proposals, particularly Referenda and Elections. ---------------------------------------- Rule 1434/1 (Mutable, MI=1) Default Procedure for Referendum Voting When a Referendum Vote is required and the procedure is not defined elsewhere, the following Standard Referendum Voting Procedure shall be used. Details specified herein are defaults which may be modified by other Rules for specific situations. This procedure shall under no circumstances be used for Voting on Proposals, unless specifically required by the Rules governing specific types of Proposals. * Vote Collector: The Vote Collector is the Entity responsible for collecting and tallying the Votes and announcing the result. This Entity is the Speaker if not otherwise specified. * Voting Entities: Every Player not on Hold may Vote on a Referendum. On Hold status is measured at the time a Player sends eir Vote. * Voting: A Voting Entity Votes by sending eir Vote to the Vote Collector during the Voting Period, indicating what Referendum e is Voting on, and what eir Vote is. * Vote Values: A Vote is FOR, AGAINST, or ABSTAIN. Words which are effectively synonymous with these are also permissible. * Vote Strength: Every Vote has equal strength. No Voting Entity may Vote more than once on any single Referendum. * Retraction: A Vote, once sent to the Vote Collector, cannot be changed. * Start of Voting: The Voting Period begins at the time the first correct and legal announcement that a Referendum is begun, as defined in other Rules, is sent to the Public Forum, together with the identity of the Vote Collector. * Duration of Voting: The Voting Period lasts for one Week. All Votes received by the Vote Collector outside of the Voting Period have no effect. * Secrecy During Voting: Unless otherwise specified, the Vote Collector may not give away any information about the Votes while the Voting is underway. * Secrecy After Voting: Unless otherwise specified, the Vote Collector shall post to the Public Forum, after the Voting Period is over, the number of Votes of each kind as well as the name and Vote of each Entity which cast a Vote. * Adoption Ratio: The Adoption Ratio, the ratio of FOR Votes on a Referendum relative to the AGAINST VOTES, must be greater than 1 for the Referendum to pass. If it is not, the Referendum fails. * Quorum: The Quorum, the smallest allowable fraction of eligible Voting Entities which actually Vote on a particular Referendum, is 50%. If a smaller fraction Voted, the Referendum automatically fails. * Nonperformance by Vote Collector: The Vote Collector must perform eir required duties, but if the result of a Referendum is not announced within one Week following the end of the Voting Period, it automatically fails. * Effectiveness: the full effects of a Referendum, as defined in Rules which make use of the Referendum procedure, come into force as of the moment the results are announced to the Public Forum. History: Created by Proposal 1456, Mar. 1 1995 Amended(1) by Proposal 2543, Mar. 19 1996 ---------------------------------------- Rule 1574/0 (Mutable, MI=1) Referndum to Install There shall be a class of legal Referenda known as Referenda to Install. Such a Referendum, if it takes effect, has the effect of installing the named player in the stated position. Any Player is permitted to call such a Referendum at any time, by posting such to the Public Forum and meeting all other requirements listed in this Rule. A Referendum to Install must name exactly one Player to fill the stated position, and the position to be filled. The position named in such a Referendum must be one of the following: * the position of Speaker * the Office of Promotor * the Office of Assessor * the Office of Clerk of the Courts * the Office of Registrar. For such a Referendum the default procedure for Referenda is modified as follows: the Vote Collector is the Player who called for the Referendum. Every Player is a Voting Entity. The Adoption Ratio of a Referendum to Install is 2. Quorum for such a Referendum is 30% of all Players. A Referendum to Install takes effect if and only if all of the following conditions are true: * the Referendum passes * all requirements for such a Referendum are met * the Player named in the Referendum has, during the Duration of Voting, posted eir consent to fill the position named in the Referendum. When a Referendum to Install takes effect, the Player named therein immediately fills the position named therein. Any other Player holding that position simultaneously ceases to hold it. History: Created by Proposal 2464, Feb. 16 1996 ---------------------------------------- Rule 1445/2 (Mutable, MI=1) Defaults for Elections When an Election is required and the procedure is not defined elsewhere, the following Standard Election Procedure shall be used. Details specified herein are defaults which may be modified by other Rules for specific situations. * Vote Collector: The Vote Collector is the Entity responsible for taking nominations, collecting and tallying the Votes, and announcing the result. Unless otherwise specified, this Entity is the Player who is Speaker at the time the Referendum starts. If another Player is specified, this Player shall be the Vote Collector for the entire duration of the Referendum. If the Vote Collector deregisters or is deregistered before the Voting Period ends, the Election has no Winner. * Nominating Entities: Every Player not on Hold may Nominate eirself in an Election. On Hold status is measured at the time a Player makes a Nomination. * Nominations: A Nominating Entity makes a Nomination by sending a message to the Vote Collector during the Nominations Period, indicating what Election e is Nominating for. * Candidates: A Player who has Nominated for an Election is called a Candidate for that Election. * Retraction: A Nomination, once sent to the Vote Collector, may be retracted before the end of the Nominating Period. A player may retract a Nomination e has made by sending a message to the Vote Collector, indicating the e wished to retract eir Nomination. * Start of Nominations: The Nominating Period begins at the time of the first correct and legal announcement that the Election has begun, as required by the Rules calling for the Election. * Duration of Nominations: The Nominating Period lasts for one Week. All Nominations received by the Vote Collector outside of the Nominating Period have no effect. * Secrecy: Nominations need not be kept secret. * Voting: A Referendum shall begin at the time Candidates are Announced. The standard procedure for referendums shall be used, with the following exceptions: * Voting: A Referendum shall begin at the end of the Nominating Period. The standard procedure for referendums shall be used, with the following exceptions: * Vote Collector: The Vote Collector for the Referendum is the same as the Vote Collector for the Election. * Vote Values: A Vote is the name of exactly one of the Candidates for the given Election. Words which are effectively synonymous with these are also permissible. * Adoption: The Winner of the Election is the Candidate for whom the most votes were cast. If there is more than one such candidate, the Speaker may make a casting vote. * Quorum: The Quorum, the smallest allowable fraction of eligible Voting Entities which actually Vote in a particular Election, is 50%. If a smaller fraction Voted, the Election has no Winner. * Nonperformance by Vote Collector: The Vote Collector must perform eir required duties, but if the result of an Election is not announced within one Week following the end of the Voting Period, the Election has no Winner. History: Created by Proposal 1499, Mar. 24 1995 Amended(1) by Proposal 1763, Oct. 31 1995 Amended(2) by Proposal 2543, Mar. 19 1996 ---------------------------------------- Rule 1558/1 (Mutable, MI=1) Defaults for Elections for Offices When the Rules require that an Election be conducted to fill an Office, that Election shall be conducted in accordance with the usual Rules for Elections, with the following exceptions: * The Vote Collector of the Election shall be the Registrar, unless the Office which the Election is seeking to fill is that of the Registrar, in which case the Vote Collector shall be the Speaker; and * No Player may be Nominated who would not be permitted to hold the Office which the Election is seeking to fill. History: Created by Proposal 2442, Feb. 6 1996 Amended(1) by Proposal 2564, Apr. 6 1996 ---------------------------------------- ======================================= Petitions This Category includes Rules regulating Petitions. ---------------------------------------- Rule 1604/0 (Mutable, MI=1) Petitions Let there be an Entity known as a Petition which consists of any a body of text designated as a Petition. Let there be an Entity known as a Signature which shall exist only within a Petition, shall be associated with exactly one Player, and which shall be known as that Player's Signature. Any number of Signatures may be contained by a single Petition, but a single Petition may only contain exactly one Signature associated with any single Player. History: Created by Proposal 2515, Mar. 3 1996 ---------------------------------------- ======================================= The Clerk of the Courts This Category includes Rules concerning the Office of the Clerk of the Courts. ---------------------------------------- Rule 889/2 (Mutable, MI=1) Clerk of the Courts There shall exist the Office of the Clerk of the Courts, with the general responsibility for the administration of the judicial process, as described elsewhere. The Salary of the Clerk of the Courts shall be five Points. History: Created by Proposal 406, Sep. 3 1993 Amended by Proposal 889, Apr. 13 1994 Amended by Rule 750, Apr. 13 1994 Amended(1) by Proposal 1441, Feb. 21 1995 Amended(2) by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 1450/1 (Mutable, MI=1) Speaker Cannot Stay CotC or Justiciar The Speaker shall never hold either of the Office of Clerk of the Courts or the Office of Justiciar in the normal fashion. If the Clerk of the Courts or the Justiciar becomes Speaker, e is immediately retired from whichever of those Offices e holds. History: Created by Proposal 1547, Apr. 14 1995 Amended(1) by Proposal 2442, Feb. 6 1996 ---------------------------------------- ======================================= Calling for Judgement This Category includes Rules regulating calling for Judgement. ---------------------------------------- Rule 991/3 (Mutable, MI=1) Invoking Judgement Any Player who seeks formal resolution of any dispute pertaining to this Nomic shall be permitted to request such by submitting a Call for Judgement to the Clerk of the Courts. For the purpose of this and other Rules, the submission of a Call for Judgement shall constitute proof of the existence of a dispute. Any document submitted to the Clerk of the Courts and which is clearly marked as a Call for Judgement is a Call for Judgement. The Clerk shall distribute the text of a Call for Judgement, along with any additional material submitted by the Caller (including, but not limited to, Arguments and Evidence) not later than the time e announces the identity of the first Judge assigned to Judge it. History: Initial Mutable Rule 213, Jun. 30 1993 Amended by Proposal 407, Sep. 3 1993 Amended by Proposal 991, ca. Aug. 12 1994 Amended by Rule 750, ca. Aug. 12 1994 Infected and amended(1) by Rule 1454, Oct. 23 1995 Amended(2) by Proposal 2042, Dec. 11 1995 Amended(3) by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 897/1 (Mutable, MI=1) Barring Players from Judgement The Player who submits a Call for Judgement is permitted to specify up to three Players who are to be Barred from Judging that CFJ. Any Players that are so Barred are ineligible to Judge that CFJ. History: Created by Proposal 897, date unknown Amended(1) by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 1562/0 (Mutable, MI=1) Excess CFJs The Clerk of the Courts shall dismiss without prejudice any CFJ made by a Player who has previously made five or more CFJs during that Nomic Week. Such a CFJ is called an "excess CFJ". The Player who submits an excess CFJ commits an Infraction, to be reported by the Clerk of the Courts and bearing a penalty of 10 Marks. If the Clerk of the Courts fails to dismiss an excess CFJ, and instead assigns it to a Judge, then the CFJ shall not be dismissed for being an excess CFJ and shall be Judged (or dismissed) exactly as any other CFJ. Failing to dismiss an excess CFJ is an Infraction, to be reported by the Justiciar, and bearing a penalty of 10 Marks and two Blots. History: Created by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 1563/0 (Mutable, MI=1) Statement of a CFJ In order to be Judged, a Call for Judgement must contain a single clearly-labeled Statement which must be able to be determined by the means of logical reasoning, with the presumption of perfect knowledge, to be either TRUE or FALSE. Statements which are inherently contradictory or which are vacuous are not acceptable, and a CFJ containing such a Statement shall not be Judged. If a Call for Judgement does not contain a Statement of the sort required by this Rule, its Judge is required to dismiss the CFJ, as described elsewhere. It is permitted for a Call for Judgement to contain Arguments, Evidence, or other material placed there at the Caller's discretion. However, the Judge is not required to take notice of any part of the CFJ other than the Statement in formulating eir Judgement. History: Created by Proposal 2457, Feb. 16 1996 ---------------------------------------- ======================================= Selecting a Judge This Category includes Rules describing how a Judge is selected for a CFJ. ---------------------------------------- Rule 951/9 (Mutable, MI=1) Selecting a Judge Whenever there is a Call for Judgement which is neither Judged nor dismissed, and to which no Player who is eligible to Judge that CFJ is assigned to Judge that CFJ, the Clerk of the Courts shall randomly select, from amongst those Players eligible, a Judge to be assigned to Judge that CFJ as soon as possible after this condition becomes known to the Clerk of the Courts. The Clerk shall distribute the identity of the Player who is assigned to Judge a CFJ as soon as possible after the selection is made. [CFJ 723: The CotC may make another assignment, (without legal effect) as long as e makes one according to this Rule as well.] History: Initial Mutable Rule 214, Jun. 30 1993 Amended by Proposal 364, Aug. 8 1993 Amended by Proposal 410, Aug. 26 1993 ... Amended by Proposal 586, date unknown Amended by Proposal 647, Oct. 29 1993 Amended by Proposal 793, ca. Jan. 31 1994 Amended by Rule 750, ca. Jan. 31 1994 Amended by Proposal 890, Apr. 13 1994 Amended by Rule 750, Apr. 13 1994 Amended by Proposal 951, Jul. 25 1994 Amended by Rule 750, Jul. 25 1994 Amended(1) by Proposal 1306, Nov. 4 1994 Amended(2) by Proposal 1384, Jan. 17 1995 Amended(3) by Proposal 1408, Jan. 29 1995 Amended(4) by Proposal 1500, Mar. 24 1995 Amended(5) by Proposal 1644, Aug. 1 1995 Amended(6) by Proposal 1705, Sep. 4 1995 Amended(7) by Proposal 2457, Feb. 16 1996 Null-Amended(8) by Proposal 2506, Mar. 3 1996 Amended(9) by Proposal 2553, Mar. 22 1996 ---------------------------------------- Rule 698/3 (Mutable, MI=1) Always an Eligible Judge Every Active Player is eligible to Judge a a given CFJ unless specifically made ineligible by some Rule. The Caller of a given CFJ is never eligible to Judge that CFJ. If there would otherwise be no Players eligible to Judge a CFJ, then all Active Players, excluding the Caller and those Players Barred by the Caller, shall be eligible, any other Rule to the contrary notwithstanding. If this still does not result in there being any Players eligible to Judge, then all Players (Active or not), excluding the Caller and those Players Barred by the Caller, shall be eligible. If this still does not result in there being any Players eligible to Judge, then all Players, excluding the Caller, shall be eligible. This Rule takes precedence over any Rule or combination of Rules which would result in there being no Players eligible to Judge a given CFJ. History: Created by Proposal 482, Sep. 30 1993 Amended by Proposal 698, Nov. 12 1993 Amended(1) by Proposal 1385, Jan. 17 1995 Amended(2) by Proposal 1734, Oct. 15 1995 Amended(3) by Proposal 2457, Feb. 26 1996 ---------------------------------------- Rule 1567/0 (Mutable, MI=1) Making Oneself Ineligible To Judge a CFJ A Player is permitted to make eirself ineligible to Judge a specific CFJ by notifying the Clerk of the Courts of this desire. A Player who does so shall lose two Points, but only if e has already been assigned to Judge that CFJ; this transfer shall be reported by the Clerk of the Courts. History: Created by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 1568/0 (Mutable, MI=1) Judges On Hold Any Player who goes on Hold while selected as the Judge of one or more CFJs commits an Infraction for each such CFJ. This Infraction is to be reported by the Clerk of the Courts, and has a penalty of two Points per occurrence. History: Created by Proposal 2457, Feb. 16 1996 ---------------------------------------- ======================================= Delivering Judgement This Category includes Rules regulating the Judgement delivered by the Judge, as well as Injunctions. ---------------------------------------- Rule 408/3 (Mutable, MI=1) Accepting Judge-ship The Player assigned to Judge a Call for Judgement is required to either return a Judgement upon that CFJ or dismiss that CFJ within seven days of when e was assigned to Judge it. If e fails to do so, e ceases to be eligible to Judge that CFJ, ceases to be assigned to Judge that CFJ, and commits an Infraction to be reported by the Clerk of the Courts and breaing bearing a penalty of three Blots. However, if the Player assigned to Judge a CFJ ceases to be eligible prior to the end of the permitted time, e is neither required nor permitted to either return a Judgement on, or dismiss, that CFJ, and ceases to be the Judge assigned to that CFJ at the moment e becomes ineligible. History: Initial Mutable Rule 215, Jun. 30 1993 Amended by Proposal 408, Sep. 3 1993 Amended(1) by Proposal 1383, Jan. 17 1995 Amended(2) by Proposal 1500, Mar. 24 1995 Amended(3) by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 591/3 (Mutable, MI=1) Legal Judgements A Judge returns a Judgement by sending it to the Clerk of the Courts. A Judgement must be either TRUE or FALSE, and must be delivered to the Clerk not later than the end of the permitted time for deliberation. A Judgement returned after the end of the permitted deliberation period, or by a Player ineligible to be Judge of that CFJ is not legal and shall not be accepted by the Clerk. A CFJ has been Judged when a legal Judgement has been received by the Clerk. As soon as possible after the receipt of a legal Judgement, the Clerk shall distribute the Judgement to the Public Forum. A Judge who delivers Judgement on a CFJ shall receive a Judicial Salary of 3 Points. [In the Judgement of CFJ 794, the CotC determined that a Judgement of the form "If X then TRUE else FALSE" is legal only if the truth- value of X itself is unambiguous.] History: Initial Mutable Rule 216, Jun. 30 1993 Amended by Proposal 409, Aug. 26 1993 Amended by Proposal 591, Oct. 21 1993 Amended(1) by Proposal 1320, Nov. 21 1994 Amended(2) by Proposal 1487, Mar. 15 1995 Amended(3) by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 217/3 (Mutable, MI=1) Judgements Must Accord with the Rules All Judgements must be in accordance with the Rules; however, if the Rules are silent, inconsistent, or unclear on the Statement to be Judged, then the Judge shall consider game custom, commonsense, past Judgements, and the best interests of the game before applying other standards. [CFJ 684: An Injunction on the interpretation of a Rule is part of Game Custom.] History: Initial Mutable Rule 217, Jun. 30 1993 Amended(1) by Proposal 1635, Jul. 25 1995 Infected and amended(2) by Rule 1454, Aug. 7 1995 Amended(3) by Proposal 2507, Mar. 3 1996 ---------------------------------------- Rule 1575/0 (Mutable, MI=1) Standards of Proof A CFJ alleging that a Player has violated a Rule or committed a Crime shall not be judged TRUE unless the evidence is sufficient to be certain of that Judgement beyond reasonable doubt. In all other CFJs, the Judgement shall be consistent with the preponderance of the evidence at hand. History: Created by Proposal 2469, Feb. 16 1996 ---------------------------------------- Rule 451/1 (Mutable, MI=1) Determination of Judgement--Timing When a Judge is considering eir Judgement of a Statement contained in a CFJ, e shall make eir evaluation based on the truth or falsity of the Statement at the time the CFJ was issued. History: Created by Proposal 451, Sep. 10 1993 Amended(1) by Proposal 1412, Feb. 1 1995 ---------------------------------------- Rule 1565/0 (Mutable, MI=1) Dismissal of a CFJ A Judge dismisses a CFJ by sending a message to the Clerk of the Courts stating that e dismisses the CFJ, and detailing the reason for dismissal. A dismissal returned after the end of the permitted deliberation period, or by a Player ineligible to be Judge of that CFJ, is not legal and shall not be accepted by the Clerk. A CFJ is dismissed when a legal dismissal has been received by the Clerk; however, if the dismissal is subsequently set aside, then that CFJ is no longer dismissed and shall again be considered. As soon as possible after the receipt of a legal dismissal, the Clerk shall distribute the notice of dismissal and the Judge's reason for dismissal to the Public Forum. A Judge who dismisses a CFJ shall receive a Judicial Salary of 3 Points. History: Created by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 1569/0 (Mutable, MI=1) Reasons for Dismissal The Judge of a CFJ shall dismiss the CFJ when one (or more) of the following applies to that CFJ: * The CFJ contains no clearly-identifiable Statement to be Judged; * The CFJ's Statement does not logically admit to being either TRUE or FALSE; * The CFJ's Statement does not relate to a matter in which the Rules have bearing or concern; * The CFJ's Statement fails to comply with any other Rules pertaining to legal Statements in Calls for Judgement; or * The CFJ lacks standing, as defined elsewhere. In addition, the Judge is permitted to dismiss the CFJ if e lacks sufficient information to make a determination of TRUE or FALSE. The Judge is required to make a reasonable effort to obtain all information necessary to make a decision before dismissing a CFJ for this reason. No CFJ shall be dismissed for any reason other than those specified in this or other Rules. If a CFJ is dismissed for a given reason, but upon Appeal that dismissal is set aside, then that CFJ shall not again be dismissed for that same reason. A Judge who does so commits an Infraction, the penalty for which is 3 Blots, to be reported by the Clerk of the Courts. History: Created by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 502/3 (Mutable, MI=1) Salary for Judges All judicial salaries shall be paid by transfer from the Bank at the end of the Nomic Week. The Clerk of the Courts shall, whenever a Player has earned a judicial salary, make a report of this fact in the Public Forum. At the end of the Nomic Week, all judicial salaries earned during that week, except as noted below, shall be paid; transfers arising from such payment are to be detected and reported by the Clerk of the Courts. The above notwithstanding, any judicial salary earned but not yet paid shall not be paid if the decision for which the salary was earned is currently subject to an appeal at the end of the Nomic Week in which it was earned. In this case, the salary shall be paid at the end of the Nomic Week in which the appeal is decided, and then only if the appeal upholds the original decision. If a decision is overturned in the same Nomic Week in which it was made, no salary shall be paid for the original decision. If a decision is not subject to an appeal at the end of the Nomic Week in which it is made, but is subsequently appealed in a later Nomic Week and overturned on appeal, the Player who made the original decision shall lose currency equal to the salary originally received for that decision. This shall be reported along with all other judicial salaries for that Nomic Week by the Clerk of the Courts. History: Created by Proposal 430, ca. Sep. 13 1993 Amended by Proposal 502, Sep. 30 1993 Amended(1) by Proposal 1501, Mar. 24 1995 Amended(2) by Proposal 1705, Sep. 4 1995 Amended(3) by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 663/3 (Mutable, MI=1) Injunctions--General Judges shall, in certain situations when specifically authorized by the Rules, have the power to issue orders requiring one or more Players to perform (or refrain from performing) one or more Actions. Such an order is called an Injunction. An Injunction, in order to be legally made, must: * specify the Player or Players to whom it applies and the Action or Actions that Player or Players are required to perform (or refrain from performing). * accompany the Judgement of a Call for Judgement, of which the Player issuing the Injunction is the Judge; and * be an Injunction issued in a situation where the Rules specifically permit the Judge an Injunction to restrain a Player or Players in the manner specified. An Injunction which does not meet these criteria, or which has otherwise been issued in a manner which is not consistent with the Rules, has no legal effect. A Judge issues an Injunction by transmitting it to the Clerk of the Courts simultaneously with the Judgement it accompanies. History: Created by Proposal 663, Nov. 2 1993 Amended(1) by Proposal 1487, Mar. 15 1995 Amended(2) by Proposal 1734, Oct. 15 1995 Amended(3) by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 1571/0 (Mutable, MI=1) Legal Force of Injunctions An Injunction has legal force at the moment the Injunction is published to the Public Forum, unless one of the following occurs within 72 hours of this publication: 1) An appeal of the Judgement the Injunction accompanies is initiated; or 2) An appeal challenging the validity of the Injunction is initiated. If either of these occurs, the Injunction instead takes legal effect upon the publication of the decision(s) of the Board(s) of Appeals which hears the appeal(s), and then only if the Board(s) sustains all matters which are appealed with respect to that CFJ. If either of the above occurs but not within 72 hours of the publication of the Injunction, the Injunction remains in force during the Appeal(s). If a Judgement which is accompanied by an Injunction is appealed and the Judgement is overturned upon Appeal, then the Injunction is set aside as of the time of the publication of the determination of the Appeals Board. History: Created by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 1573/0 (Mutable, MI=1) Penalties for Violations of Injunctions If an Injunction requires a Player to perform an Action, that Player must do so within 72 hours of when that Injunction takes effect, unless the Injunction is set aside prior to that time. A Player who fails to perform an Action required by an Injunction within 72 hours as required by this paragraph commits a Class C Crime. If an Injunction requires a Player to refrain from performing an Action, then that Player is forbidden from performing that action while the Injunction is in legal force. If the Player does perform the forbidden action, e commits a Class C Crime upon each such instance of performing the forbidden action. This Rule takes precedence over all other Rules pertaining to Injunctions. History: Created by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 789/2 (Mutable, MI=1) Injunctions on Interpretations of Rules When a player makes a CFJ alleging that a Rule should be interpreted in a certain way, e shall also submit a list of Rules relevant to that CFJ, which must include the Rule in question. If the statement is Judged TRUE, the Judge may include with the Judgement an Injuction requiring the Rulekeepor to annotate the Rule in question with the Statement in the CFJ and the list of relevant Rules. The annotation shall remain only until one of the Rules in the list of relevant Rules is changed in any way; or until a CFJ determines that the injunction no longer applies, as described below. While it remains, it shall guide the application of that Rule. If a Player believes that the circumstances which led to the Judgement no longer prevail and the annotation is therefore no longer applicable, e may submit a CFJ to that effect. If it is Judged TRUE, the annotation shall be stricken from the rule set. [CFJ 684: Such an Injunction applies not only during Judging, but also in the everyday interpretation of the Rule.] History: Created by Proposal 789, ca. Jan. 14 1994 Amended(1) by Proposal 1396, Jan. 29 1995 Amended(2) by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 1500/2 (Mutable, MI=1) Injunctions on the Interpretation of Compacts If a Call for Judgement alleges that a Statute or Warranty should be interpreted in a certain way, and the Caller of that CFJ has included a list of Rules, Statutes, and Warranties relevant to that CFJ (which must include the Statute or Warranty in question), and that CFJ has been Judged TRUE, the Judge of the CFJ is permitted to issue an Injunction ordering the Player responsible for maintaining that particular Statute or Warranty to annotate the Statute or Warranty in question with the Statement in the CFJ and the list of relevant Rules, Statutes, and Warranties. Such an annotation shall remain only until any of the Rules, Statutes, or Warranties in the list of relevant Rules, Statutes, or Warranties is changed in any way, or until removed by another Injunction. While it remains, it shall guide the application of that Statute or Warranty. If a Call for Judgement alleges that the circumstances which led to an annotation of a Statute or Warranty under this Rule no longer prevail, and that CFJ has been Judged TRUE, the Judge of that CFJ is required to issue an Injunction ordering the Player responsible for maintaining that particular Statute or Warranty to remove said annotation. History: Created by Proposal 1677, Aug. 22 1995 Amended(1) by Proposal 1760, Oct. 21 1995 Amended(2) by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 1365/3 (Mutable, MI=1) Concurring and Dissenting Opinions Upon the distribution of a legal judgement to the Nomic community, a Concurring or a Dissenting Opinion may be filed in written format with the Clerk of the Courts. The Concurring or Dissenting Opinion must satisfy the following criteria: (i) The opinion must be accompanied by reasons and arguments, which include, but are not necessarily limited to, citations of deciding Rules, past Judgement, and Agora Conventions. (ii) The opinion must be sponsored by at least two active Agora players and the sponsors must be listed on the opinion. (iii) The opinion must be filed with the Clerk of the Courts within 1 Nomic Week. (iv) The opinion must be entitled Concurring or Dissenting with the Judgement. Once an opinion satisfies these components, the Clerk of the Courts must distribute the opinion to all Players as soon as possible. Furthermore, all Concurring and Dissenting Opinions must be appended to the Legal Judgement as Concurring or Dissenting Opinions. History: Created by Proposal 1365, Jan. 5 1995 Amended(1) by Proposal 1644, Aug. 1 1995 Amended(2) by Proposal 1734, Oct. 15 1995 Amended(3) by Proposal 1754, Oct. 21 1995 ---------------------------------------- ======================================= Overturning Judgement This Category Includes Rules regulating the overturning of Judgements as well as the office of Justiciar. ---------------------------------------- Rule 911/5 (Mutable, MI=1) Appeals Whenever an Appeal is initiated, a Board of Appeals shall be constituted to consider the Appeal and to reach a determination. A Board of Appeals shall consist of three distinct Players, called Justices. The Clerk of the Courts shall select the Justices for each Board of Appeals as follows, until three eligible Justices have been selected. First, the Speaker shall be selected, if eligible. Then, the Justiciar shall be selected, if eligible. Then, the Clerk of the Courts shall be selected, if eligible. All remaining positions on the Board (if any) shall then be filled by the random selection of the Clerk of the Courts from amongst all those Players eligible to be selected, as described below. A Player who has already been selected to serve on a given Board of Appeal is not eligible to be selected a second time for that Board; this does not in any way affect that Player's eligibility to serve in the first position, however. If a Board of Appeals is considering a question pertaining to a CFJ, then a Player shall only be eligible to be selected to serve on that Board of Appeals if e was not a Judge of that CFJ, and is eligible to be selected as a Judge of that CFJ. However, if this restriction would result in there being fewer than three Players who are eligible to serve on that Board of Appeals, it shall not have any effect for that Board. If a Board of Appeals is considering a question that does not pertain to any one CFJ, then all Active Players (except those already selected) shall be eligible to be selected for that Board. If this would result in there being fewer than three Players who are eligible to serve on that Board of Appeals, then all Players, whether or not active, shall be eligible. History: Created by Proposal 384, Aug. 16 1993 Amended by Proposal 690, Nov. 11 1993 Amended by Proposal 911, May 4 1994 Amended by Rule 750, May 4 1994 Amended(1) by Proposal 1345, Nov. 29 1994 Amended(2) by Proposal 1487, Mar. 15 1995 Amended(3) by Proposal 1511, Mar. 24 1995 Amended(4) by Proposal 2457, Feb. 16 1996 Amended(5) by Proposal 2553, Mar. 22 1996 ---------------------------------------- Rule 910/4 (Mutable, MI=1) The Justiciar There shall exist the Office of the Justiciar, with the duty of Judging various matters of law, when the Rules so require. The Justiciar shall receive no fixed weekly salary. A Vacant Office of Justiciar shall be filled by an Election according to the standard procedure, except that: * the Nominating Period shall be three days; * the Vote Collector shall be the Registrar, or in eir absence the Speaker; and * the Speaker and the Clerk of the Courts are not permitted to be nominated. The Speaker and the Clerk of the Courts are prohibited from becoming the Justiciar. If the Player holding the Office of Justiciar becomes either Speaker or Clerk of the Courts, and thus is both Justiciar and either Speaker or Clerk of the Courts for a period of an entire week, e is removed as Justiciar and the Office becomes vacant. History: Created by Proposal 910, May 4 1994 Amended(1) by Proposal 1447, Feb. 21 1995 Amended(2) by Proposal 1511, Mar. 24 1995 Amended(3) by Proposal 1581, May 15 1995 Amended(4) by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 1570/0 (Mutable, MI=1) Announcement of Appeal The Clerk of the Courts shall make an announcement in the Public Forum as soon as possible after an Appeal has been initiated, including in eir announcement the matter of consideration of the Appeal and the identity of the Justices selected to serve on the Board of Appeals and which (if any) of these Players are ineligible to fill the positions to which they have been assigned. The Clerk shall also make an announcement to the Public Forum as soon as possible after any change in the identity of the Justices that takes place after the Board has been constituted. History: Created by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 1564/0 (Mutable, MI=1) Appeal of Judgement The Judgement returned by a Judge shall be subject to review by the Board of Appeals. Such an appeal shall be initiated upon the insistence of any three Players. The matter of consideration of such an appeal is whether or not the Judgement is correct. If the Board of Appeals determines that the Judgement was not correct, it shall then order one of the following: * that the Judgement be reversed, so that the CFJ becomes Judged according to the majority opinion of the Board of Appeals; or * that the Judgement be set aside, and further that the CFJ be dismissed; or * that the Judgement be set aside, and a new Judge selected to Judge it. If a majority of the Justices agree that the Judgement was in error, but cannot agree as to which of the above actions should be taken, the Judgement shall be set aside and a new Judge selected to Judge it. For the purpose of this Rule, insistence of a Player consists of that Player posting a message to the Public Forum stating that e insists. History: Created by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 1566/0 (Mutable, MI=1) Appeal of Dismissal The act of dismissing a CFJ shall be subject to review by the Board of Appeals. Such an appeal shall be initiated upon the insistence of any three Players. The matter of consideration of such an appeal is whether or not the dismissal was justified. If the Appeal determines that the dismissal was not justified, then the dismissal shall be set aside. If this happens, the Judge who dismissed the CFJ forfeits eir judicial Salary. For the purpose of this Rule, insistence of a Player consists of that Player posting a message to the Public Forum stating that e insists. History: Created by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 1572/0 (Mutable, MI=1) Appeal of Injunctions The act of making an Injunction shall be subject to review by the Board of Appeals. Such an appeal shall be initiated upon the insistence of any three Players, or upon the insistence of any single Player who is named in the Injunction. The matter of consideration of such an appeal is whether or not the Injunction has been made in accordance with the Rules. If the Appeal determines that the Injunction was not made in accordance with the Rules, then the Injunction shall be set aside, and the Judge who made the Injunction shall be penalized for an Infraction to be reported by the Clerk of the Courts and bearing a penalty of both 1 Blot and 5 Points. For the purpose of this Rule, insistence of a Player consists of that Player posting a message to the Public Forum stating that e insists. History: Created by Proposal 2457, Feb. 16 1996 ---------------------------------------- Rule 1447/4 (Mutable, MI=1) Final Judgement upon Appeal Once a Board of Appeals has been constituted upon a given question, the Justices shall consider the question amongst themselves. A Justice is permitted to, at any time, request that any other Player act in eir stead as Justice on a given Board of Appeals, provided that this second Player is both eligible to hold that position and consents to the assignment. A Justice who wishes to do this shall inform the Clerk of the Courts of this desire. Each Justice shall convey eir determination on the matter of the Appeal to the Clerk of the Courts before seven days have elapsed from the time e became a Justice on that Board of Appeals. If e fails to do so, e commits an Infraction, to be reported by the Clerk of the Courts and carrying a penalty of three Blots. E also becomes ineligible to serve on that Board of Appeals, and the Clerk of the Courts shall select a new Player according to the procedures for selecting Justices. A Justice shall either sustain or overturn the matter which is being considered. After all three Justices have submitted their determinations to the Clerk of the Courts, the Clerk shall post to the Public Forum these determinations along with any arguments, evidence, or other material the Justices have included with their determination. If a majority of the Justices agree to sustain the matter which is being considered, it is sustained; otherwise, it is overturned. The specific results of overturning a matter upon Appeal shall be determined by the Rules which permit an Appeal of that sort. All three Justices receive a Judicial Salary of 3 Points each upon the publication of their determinations and the outcome of the Appeal. History: Created by Proposal 1511, Mar. 24 1995 Amended(1) by Proposal 1656, Aug. 14 1995 Infected and Amended(2) by Rule 1454, Sep. 10 1995 Amended(3) by Proposal 2457, Feb. 16 1996 Amended(4) by Proposal 2553, Mar. 22 1996 ---------------------------------------- ======================================= Rule Violations This Category includes Rules describing actions to be taken concerning violations of the Rules. ---------------------------------------- Rule 908/6 (Mutable, MI=1) Formal Apologies If a Call for Judgement alleges that a Player (herein called the Ninny) has acted or has failed to act in such a way as to be in violation of one or more Rules, or to have committed one or more Crimes, and this CFJ is Judged TRUE, then the Ninny must submit to the Public Forum a Formal Apology within 72 hours of the publication of Judgement, unless that Judgement is successfully appealed within 72 hours. By a Formal Apology is meant a letter of at least 200 words, containing all of the Prescribed Words (if any were prescribed) explaining the Ninny's error, shame, remorse, and ardent desire for self-improvement. A Judge deciding TRUE in such a CFJ may issue an Injunction including a list of up to ten Prescribed Words of the Judge's choice, and ordering that the Ninny's Formal Apology must include the Prescribed Words. If the Ninny fails to meet these criteria e shall gain 3 Blots. The Player who called the initial CFJ has the duty to report to the Tabulator any Blots gained through this rule. This Rule defers to all other Rules which do not contain this sentence. History: Created by Proposal 781, ca. Dec. 20 1993 Amended by Proposal 908, May 4 1994 Amended by Rule 750, May 4 1994 Amended(1) by Proposal 1362, Dec. 13 1994 Amended(2) by Proposal 1382, Jan. 17 1995 Amended(3) by Proposal 1500, Mar. 24 1995 Amended(4) by Proposal 1734, Oct. 15 1995 Amended(5) by Proposal 2432, Jan. 30 1996 Infected and Amended(6) by Rule 1454, Apr. 1 1996 ---------------------------------------- ======================================= Crimes and Infractions This Category includes general Rules regarding Crimes and Infractions. ---------------------------------------- Rule 1503/0 (Mutable, MI=1) Crime: General Definition Whenever a Player performs an action which is designated by the Rules as a Crime, and further it has been determined by a CFJ that in fact that this action did take place and was in fact a Crime, then that Player shall be subject to the penalties for that Crime, as defined by the Rules. An action is a Crime only if there is a Rule which designates it to be a Crime. The fact that an action is prohibited by the Rules is not sufficient to make it a Crime. The designation of an action as a Crime does not in any way grant legal status to that action. A Rule which designates an action to be a Crime must also either specify an explicit penalty for committing that Crime, or designate that Crime to be one of several Classes of Crime defined elsewhere in the Rules. If a Rule designates an action to be a Crime, but does not either specify an explicit penalty or specify a valid Class of Crime, then that Crime shall not have any associated penalty. History: Created by Proposal 1682, Aug. 22 1995 ---------------------------------------- Rule 1504/0 (Mutable, MI=1) Application and Timing of Criminal Penalties All criminal penalties shall take effect 72 hours after the announcement of the Judge's Ruling in the CFJ which alleges the criminal act; however, if the CFJ is appealed prior to this time, then the penalty shall not be applied until immediately after the announcement of the ruling of the Appeals Court, and then only if the Judgement of the Appeals Court is also TRUE. If the CFJ is appealed, but not within 72 hours, and the Appeals Court judges differently than the Judge of the CFJ, then all penalties shall be reversed to the fullest extent possible at the time the Appeal Court's Judgement is announced. Responsibility for reporting all consequences of the application or reversal of a Criminal penalty falls unto the Clerk of the Courts, or, in eir absence, the Speaker. This includes, but is not limited to, reporting any Blot Awards or Currency Transfers to the Tabulator or the appropriate Recordkeepors. This Rule takes precedence over any Rule which requires another Player to report Score, Currency, or Blot changes which result from the commission of a Crime, or which causes Score, Currency, or Blots changes resulting from the commission of a Crime to take effect sooner than specified in this Rule. History: Created by Proposal 1682, Aug. 22 1995 ---------------------------------------- Rule 1505/1 (Mutable, MI=1) Standard Classes of Crimes The following Classes of Crime are defined, with the listed penalties: Class A Crime: The Player receives 20 Blots and loses 100 Points. Class B Crime: The Player receives 10 Blots and loses 50 Points. Class C Crime: The Player receives 4 Blots and loses 20 Points. Class D Crime: The Player receives 2 Blots and loses 10 Points. Class E Crime: The Player receives 1 Blot and loses 5 Points. Class 1 Crime: The Player receives 1 Blot. Class 2 Crime: The Player receives 2 Blots. Class 3 Crime: The Player receives 3 Blots. Class 4 Crime: The Player receives 4 Blots. History: Created by Proposal 1682, Aug. 22 1995 Amended by Proposal 2431, Jan. 30 1996 ---------------------------------------- Rule 1507/0 (Mutable, MI=1) Infractions: General Definition Whenever a Player performs an action which is designated by the Rules as a Infraction, that Player shall be subject to the penalties for that Infraction, as defined by the Rules. An action is a Infraction only if there is a Rule which designates it to be a Infraction. The fact that an action is prohibited by the Rules is not sufficient to make it a Infraction. The designation of an action as a Infraction neither grants nor denies legal status to that action. A Rule which designates an action to be a Infraction must specify an explicit penalty for committing that Infraction. If a Rule designates an action to be a Infraction, but does not specify an explicit penalty, then that Infraction shall not have any associated penalty. A Rule which designates an action to be an Infraction must specify the Officer who is to detect and report that Infraction, and only that Officer and the Speaker are authorized to detect and report that Infraction. A report of an Infraction by a Player other than the Officer mandated to report such Infractions or the Speaker has no legal effect. History: Created by Proposal 1690, Sep. 1 1995 ---------------------------------------- Rule 1508/1 (Mutable, MI=1) Application of Penalties for Infractions; Appeals Thereof All penalties for Infractions take effect at the time the first report of the Infraction is posted by the Player who reported it, provided that report was made by a Player who is legally authorized to make it. The determination of the reporting Player is legally binding until and unless it is reversed by a Call for Judgement. Any second or subsequent report of an Infraction has no legal effect. A Player who disagrees with the determination that an action was an Infraction is permitted to submit a Call for Judgement alleging that the action was not an Infraction. If the Officer's determination is reversed by CFJ, then the penalties shall be reversed 72 hours after the Judgement is announced, unless the CFJ is itself appealed during this time, in which case the penalties are reversed immediately upon the announcement of the ruling of the Appeals Court, and then only if the Appeals Court sustains the original Judgement. If the CFJ is appealed, but not within 72 hours, and the Appeals Court does not sustain the original Judgement, the penalties shall be reapplied upon the time the Appeal Courts' Judgement is announced. The responsibility for reporting all consequences of the application of a penalty falls unto the Player who makes the report of Infraction. The responsibility for reporting all consequences of the reversal or reapplication of a penalty as a result of the appeals process falls unto the Clerk of the Courts, or, in eir absence, the Speaker. This includes, but is not limited to, reporting any Blot Awards or Currency Transfers to the Tabulator or the appropriate Recordkeepors. Penalties for Infractions shall be limited to the loss of units of one or more Currencies, the award of one or more Blots, or both. This Rule takes precedence over any Rule which requires another Player to report Score, Currency, or Blot changes which result from the commission of a Infraction, or which causes Score, Currency, or Blots changes resulting from the commission of a Infraction to take effect sooner than specified in this Rule. History: Created by Proposal 1690, Sep. 1 1995 Amended(1) by Proposal 1754, Oct. 21 1995 ---------------------------------------- Rule 1509/2 (Mutable, MI=1) Judicial Recourse for Nonreporting of Infractions Any Player who believes that an Infraction has occurred, but which has not been reported by a Player authorized to report it, is permitted to make a Call for Judgement alleging thus. If the Judgement of the CFJ upholds the allegation, then the Judge of the CFJ shall be authorized to, and shall be obligated to, report the Infraction as provided by other Rules. This Rule takes precedence over any Rule which would prevent the Judge's report of an infraction from having legal effect. History: Created by Proposal 1690, Sep. 1 1995 Amended(1) by Proposal 1738, Oct. 15 1995 Amended(2) by Proposal 1754, Oct. 21 1995 ---------------------------------------- ======================================= The Distributor and the Assistant This Category includes Rules concerning the Offices of Distributor and Assistant. ---------------------------------------- Rule 796/2 (Mutable, MI=1) The Distributor There shall be an Office known as the Distributor. Whenever the Rules state that anything must be sent to all Players, they may instead be sent to the Distributor with some indication that they should be forwarded to all Players. The Distributor shall then send this message to all Players as soon as possible and in the order received. The first Distributor shall be Wes. This Rule shall take precedence over all Rules which require a Player to send something to all Players. History: Created by Proposal 510, Oct. 5 1993 Amended by Proposal 796, ca. Jan. 31 1994 Amended by Rule 750, ca. Jan. 31 1994 Amended(1) by Proposal 1754, Oct. 21 1995 Amended(2) by Proposal 2042, Dec. 11 1995 ---------------------------------------- Rule 514/0 (Mutable, MI=1) Keep the Distributor Informed of Your Address All Players shall notify the Distributor of their preferred email address(es). Should this address change, that Player shall notify the Distributor of this change. If a Player fails to notify the Distributor of a change of address, the Distributor shall not be responsible for any mail which did not reach that Player. History: Created by Proposal 514, Oct. 5 1993 ---------------------------------------- ======================================= The Registrar This Category includes Rules concerning the Office of Registrar. ---------------------------------------- Rule 559/6 (Mutable, MI=1) The Registrar There shall exist an Office called the Registrar. The Registrar's Salary is 4 Points. History: ... Amended(1) by Proposal 1325, Nov. 22 1994 Amended(2) by Proposal 1436, Feb. 21 1995 Amended(3) by Proposal 1660, Aug. 14 1995 Amended(4) by Proposal 1681, Aug. 22 1995 Amended(5) by Proposal 2451, Feb. 6 1996 Amended(6) by Proposal 2532, Mar. 10 1996 ---------------------------------------- Rule 676/4 (Mutable, MI=1) The Nomic Phone Books The Registrar shall maintain a list of all Registered Players, with their Nomic nickname, preferred email address, current On/Off Hold status, and the date the Player last Registered or went On or Off Hold. This list is known as the White Pages, and is part of the Registrar's Report. The Registrar shall maintain a list of all Offices and other official positions within Agora (such as Speaker), with the Nomic nickname of the holder of each position, and (in the case of Offices) when the last Election for that Office was and whether the Office is held temporarily. This list is known as the Blue Pages, and is part of the Registrar's Report. History: ... Amended(1) by Proposal 1315, Nov. 12 1994 Amended(2) by Proposal 1681, Aug. 22 1995 Amended(3) by Proposal 1739, Oct. 15 1995 Amended(4) by Proposal 2532, Mar. 10 1996 ---------------------------------------- Rule 1502/2 (Mutable, MI=1) The Registrar's Report There is a set of information known as the Registrar's Report. It consists of all the information that the Rules say is part of the Registrar's Report. At least once every Nomic Week the Registrar shall post the Registrar's Report to the Public Forum. A Registrar that fails to do so commits a Class C Crime. History: Created by Proposal 1681, Aug. 22 1995 Amended(1) by Proposal 2038, Dec. 4 1995 Amended(2) by Proposal 2532, Mar. 10 1996 ---------------------------------------- Rule 1494/1 (Mutable, MI=1) Establish the Welcome Wagon The Registrar, in consultation with the Speaker, shall develop and maintain a Welcome Message, welcoming a new player to Agora Nomic, explaining any subscriptions required to receive the Public Forum, how to obtain a current ruleset, and any other information, advice, and gossip as the Registrar sees fit. The Registrar shall send a copy of the Welcome Message to any Player who Registers for the first time, within a week of such Registration. History: Created by Proposal 1655, Aug. 14 1995 Amended(1) by Proposal 1703, Sep. 1 1995 ---------------------------------------- ======================================= The Rulekeepor and Archivist This Category includes Rules concerning the Offices of Rulekeepor and Archivist, as well as Rules regulating the Logical Ruleset and Rule Titles ---------------------------------------- Rule 1051/3 (Mutable, MI=1) The Office of the Rulekeepor Let there be an Officer known as the Rulekeepor. The Rulekeepor shall maintain a complete list of the current Rules, and post this list to all Players at least once a week. The Rulekeepor shall receive a weekly Salary of 5 Points. History: ... Amended(1) by Proposal 1735, Oct. 15 1995 Amended(2) by Proposal 2042, Dec. 11 1995 Amended(3) by Proposal 2048, Dec. 19 1995 ---------------------------------------- Rule 1048/3 (Mutable, MI=1) The Logical Ruleset The mandated weekly posting of the Ruleset shall be done in the "Logical Rule Set Format". In this format, each Rule is assigned to a principal Category, and the Rules are grouped according to their Category. Within a Category, the ordering of Rules is decided by the Rulekeepor. All existing Rule Categories must be listed, along with a brief description, whether or not any Rules currently are assigned to the Category. Whenever a new Rule is added, it is assigned to the most appropriate Category in the opinion of the Rulekeepor, who must choose from existing Categories. Alternatively, the Rulekeepor may create a new Rule Category and assign the Rule to this new Category, if this is permitted by other Rules. Once e assigns a Rule to a Category, e may not change it except as provided by other Rules. However, if the Proposal itself stipulates a specific Category, as provided for by other Rules, the Rulekeepor is required to abide by this, if it is a valid defined Category. Also, a Rule's Category may be changed by a type of Proposal defined in other Rules. History: ... Amended(1) by Proposal 1561, Apr. 17 1995 Amended(2) by Proposal 1754, Oct. 21 1995 Amended(3) by Proposal 2538, Mar. 13 1996 ---------------------------------------- Rule 1054/2 (Mutable, MI=1) Changing the Category of a Rule The assigned Category of an existing Rule may be changed by means of a Directive to change the Category of that Rule. Such a Directive shall clearly state the Rule whose Category is to be changed, its old Category, and its proposed new Category. History: ... Amended(1) by Proposal 1332, Nov. 22 1994 Amended(2) by Proposal 1740, Oct. 15 1995 ---------------------------------------- Rule 1052/2 (Mutable, MI=1) Creating New Rule Categories New Rule Categories may be created by means of a Directive to create the new Category. Such a Directive shall clearly state the name of the Category to be created. The Rulekeepor shall include all existing Categories in the publication of the Logical Rule Set, even if a given Category contains no Rules. History: Created by Proposal 1052, Sep. 20 1994 Amended(1) by Proposal 1331, Nov. 22 1994 Amended(2) by Proposal 1740, Oct. 15 1995 ---------------------------------------- Rule 1452/0 (Mutable, MI=1) Rulekeepor May Create New Categories The Rulekeepor is given the authority to define a new Rule Category in the following specific situation: If the Category is not specified in a Proposal to Create a Rule, AND in the Rulekeepor's estimation none of the existing Rule Categories is appropriate, then the Rulekeepor may unilaterally define and create a new Category and assign the new Rule to this Category. The Rulekeepor must announce the creation of the new Category to the Public Forum no later than the publication of the first Rule Set which uses the new Category. The announcement may be in the same message as the Rule Set itself. History: Created by Proposal 1561, Apr. 17 1995 ---------------------------------------- Rule 1524/1 (Mutable, MI=1) Directive to Change the Name of a Category The name of a Rule Category may be changed by means of a Directive to change the name of a Rule Category. The Directive must explicitly state both the current name of the Category and the proposed new name. If a Proposal containing such a Directive is adopted, it has the effect of changing the name of the Rule Category in the manner specified. History: Created by Proposal 1730, Oct. 10 1995 Amended(1) by Proposal 1788, Nov. 13 1995 ---------------------------------------- Rule 1416/1 (Mutable, MI=1) Deletion of Rule Categories An empty Rule Category may be removed by the Rulekeepor as e sees fit. History: Created by Proposal 1416, Feb. 1 1995 Amended(1) by Proposal 1740, Oct. 15 1995 ---------------------------------------- Rule 1485/4 (Mutable, MI=1) Titles For Rules All Rules have a Title, which is a single line of text containing not more than 60 characters. The Title must be listed by the Rulekeepor along with the Rule. However, they are not part of the Rule itself and have no effect on the application of the Rule, being merely a convenience for the Players. Titles, once assigned, may not be altered except as specified in this and other Rules. For a new Rule created as a result of a Rule Change Proposal: If the Rule Change Proposal specifies the Title within the body of the Proposal, that Title is assigned. Otherwise the Rulekeepor chooses a Title. For a new Rule created by other means: If the procedure which caused the Rule to be created specifies a way to determine the Title, then that Title is assigned. Otherwise, the Rulekeepor chooses a Title. To change the Title of an existing Rule: A Rule's Title may be changed by a Directive. The Directive must unambiguously state the number of the Rule and the new Title. Titles for old Rules with no Titles: If a Rule has no Title, because it was created at a time when this Rule did not apply, the Rulekeepor shall choose a Title for that Rule. History: Created by Proposal 1634, Jul. 25 1995 Amended(1) by Proposal 1668, Aug. 18 1995 Amended(2) by Proposal 1673, Aug. 22 1995 Amended(3) by Proposal 1740, Oct. 15 1995 Amended(4) by Proposal 1754, Oct. 21 1995 ---------------------------------------- Rule 1430/0 (Mutable, MI=1) Mandatory Rule Annotations Whenever a Rule is changed in any way, the Rulekeepor shall attach to the Rule an annotation giving the type of change, the source of the Change (that is, the Number of the Proposal or Rule which contained the Change), and the date upon which the change took effect. Other Rules may require additional information to appear in an annotation for certain types of Rule Change. Such an annotation does not in any way affect the Rule itself, is not part of the text of the Rule, and is not a Rule Change in its own regard. The Rulekeepor shall indicate all annotations in such a way that they are readily distinguished from the text of the Rule. When a Rule is repealed, all annotations attached to it are discarded, and need not appear in the published Ruleset. History: Created by Proposal 1430, Feb. 7 1995 ---------------------------------------- Rule 417/6 (Mutable, MI=1) The Nomic Archivist Let there be an office known as the Nomic Archivist, which shall be governed by the default Rules concerning Offices. The duties of the Archivist shall be as follows: * to record the passage and failure of Proposals, * to maintain the Historical Ruleset, a document which includes all rules ever to exist as part of the Agora Ruleset, annotated with the periods of time they were in effect, and what Proposals or Rules enacted them. * to maintain a list of Judgements and their case histories, * to maintain copies of prior Officer reports, and * to maintain a list of game Winners in past games. The Archivist is free to comment on the historical records as e sees fit, but such commentary must be clearly delimited from the historical material. The Archivist is free to design a classification method for the material e stores. The "historical record" of the Ruleset maintained by the Archivist is one that includes all rules ever part of the Agora Ruleset, annotated with information as to their ultimate fate, whether Repealed or Amended etc. This record of the Ruleset has no legal force. The salary of the Archivist shall be 5 points. This Rule defers to all other Rules which do not contain this sentence. History: ... Amended(1) by Proposal 1302, Nov. 4 1994 Amended(2) by Proposal 1700, Sep. 1 1995 Amended(3) by Proposal 1735, Oct. 15 1995 Amended(4) by Proposal 1741, Oct. 15 1995 Amended(5) by Proposal 2029, Nov. 28 1995 Infected and Amended(6) by Rule 1454, Jan. 23 1996 ---------------------------------------- ======================================= Patent Titles This Category includes Rules regulating Patent Titles. ---------------------------------------- Rule 649/3 (Mutable, MI=1) Patent Titles Let there be a Nomic Entity known as a Patent Title. A Player may nominate a person for a Patent Title by means of a Directive awarding the Title to that Person. Such a Directive must clearly specify the Patent Title, and the person to whom it is to be awarded. A Proposal containing a Directive to Award a Patent Title must have an Adoption Index of at least 1. If the Directive is adopted, the person in question shall be known to all Players by that Patent Title. If the Directive fails, that person may not be nominated for the same Patent Title for a period of 4 weeks. If the Rule which creates the Patent Title specifies another method of assigning the Patent Title, then that Rule shall take precedence over this Rule. The Registrar shall maintain a list of all Patent Titles that have been awarded, and to whom they have been awarded. This list is known as the Gold Pages, and is part of the Registrar's Report. History: ... Amended(1) by Proposal 1334, Nov. 22 1994 Amended(2) by Proposal 1681, Aug. 22 1995 Amended(3) by Proposal 2532, Mar. 10 1996 ---------------------------------------- Rule 1044/4 (Mutable, MI=1) Unique Patent Titles There shall be a subset of Patent Titles known as Unique Patent Titles. A Unique Patent Title is awarded to a single person, at the same time as the creation of the Unique Patent Title; no other person may ever hold that Patent Title. A Unique Patent Title is created and awarded by a Directive to award the Unique Patent Title to the specified Player. Such a Directive shall clearly state the Unique Patent Title to be awarded, that said Title is Unique, and the person who shall receive the Unique Title. The Registrar shall maintain a list of all Unique Patent Titles as part of the Gold Pages. History: ... Amended(1) by Proposal 1335, Nov. 22 1994 Amended(2) by Proposal 1681, Aug. 22 1995 Amended(3) by Proposal 2399, Jan. 20 1996 Amended(4) by Proposal 2532, Mar. 10 1996 ---------------------------------------- Rule 651/0 (Mutable, MI=1) Heroes Let there be the Patent Title known as Hero, which shall be given to those persons who gave outstanding service to eNomic, but who are no longer Players or who never were Players. No Player may hold the Patent Title of Hero. ---------------------------------------- Rule 840/6 (Mutable, MI=1) The Scamster Let there be a Patent Title known as the "Scamster". This is awarded to a Player who has shown great enthusiasm, persistence, or skill in the perpetrating of Scams. This Title is awarded in the normal manner for Patent Titles, and may never be retracted. At the time the Title is awarded, 1 Mark shall be transferred from the new Scamster to the Bank. This transfer shall be reported by the Registrar, as soon as possible after it occurs. The Patent Title of Scamster may not be declined. History: ... Amended(1) by Proposal 1346, Nov. 29 1994 Amended(2) by Proposal 1372, Jan. 5 1995 Amended(3) by Proposal 1688, Sep. 1 1995 Amended(4) by Proposal 1716, Sep. 12 1995 Amended(5) by Proposal 1754, Oct. 21 1995 Amended(6) by Proposal 2494, Feb. 16 1996 ---------------------------------------- Rule 1047/3 (Mutable, MI=1) Patent Title of Zeitgeist When a Proposal made by some Player is adopted unanimously (that is, no votes are cast AGAINST it), and the Proposer of that Proposal is a Player, then that Proposal's Proposer is awarded the Patent Title of Zeitgeist. All current holders of the Title of Zeitgeist lose the Title whenever it is newly awarded. The Assessor is responsible for detecting the award of this Title and reporting it to the Registrar. When a Player is awarded the Patent Title of Zeitgeist, one Extra Vote is transferred to that Player from the Bank. The Assessor is responsible for detecting and reporting this transfer. [CFJs 745 & 747: A Proposal passes unanimously if there are no Votes AGAINST, even if there are some ABSTAIN votes.] History: Created by Proposal 1047, Sep. 20 1994. Amended(1) by Proposal 1707, Sep. 4 1995 Amended(2) by Proposal 2486, Feb. 16 1996 Amended(3) by Proposal 2522, Mar. 10 1996 ---------------------------------------- ======================================= Degrees and Theses This Category includes Rules concerning Theses and that subset of Patent Titles known as Degrees. ---------------------------------------- Rule 1367/1 (Mutable, MI=1) Degrees There shall exist a subset of the Patent Titles known as Degrees. A Patent Title is only a Degree if it is specifically made such by a Rule. A person may use a Degree with their name for any official or unofficial business if and only if that person currently possesses that Degree. Persons may come to possess Degrees only as specified in the Rules. Once a person possesses a Degree, e shall keep that Degree forever. The Registrar shall note in eir report which persons possess which Degrees. This Rule takes precedence over any Rule specifying default properties of Patent Titles. This Rule defers to all other Rules which do not contain this sentence. History: Created by Proposal 1367, Jan. 5 1995 Infected and Amended(1) by Rule 1454, Feb. 12 1996 ---------------------------------------- Rule 1368/0 (Mutable, MI=1) The Legal Degrees The following Degrees are hereby made legal: - Associate of Nomic (A.N.) - Bachelor of Nomic (B.N.) - Master of Nomic (M.N.) - Doctor of Nomic Philosophy (D.N.Phil) Degrees shall be ranked in the order they appear in this Rule, with Degrees listed latest in the Rule being ranked higher than Degrees listed earlier. The abbreviations in parenthesis are not part of the actual Degree. History: Created by Proposal 1368, Jan. 5 1995 ---------------------------------------- Rule 1369/0 (Mutable, MI=1) Theses There shall be a Nomic Entity known as a Thesis, plural Theses. A Thesis shall be an essay whose topic is any facet of Agora Nomic, or Nomic in general. The topic should be substantially different from all other Theses previously approved, but this is not a requirement. History: Created by Proposal 1369, Jan. 5 1995 ---------------------------------------- Rule 1370/4 (Mutable, MI=1) How To Get A Degree There shall be a legal Directive to Request a Degree. A Directive to Request a Degree must specify the intended recipient of the Degree and the Degree being Requested and include any texts necessary to the awarding of that Degree. A person shall receive a Degree if and only if the conditions specified in this Rule are met. The following conditions are a prerequisite to the awarding of a Degree to a person (referred to here as Person X): - A Proposal to Request a Degree is submitted specifying Person X as the intended recipient of the Degree. - Only the Degree specified in the Proposal may be awarded to Person X. - Person X sends a message to the Public Forum containing a Thesis authored by Person X and a statement explicitly associating the Thesis with the Proposal to Request a Degree. The Archivist shall be responsible for keeping a copy of each Thesis written in this manner. - Person X does not decline the Degree. (To decline the Degree, e states such in a message to the Public Forum.) The following are additional requirements for the awarding of individual Degrees. To receive the Degree Bachelor of Nomic: - The Thesis in the Proposal to Request a Degree must be at least 500 words. To receive the Degree Master of Nomic: - The minimum Adoption Index necessary for such a Directive to take effect is 2. - The Thesis in the Proposal to Request a Degree must be at least 500 words. To receive the Degree Doctor of Nomic Philosophy: - The minimum Adoption Index necessary for such a Directive to take effect is 3. - The Thesis in the Proposal to Request a Degree must be at least 500 words. - The Proposal to Request a Degree must clearly identify a creative work, which has been published in the Public Forum, and whose topic or theme is any concept related to Agora or Nomic in general. The author of this work must be Person X. History: Created by Proposal 1370, Jan. 5 1995 Amended(1) by Proposal 1508, Mar. 24 1995 Amended(2) by Proposal 1754, Oct. 21 1995 Amended(3) by Proposal 2399, Jan. 20 1996 Amended(4) by Proposal 2487, Feb. 16 1996 ---------------------------------------- ======================================= Currencies This Category includes Rules concerning Currencies in general. ---------------------------------------- Rule 1467/2 (Mutable, MI=1) Definition of a Currency There are certain entities which are Currencies. An entity is a Currency if and only if it has been made such by the Rules, and if and only if it complies with all the requirements in the Rules pertaining to Currencies. Neither Currencies nor units of Currency shall be created or destroyed except as specified by the Rules. History: Created by Proposal 1601, Jun. 19 1995 Amended(1) by Proposal 1685, Sep. 1 1995 Amended(2) by Proposal 2470, Feb. 16 1996 ---------------------------------------- Rule 1576/0 (Mutable, MI=1) Names of Currencies Each Currency shall have a name, which must be distinct from the name of every other Currency. Any attempt to create a Currency with the same name as an already existing Currency fails. History: Created by Proposal 2470, Feb. 16 1996 ---------------------------------------- Rule 1468/1 (Mutable, MI=1) Definition of a Treasury A Treasury is a repository for holding Currencies. A Treasury is permitted to contain any quantity of Currencies in any combination, unless otherwise restricted by some other Rule. Every unit of every Currency always resides in some Treasury. Units of Currency shall only be placed into, removed from, or transferred between, Treasuries as permitted by the Rules. The possession of Treasuries is limited to those entities authorized by the Rules to possess them. No entity shall possess more than one Treasury; no Treasury shall be possessed by more than one entity. Treasuries shall not be transferred. It shall always be a permissible and unambiguous abbreviation to state that an entity in possession of a Treasury possesses the Currencies within that Treasury. [CFJ 802: If an Entity ceases to exist, its Treasury does too. CFJ 855: Currency Holdings are limited to real numbers.] History: Created by Proposal 1601, Jun. 19 1995 Amended(1) by Proposal 2496, Mar. 3 1996 ---------------------------------------- Rule 1469/3 (Mutable, MI=1) Creation and Destruction of Treasuries Treasuries shall only be created or destroyed when required by the Rules. When a Treasury is created, it contains no units of any Currency. When a Treasury is destroyed, all units of Currency within it are transferred to the Treasuries of the Mintors of the respective Currencies, to the extent permitted by the Rules. Any untransferrable Currencies are instead destroyed. The Recordkeepors of each individual Currency are required to detect and report transfers of that Currency which occur as a result of this Rule. History: Created by Proposal 1601, Jun. 19 1995 Amended(1) by Proposal 1698, Sep. 1 1995 Amended(2) by Proposal 1705, Sep. 4 1995 Amended(3) by Proposal 2496, Mar. 3 1996 ---------------------------------------- Rule 1601/0 (Mutable, MI=1) Automatic Creation and Destruction of Treasuries Whenever an entity which is authorized to possess a Treasury is created, or an existing entity is granted the authority to possess a Treasury, a Treasury is created for that entity. Whenever an entity which possesses a Treasury is destroyed or ceases to have the authority to possess a Treasury, its Treasury is destroyed. History: Created by Proposal 2496, Mar. 3 1996 ---------------------------------------- Rule 1478/1 (Mutable, MI=1) Executors The Rules may, for any given non-Player Nomic Entity, specify a Player, or the means to designate a Player, who shall act as the Executor of that Entity. The Executor of a non-Player Nomic Entity shall have the legal authority to act on behalf of that Entity, as if e were that Entity. The Rules may also specify constraints on how the Executor of an Entity may act. If a non-Player Nomic Entity has no Executor, it may not act except as specifically required of it by the Rules. The Executor of a Group is that Group's Vizier. For the sake of completeness, a Player is eir own Executor. Whenever a Player is acting on behalf of some Entity of which e is the Executor, e must make it clear that e is doing so. If such a Player fails to clearly indicate that e is acting as the Executor of some other Entity, it shall be presumed that e is acting on eir own behalf. History: Created by Proposal 1601, Jun. 19 1995 Amended(1) by Proposal 2514, Mar. 3 1996 ---------------------------------------- Rule 1577/1 (Mutable, MI=1) Minimum Unit Quantities (MUQ) Each Currency shall have associated with it a Minimum Unit Quantity (MUQ). This quantity is the smallest amount of that Currency which is permitted to be transferred. All transfers, holdings, and calculations involving a given Currency shall be rounded off to the nearest multiple of its MUQ. The MUQ of a given Currency is 1 if no other specification exists. This Rule defers to all other Rules which do not contain this sentence. History: Created by Proposal 2470, Feb. 16 1996 Infected and Amended(1) by Rule 1454, Mar. 24 1996 ---------------------------------------- Rule 1578/0 (Mutable, MI=1) Currency Recordkeepors Each Currency shall have associated with it a Recordkeepor, which must be a Player. The Recordkeepor of a Currency is required to maintain a record of the amounts of that Currency held in the various Treasuries which exist. If the designated Recordkeepor of a Currency ceases to be a Player, the Banker (or, in the absence of a Banker, the Speaker) shall fulfill that responsibilty until a new Recordkeepor is selected according to whatever procedure applies. If there is no procedure defined for selecting a new Recordkeepor, then all units of that Currency are destroyed and the Currency ceases to exist. History: Created by Proposal 2470, Feb. 16 1996 ---------------------------------------- Rule 1579/0 (Mutable, MI=1) Mintors Each Currency shall have associated with it a Mintor, which must be an entity to which the Rules grant Mint Authority. An entity has Mint Authority if and only if the Rules grant it such. If the designated Mintor of a Currency ceases to exist or ceases to possess Mint Authority, all units of that Currency are destroyed and the Currency ceases to exist. The Mintor of a given Currency is the Mint if no other specification exists. History: Created by Proposal 2470, Feb. 16 1996 ---------------------------------------- Rule 1471/0 (Mutable, MI=1) Creation and Destruction of Currencies The Mintor of a Currency may, at any time, create new units of that Currency, so long as this creation is permitted by the Rules. These newly-created units of Currency are placed in the Treasury of the Mintor. Units of Currency may not otherwise be created except as specifically authorized by the Rules. The Mintor of a Currency may, at any time, destroy those units of that Currency which it currently possesses in its Treasury, so long as this destruction is permitted by the Rules. Units of Currency may not be otherwise destroyed except as specifically authorized by the Rules. If the Mintor of a Currency ceases to exist, or ceases to have the authority to be a Mintor, then all units of that Currency are immediately destroyed, and Currency ceases to exist. The Mintor of the Currency shall notify the Recordkeepor of the Currency as soon as possible after it creates or destroys Units of Currency. A Mintor must have a Treasury. History: Created by Proposal 1601, Jun. 19 1995 ---------------------------------------- Rule 1472/3 (Mutable, MI=1) Transfer of Currencies Units of Currency are transferrable between Treasuries under the following conditions: a) The transfer shall be from exactly one Treasury to exactly one other Treasury. b) The transfer must be of a positive amount of exactly one Currency, and that amount must be an exact integral multiple of that Currency's MUQ. c) Some Rule must authorize the transfer, either by requiring it directly or by granting authority to require the transfer to some other entity. d) Some Rule must specify a Player whose duty it is to report the occurence of the transfer to the Recordkeepor of the Currency involved. This Rule takes precedence over any Rule which would permit or require a transfer prohibited by this Rule, and defers to any Rule which prohibits a transfer permitted by this Rule. [CFJ 793: Notification may take place as part of an Official Report to the Public Forum.] History: Created by Proposal 1601, Jun. 19 1995 Amended(1) by Proposal 1649, Aug. 1 1995 Amended(2) by Proposal 1702, Sep. 1 1995 Amended(3) by Proposal 2493, Feb. 16 1996 ---------------------------------------- Rule 1599/0 (Mutable, MI=1) Requirement to Report Currency Transfers When a Rule requires a Player to report a Currency transfer to the Recordkeepor of a Currency, that Player is required to do so within seven days. The failure to do so is an Infraction, the penalty for which is 1 Blot, which shall be reported by the Recordkeepor of the Currency involved. The failure to report a Currency transfer as required by the Rules does not in any way deprive the transfer of legal force. This Rule defers to any Rule which specifies a different time limit for reporting a certain transfer or class of transfers. History: Created by Proposal 2493, Feb. 16 1996 ---------------------------------------- Rule 1596/0 (Mutable, MI=1) Currency Transfers Mandated by the Rules Whenever a Rule directly requires a transfer of Currencies to take place, the transfer takes place as required by that Rule, provided that the transfer is otherwise permitted by the Rules. Such a transfer takes place at the time specified in the Rule which requires the transfer, or, if no time is specified, at the time when the Rule first begins to require the transfer. History: Created by Proposal 2493, Feb. 16 1996 ---------------------------------------- Rule 1597/0 (Mutable, MI=1) Currency Transfers Mandated by Non-Rule Entities Whenever an Entity other than a Player to which the Rules have granted the authority to require Currency transfers directly requires a transfer of Currencies to take place, the transfer takes place as required by that Entity, provided that: a) the transfer would not result in the Treasury being transferred from containing a negative quantity of the Currency transferred, and b) the transfer is otherwise permitted by the Rules. Such a transfer takes place at the time specified by the Entity which requires the transfer, or, if no time is specified, at the time when the Entity first begins to require the transfer. This Rule takes precedence over any Rule which would permit or require a transfer prohibited by this Rule. History: Created by Proposal 2493, Feb. 16 1996 ---------------------------------------- Rule 1598/0 (Mutable, MI=1) Currency Transfers Mandated by Players Any Player is permitted to require a transfer of Currency to take place, provided that: a) the transfer would not result in the Treasury from which the Currency is being transferred containing a negative quantity of the Currency being transferred, b) the Player requiring the transfer is the Executor of the Owner of the Treasury from which the Currency is being transferred, c) the Player requiring the transfer reports the transfer to the Recordkeepor of the Currency transferred, and d) the transfer is otherwise permitted by the Rules. Such a transfer takes place at the time the Player requiring it reports it to the Recordkeepor of the Currency transferred. This Rule takes precedence over any Rule which would permit or require a transfer prohibited by this Rule. History: Created by Proposal 2493, Feb. 16 1996 ---------------------------------------- Rule 1466/4 (Mutable, MI=1) Currency Directives There is a type of Directive, called a Currency Directive. If adopted, they have the effect of specifying the Currency holdings contained in an Entity or Entities' Treasury or Treasuries. They may have no other effects. The AI of a Proposal which contains such a Directive shall be at least 1. [CFJ 781: Such Directives specify the Currency Holdings only at the instant they are adopted.] History: Created by Proposal 1596, Jun. 2 1995 Amended(1) by Proposal 1637, Jul. 25 1995 Null-amended(2) by Proposal 1640, Aug. 1 1995 Amended(3) by Proposal 1669, Aug. 18 1995 Amended(4) by Proposal 2293, Dec. 29 1995 ---------------------------------------- ======================================= The Scorekeepor and Points This Category includes Rules concerning the Office of Scorekeepor, the recordkeeping of Scores, and miscellaneous Rules regulating point changes. (I.e. a Rule specifying a point change goes here only if no other Category is appropriate.) ---------------------------------------- Rule 901/3 (Mutable, MI=1) The Scorekeepor There shall be an Office called the Scorekeepor. The Scorekeepor shall, in addition to eir other duties, detect and report as soon as possible whenever a Player has Won the Game due to a Win by Points. The Salary of the Scorekeepor shall be 5 Points per Week. History: ... Amended(1) by Proposal 1328, Nov. 22 1994 Amended(2) by Proposal 1601, Jun. 19 1995 Null-Amended(3) by Proposal 2442, Feb. 6 1996 ---------------------------------------- Rule 1475/0 (Mutable, MI=1) Points Points are a Currency. The MUQ of Points is 0.1. The Recordkeepor for Points is the Scorekeepor, or, in eir absence, the Speaker. The Mintor for Points is the Mint. The Scorekeepor shall post at least once every Nomic Week an Official Report to the Public Forum detailing the number of Points held in every Treasury, and the changes thereof since at least the last such report. All transfers involving Points shall be reported to the Public Forum. This takes precedence over any Rule which might not require, or which might prohibit, the reporting of a transfer to the Public Forum. History: Created by Proposal 1601, Jun. 19 1995 ---------------------------------------- Rule 1511/0 (Mutable, MI=1) Limitations on Point Ownership and Transfer A transfer of Points is legal only if the transfer is from the Bank and to a Player's Treasury, if it is from a Player's Treasury and to the Bank, or if the transfer is of the sort specifically required by this Rule. All other transfers of Points are illegal. If, for any reason, an Treasury belonging to an entity which is neither the Mint nor a Player contains a non-zero number of Points, all the Points in that Treasury shall be immediately transferred to the Bank, and a commensurate number of Marks computed using the primary Mark Exchange Rate shall be transferred from the Bank to that Treasury. Such transfers shall be detected and reported by the Scorekeepor. This Rule takes precedence over all other Rules which determine the legality of Currency transfers. History: Created by Proposal 1691, Sep. 1 1995 ---------------------------------------- Rule 726/4 (Mutable, MI=1) Starting Points When a new Player enters the Game, e shall receive from the Bank a number of Points equal to the median of the number of Points held by all Active Players. The Scorekeepor shall detect and report all transfers which occur under this Rule. History: ... Amended(1) by Proposal 1601, Jun. 19 1995 Infected and amended(2) by Rule 1454, Aug. 14 1995 Amended(3) by Proposal 1679, Aug. 22 1995 Amended(4) by Proposal 1705, Sep. 4 1995 ---------------------------------------- ======================================= Marks and the Banker This Category includes Rules concerning the Currency of Marks and the Office of Banker, as well as the Mint and the Bank. ---------------------------------------- Rule 1548/1 (Mutable, MI=1) The Banker Let there be an Office called the Banker. The Banker has a weekly salary of 5 points. The Banker shall maintain a record of all existing Currencies and their respective MUQs, Recordkeepors, and Mintors. History: Created by Proposal 2039, Dec. 4 1995 Amended(1) by Proposal 2470, Feb. 16 1996 ---------------------------------------- Rule 1470/1 (Mutable, MI=1) The Mint and the Bank There shall exist a Nomic Entity called the Mint. The Mint shall have a Treasury known as the Bank. The Mint may never transfer Currencies from its Treasury, or create or destroy any of the Currencies of which it is the Mintor, except as specifically authorized to do so in the Rules. The Mint shall not have an Executor. The Mint has Mint Authority. History: Created by Proposal 1601, Jun. 19 1995 Amended(1) by Proposal 2470, Feb. 16 1996 ---------------------------------------- Rule 1473/0 (Mutable, MI=1) Marks Marks are a Currency. The MUQ of Marks is 0.01. The Recordkeepor for Marks is the Banker, or, in eir absence, the Speaker. The Mintor for Marks is the Mint. The Banker shall post at least once every Nomic Week an Official Report to the Public Forum detailing the number of Marks held in every Treasury, and the changes thereof since at least the last such report. History: Created by Proposal 1601, Jun. 19 1995 ---------------------------------------- Rule 1608/0 (Mutable, MI=1) The Mil A Mil is a variable quantity of Marks. The 'ideal value' of the Mil is equal to one thousandth of all the Marks in existence which were not held by the Bank at the beginning of the current game. However, negative quantities of Marks do not exist for the purposes of this Rule. The 'posted value' of the Mil is the value of the Mil last posted by the Banker. The 'actual value' or 'legal value' of the Mil is the value of the Mil used for the purposes of calculating the sizes of various transfers made in Mil, and it is always equal to the last posted value of the Mil to become the actual value. A posted value of the Mil only becomes the actual value as specified in this Rule. As soon as possible after the legal and correct announcement that a Game has ended, the Banker shall calculate the ideal value of the Mil and post the result of eir calculation to the Public Forum. If the Banker's calculation of the ideal value of the Mil remains unchalleged by COE or CFJ for 72 hours after it is published, then the posted value of the Mil becomes the actual value, as of the end of the 72 hour period. If the posted value of the Mil is challenged by COE or CFJ within 72 hours of its publication, then the actual value of the Mil shall then be determined according to the following provisions: If it is determined as a result of the COE or CFJ that the posted value of the Mil differs from the ideal value by less than or equal to 5% of the ideal value, then the posted value of the Mil becomes the actual value. If it is determined as a result of the COE or CFJ that the posted value of the Mil differs from the ideal value by greater than 5% of the ideal value, the Banker shall, within 72 hours, recalculate the ideal value of the Mil and post the result of eir calculation to the Public Forum. This new posted value is subject to all the conditions set out in this Rule for a posted value of the Mil to become the actual value. History: Created by Proposal 2523, Mar. 10 1996 Amended(1) by Rule 1608, Mar. 15 1996 ---------------------------------------- Rule 1510/0 (Mutable, MI=1) Mark Exchange Rates There shall be two Mark Exchange Rates: the primary exchange rate, which shall apply for most voluntary and involuntary trades of Points for Marks; and the secondary exchange rate, which shall apply when Points are automatically exchanged for Marks at the end of a Game. All Mark Exchange Rates shall be applicable to any quantity of Currency, within MUQ limits. The primary Mark Exchange Rate shall be 1 Point to 1 Mark. The secondary Mark Exchange Rate shall be 1.5 Points to 1 Mark. History: Created by Proposal 1691, Sep. 1 1995 ---------------------------------------- Rule 1554/1 (Mutable, MI=1) Misers Every Player is either a Miser or a non-Miser. Every Player is a non-Miser at the time e Registers, and every Player becomes a non-Miser whenever a new Game begins. A Player becomes a Miser by announcing to the Public Forum that e is doing so. The Scorekeepor shall keep a record of which Players are Misers and shall publish this information in eir Weekly Report. Whenever a Miser's Treasury contains any Points, those Points are immediately, without any delay or intervening events, converted to Marks, at the primary Mark Exchange Rate. History: Created by Proposal 2430, Jan. 30 1996 Amended(1) by Proposal 2535, Mar. 13 1996 ---------------------------------------- Rule 1479/1 (Mutable, MI=1) Point Penalties and Awards Whenever a Rule calls for a Player to lose some quantity of Currency without specifying where this Currency shall be transferred to, that quantity shall be transferred from that Player's Treasury to the Bank. Whenever a Rule calls for a Player to receive some quantity of Currency but does not specify where the Currency shall be transferred from, that quantity shall be transferred from the Bank to that Player's Treasury. The payment of all Salaries shall be by transfer from the Bank to that of the Player receiving the Salary. History: Created by Proposal 1601, Jun. 19 1995 Amended(1) by Proposal 2476, Feb. 16 1996 ---------------------------------------- Rule 1080/1 (Mutable, MI=1) Starting Marks When a new Player enters the Game, e shall receive 3 Marks from the Bank; however, if the new Player has previously been a Player within the last three months, e shall receive however many Marks e had when e left, or 3 Marks, whichever is less. History: ... Amended(1) by Proposal 1601, Jun. 19 1995 ---------------------------------------- Rule 1034/4 (Mutable, MI=1) Purchase of Marks An Entity which possesses Points in any of its Treasuries is permitted to convert any or all of those Points to Marks. E does so by sending a message to the Scorekeepor indicating that e wishes to do so, also specifying how many Points e wishes to convert, and the Treasury from which this Points are to be removed (if the Entity possess more than one Treasury). When such a message is sent, if the Treasury specified is owned by the Entity requesting the exchange and contains at least as many Points as are to be converted, then that many Points are transferred from that Treasury to the Bank, and, simultaneously, a commensurate number of Marks computed using the primary Mark Exchange Rate are transferred from the Bank to that Treasury. All these transfers shall be detected and reported by the Scorekeepor, as soon as possible after they take place. History: ... Amended(1) by Proposal 1347, Nov. 29 1994 Amended(2) by Proposal 1601, Jun. 19 1995 Amended(3) by Proposal 1691, Sep. 1 1995 Amended(4) by Proposal 1743, Oct. 15 1995 ---------------------------------------- ======================================= Extra Votes This Category includes Rules concerning the Currency of Extra Votes. ---------------------------------------- Rule 1477/0 (Mutable, MI=1) Extra Votes Extra Votes are a Currency. The MUQ of Extra Votes is 1. The Recordkeepor for Extra Votes is the Assessor, or, in eir absence, the Speaker. The Mintor of Extra Votes is the Mint. History: Created by Rule 1601, Jun. 19 1995 ---------------------------------------- Rule 1442/8 (Mutable, MI=1) Using Extra Votes Provided that e possesses sufficient Extra Votes, a Player may use them to cast extra Votes on a Proposal up to the maximum allowed to them for that Proposal, as specified in other Rules. A Player casts an extra Vote by notifying the Assessor that e is doing so, at the same time specifying the Proposal upon which the Vote is cast, and the Vote itself. Extra Votes may only be cast on a Proposal during the Voting Period of that Proposal. If, at the moment the Player casts an extra Vote, e possesses at least one Extra Vote, then the Extra Vote is legally cast, and one Extra Vote is transferred from the Treasury of the Player to the Bank. Otherwise, the Extra Vote is not legally cast, and no transfer takes place. All transfers required by this Rule shall be detected and reported by the Assessor. [CFJ 791: "Using" Extra Votes is synonymous with "casting" them. EVs are Votes as well as Currencies.] History: Created by Proposal 1479, Mar. 15 1995 Amended(1) by Proposal 1533, Mar. 24 1995 Amended(2) by Proposal 1538, Apr. 4 1995 Amended(3) by Proposal 1544, Apr. 14 1995 Amended(4) by Proposal 1565, Apr. 28 1995 Amended(5) by Proposal 1601, Jun. 19 1995 Amended(6) by Proposal 1625, Jul. 17 1995 Amended(7) by Proposal 2506, Mar. 3 1996 Amended(8) by Proposal 2519, Mar. 10 1996 ---------------------------------------- Rule 1525/0 (Mutable, MI=1) One EV a Week for Successful Proposals At the beginning of each Nomic Week, every Player who had previously proposed a Proposal which was subsequently adopted during the Nomic Week immediately preceding shall receive one Extra Vote from the Bank. These transfers shall be detected and reported by the Assessor. History: Created by Proposal 1745, Oct. 15 1995 ---------------------------------------- ======================================= Powers This Category includes Rules concerning the Currency of Powers. ---------------------------------------- Rule 1517/1 (Mutable, MI=1) Definition of the Powers There is a class of Nomic Entities called the Powers. An Entity is a Power if and only if it designated by the Rules to be so. Powers are a Currency. The Mintor of the Powers is the Mint. The Recordkeepor for the Powers is the Assessor. Instances of Powers are called Cards. A Player may use a Power only if e possesses a Card of that Power. A Player uses a Power by 'casting' it upon an Active Player, which may be emself. Powers may only be cast by Active Players. A Player must inform the Assessor whenever e casts a Power, otherwise the Power is not legally cast. The casting Player is called the Caster. Rules which create specific Powers may specify that that Power may not be cast or may only be cast by certain Players, or on certain Players. If the casting of a Power requires the specification by the Caster of a Proposal or Proposals to which it applies, then all Proposals so specified by the Caster must be ones for which the Voting Period has commenced and not yet concluded, or the Power is not legally cast. If a Card of such a Power is legally cast, it is In Limbo until the Voting Periods of all specified Proposals have ended. The following are generally true of all Cards, unless a Rule defining a specific Power says otherwise of the Power which that Rule defines: 1) exactly one Card of a given type exists at any time. 2) when a Card is not held by any Player, it is held by the Bank. 3) provided that the Bank holds at least one Card of a given type, Players may purchase a Card of that type from the Bank. 4) the purchase price of a Card is 10 Mil. 5) when a Player uses a Card, or if e does not use it within a week of having acquired it, either from the Bank or from another Player, it is returned to the Bank. 6) a Player who possesses a Card but who has not yet made use of it may trade it to another Player as e sees fit. 7) Cards which are In Limbo may not be cast. The Assessor is responsible for detecting and reporting all transfers which occur as a result of the use of Powers. History: Created by Proposal 1719, Sep. 19 1995 Amended(1) by Proposal 2554, Mar. 22 1996 ---------------------------------------- Rule 1618/0 (Mutable, MI=1) Precedence Relations Among Powers In the case where two or more Rules which define specific Powers conflict in their effects, then if one of the Rules claims to take precedence over all other Rules which define specific Powers, that Rule shall have precedence. Otherwise, precedence shall be determined by reverse order of casting, that is, the Rule defining the latest cast Power shall have precedence. History: Created by Proposal 2520, Mar. 10 1996 ---------------------------------------- Rule 1518/1 (Mutable, MI=1) Purchasing and Trading Powers No Player may possess more than two Cards in any ten day period. This restriction is called 'the ten day restriction'. For the purposes of this Rule, each acquisition of a Card by a Player counts as a new possession of a Card by that Player. If the transfer of a Card to Player would result in that Player violating the ten day restriction, then the transfer is cancelled and does not take place. This Rule takes precedence over any Rule which requires or permits transfers prohibited by this Rule from taking place. A Player purchases a Card from the Bank by sending a message to the Public Forum indicating that e transfers the purchase price of that Card to the Bank, and indicating which Card it is that e wishes to purchase, provided that the purchase does not violate the ten day restriction. A Player trades a Card to another Player by sending a message to the Public Forum indicating that e transfers the Card to that Player, provided that the trade does not violate the ten day restriction. This Rule takes precedence over other Rules which would permit these transactions to take place without notification in the Public Forum. History: Created by Proposal 1719, Sep. 19 1995 Amended(1) by Proposal 2041, Dec. 11 1995 ---------------------------------------- Rule 1603/0 (Mutable, MI=1) The Powers Lottery As soon as possible after the beginning of each Nomic Week in which at least one Card of a Power is held by the Bank, the Assessor shall conduct a Powers Lottery, as set out below, and announce the results of the Lottery in the Public Forum. The Powers Lottery is conducted as follows: the Assessor randomly chooses one Card which is held by the Bank to be the prize of that week's Lottery. The Assessor also randomly chooses an Active Player to be winner of the week's Lottery. The chosen Card is transferred to the winner of the week's Lottery. If the Card chosen to be the prize is a Card of the Power of Influence, then the Card counts as a 3-vote Power of Influence Card. This Rule takes precedence over Rules which describe other ways of determining the influence granted by a Card of the Power of Influence. History: Created by Proposal 2508, Mar. 3 1996 ---------------------------------------- Rule 1520/2 (Mutable, MI=1) The Power of Immunity There is a Power called the Power of Immunity. There are 4 Immunity Cards. A Player who possesses an Immunity Card may only cast the Power on emself. A Player upon whom the Power of Immunity is cast is called an Immune Player. A Card of the Power of Immunity is in Limbo for ten days after it is cast. The effect of the Power of Immunity is to neutralize the effects of Powers upon the Immune Player, other than those Powers cast by the Immune Player emself, for a period commencing three days prior to the casting of the Power, and concluding ten days after the Power is cast. A Power which is neutralized in this way is called a Neutralized Power. The Power of Immunity does not cancel the castings of Neutralized Powers upon an Immune Player; rather, it deprives them of any effects on an Immune Player which they might otherwise have. The purchase price of a Power which is Neutralized because a Player is Immune is transferred from the Bank to the Caster of the Neutralized Power. For a Neutralized Power which has been cast prior to the casting of the Power of Immunity, this transfer takes place when the Power of Immunity is cast. For a Neutralized Power which is cast after the Power of Immunity is cast, this transfer takes place at the time the Neutralized Power is cast. The Assessor is responsible for detecting these transfers and reporting them to the appropriate Recordkeepor. If this Rule conflicts in its effects with those of another Rule defining a specific Power, then the conflict shall be resolved according to the Rule for determining precedence among Powers. History: Created by Proposal 1724, Oct. 6 1995 Amended(1) by Proposal 1778, Nov. 6 1995 Amended(2) by Proposal 2520, Mar. 10 1996 ---------------------------------------- Rule 1521/2 (Mutable, MI=1) The Oracle Power There is a Power called the Oracle Power. There are two Oracle Cards. The Player upon whom the Oracle Power is cast is called the Oracle. The Oracle Power may not be cast by or on the Assessor. When a Player is the Oracle, e must predict whether a particular Proposal, specified by the Caster, will pass or fail. This prediction must be made in a message to the Public Forum, before the end of the Voting Period on that Proposal. The Oracle may predict at most one of the outcomes, pass or fail. If the Oracle predicts the outcome of the vote on that Proposal correctly, then 10 points and are transferred from the Caster to the Bank, and from the Bank to the Oracle. If the prediction of the Oracle is incorrect, or if the Oracle makes no prediction before the close of the Voting Period, then 3 Extra Votes are transferred from the Oracle to the Caster, and 50 points are transferred from the Oracle to the Bank, and from the Bank to the Caster. The Caster casts the Oracle Power upon a Player by sending a message to the Public Forum specifying that that Player is to be the Oracle. In the same message, the Caster must also state on which Proposal the Oracle is to make eir prediction. This Proposal must be one for which the first half of the Voting Period has not yet finished, at the time the message appears in the Public Forum. Unless all these conditions are met, the Power is not legally cast. If this Rule conflicts in its effects with those of another Rule defining a specific Power, then the conflict shall be resolved according to the Rule for determining precedence among Powers. The Assessor is responsible for detecting and reporting all transfers which occur as a result of this Rule. History: Created by Proposal 1725, Oct. 6 1995 Amended(1) by Proposal 1765, Oct. 31 1995 Amended(2) by Proposal 2520, Mar. 10 1996 ---------------------------------------- Rule 1522/2 (Mutable, MI=1) The Power of Influence There is a Power called the Power of Influence. A Player on whom the Power of Influence is cast is called an Influential Player. The effect of the Power of Influence is to increase the maximum number of votes which the Influential Player may cast on a single Proposal, specified by the Caster, called the Influenced Proposal. The maximum number of votes which may be cast by the Influential Player on the Influenced Proposal may be increased to 3, 4, or 5 votes, depending on the price last paid to the Bank in order to purchase the Power. The purchase price of the Power of Influence increases according to the extent of the Influence granted by the use of the Power, and this greater influence is granted by the Power of Influence only if the Bank is paid for it, as set out below: A maximum of 3 votes : 10 Mil A maximum of 4 votes : 25 Mil A maximum of 5 votes : 50 Mil A Player casts the Power of Influence by sending a message to the Assessor specifying which player is to be the Influential Player, and which Proposal is to be the Influential Proposal. If this Rule conflicts in its effects with those of another Rule defining a specific Power, then the conflict shall be resolved according to the Rule for determining precedence among Powers. History: Created by Proposal 1728, Oct. 6 1995 Amended(1) by Proposal 2520, Mar. 10 1996 Amended(2) by Proposal 2554, Mar. 22 1996 ---------------------------------------- Rule 1523/2 (Mutable, MI=1) The Power of Quiet There is Power called the Power of Quiet. There are 3 Quiet Cards. The purchase price for each of these Cards is 5 Mil. The effect of this Power is to prevent the Player on whom it is cast, called the Quiet Player, from casting any Extra Votes on a Proposal specified by the Caster, called the Quiet Proposal. The Power of Quiet may not be cast by the Assessor. A Quiet Player is not permitted to cast Extra Votes on their Quiet Proposal. If a Quiet Player has already cast Extra Votes on their Quiet Proposal at the time they become Quiet, then these Extra Votes are without effect on the Quiet Proposal, and Extra Votes equal in number to those cast by the Quiet Player on the Quiet Proposal are transferred from the Bank to the Quiet Player. The Assessor is responsible for detecting and reporting these transfers. The Caster casts the Power of Quiet by sending a message to the Assessor unambiguously identifying the Player who is to be the Quiet Player, and the Proposal which is to be the Quiet Proposal. Unless this condition is met, the Power is not legally cast. This Rule takes precedence over other Rules which describe the circumstances in which Players may legally cast Extra Votes, with the exception of Rules which describe the effects of other Powers. This Rule also takes precedence over other Rules which describe the effects of legally cast Extra Votes on Proposals. If this Rule conflicts in its effects with those of another Rule defining a specific Power, then the conflict shall be resolved according to the Rule for determining precedence among Powers. History: Created by Proposal 1729, Oct. 6 1995 Amended(1) by Proposal 2520, Mar. 10 1996 Amended(2) by Proposal 2554, Mar. 22 1996 ---------------------------------------- Rule 1540/1 (Mutable, MI=1) The Skeptic Power There is a Power called the Skeptic Power. There are two Skeptic Cards. The Caster of the Skeptic Power is called the Skeptic; the Player on whom the Skeptic Power is cast is called the Believer. The Skeptic Power may not be cast by or on the Assessor. A Player casts the Skeptic Power by sending a message to the Public Forum clearly and unambiguously identifying the Player who is to be the Believer. In the same message, the Skeptic must give the number of a Proposal, called the Doubtful Proposal, which has been proposed by the Believer, for which the first half of the Voting Period has not yet finished, and state that e, the Skeptic, doubts that this Proposal will pass. Unless all these conditions are met, the Power is not legally cast. The Believer must, before the conclusion of the Voting Period of the Doubtful Proposal, indicate in a message to the Public Forum, whether e concurs with or dissents from the doubt of the Skeptic. If e makes no such indication, then e is assumed to have dissented. If the Believer indicates that e concurs with the doubt of the Skeptic, then the Believer is penalized 30 points, which are transferred to the Bank, and from the Bank to the Skeptic. If the Believer dissents from the doubt of the Skeptic, then if the Doubtful Proposal fails, the Believer is penalized 3 Extra Votes, which are transferred from the Believer to the Skeptic, and 50 points, which are transferred from the Believer to the Bank, and from the Bank to the Skeptic. If, however, the Doubtful Proposal passes, then the Skeptic is penalized 3 Extra Votes, which are transferred from the Skeptic to the Believer, and 20 points, which are transferred from the Skeptic to the Bank, and from the Bank to the Believer. If this Rule conflicts in its effects with those of another Rule defining a specific Power, then the conflict shall be resolved according to the Rule for determining precedence among Powers. The Assessor is responsible for detecting and reporting all Currency transfers which occur as a result of this Rule. History: Created by Proposal 1762, Oct. 31 1995 Amended(1) by Proposal 2520, Mar. 10 1996 ---------------------------------------- ======================================= Style Points and the Wizard This Category includes Rules concerning Style Points and the Office of the Wizard. ---------------------------------------- Rule 1542/2 (Mutable, MI=1) Style Points There are Entities known as Style Points. All Players possess an integral number of Style Points that is positive, negative or zero. The number of Style Points a Player has is that Player's Style. Any new Player, or a Player with no recorded Style Points, begins with a Style of zero. At the time there is a legal and correct announcement of a End of the Game, all Players have their Style set to zero. Every time a Proposal is distributed, the Wizard has the option of changing the Style of the Player who submitted that Proposal, as long as that Player is not the Wizard. The Wizard may only change the Style of Players whose Proposals were distributed after e became Wizard. The Wizard may add or subtract up to three Style Points from the Proposer's Style for any reason having to do with the form, content, effects, or nature of the Proposal-- but, for the change to have effect, such reasons must be included in eir Wizard's Report, as provided for in other Rules. A Player's Style can only change as provided for in this Rule. History: Created by Proposal 2026, Nov. 28 1995 Amended(1) by Proposal 2057, Dec. 25 1995 Amended(2) by Proposal 2524, Mar. 10 1996 ---------------------------------------- Rule 1543/2 (Mutable, MI=1) The Wizard There is a Player known as the Wizard. The Wizard is the Player in charge of maintaining a record of each Player's Style. The Wizard must post in the Public Forum, at least once a week, a report which includes: i) The Style of every Player. ii) All Style changes, and the values of those changes, since the last Wizard's Report. iii) The Proposal numbers of every Proposal that merited a Style change. iv) The reasons for each change. The Player who is the Wizard, as compensation for his duties, receives one Extra Vote from the Bank every Nomic Week in which that Player produced a Wizard's Report. This transfer is reported to the Assessor by the Wizard. History: Created by Proposal 2026, Nov. 28 1995 Amended(1) by Proposal 2057, Dec. 25 1995 Amended(2) by Proposal 2524, Mar. 10 1996 ---------------------------------------- Rule 1609/0 (Mutable, MI=1) Wizard Transition Wizard Transition is the process by which one Player ceases to be Wizard while, at the same time, another Player becomes the Wizard. Wizard Transition occurs when any of the following happens: i) There is a legal and correct announcement of a Game End. ii) The Wizard goes (or is already) On Hold iii) The Wizard no longer wishes to be Wizard. The Wizard must initiate a Wizard Transition as soon as possible after any of these events by announcing the initiation in the Public Forum stating that a Wizard Transition is taking Place. The announcement must contain a Transition List containing the names of all Players who are not On Hold and not the Wizard, in descending order of their Style. If the Transition is occurring as a result of a Game End, the Style used for this ordering is the Style the Players had immediately prior to the legal announcement of the Game End. Otherwise, it is the Players' current Style. In the case of Players with the same Style, those Players' order is randomly determined by the Wizard. (As long as the list as a whole is ordered by descending Style.) Upon the announcement of the Transition, the first Player on the Transition List (The Player with the highest Style) immediately becomes the Wizard, and the Player who initiated the Transition ceases to be the Wizard. If a Player ever ceases to be Wizard before initiating a Wizard Transition, or if there is, for any reason, no Player legally designated as the Wizard, the Speaker shall immediately become the Wizard and, as soon as possible thereafter, initiate a Wizard Transition. A Player may only become the Wizard as provided for in this Rule. History: Created by Proposal 2524, Mar. 10 1996 ---------------------------------------- Rule 1610/0 (Mutable, MI=1) Declining the Position of Wizard When a Wizard Transition is initiated (as described in other Rules) Players have the option to decline becoming the Wizard. The new Wizard has the option of declining within 72 hours after becoming the Wizard by posting a message to the Public Forum saying e doesn't wish to be Wizard. If this decline is made, that Player's name is stricken from the Transition list (as if eir name never appeared upon it), and that Player ceases to be the Wizard. The next Player in descending order immediately becomes the first Player on the Transition list and becomes Wizard, with the same option of declining. A decline may also be done before a Player becomes Wizard, and any Player who does so has eir name stricken from the Transition list as if eir name had never appeared upon it. However, any decline by a Wizard that is not made within 72 hours of eir becoming Wizard is void and without effect. History: Created by Proposal 2524, Mar. 10 1996 ---------------------------------------- ======================================= Blots and the Immaculate This Category includes Rules concerning Blots or the lack thereof, and the Office of the Tabulator ---------------------------------------- Rule 1435/0 (Mutable, MI=1) Definition of Blots and Immaculate Let there be an Entity called a Blot. At all times all Players possess an integral number of Blots equal to or greater than zero. Any Player with zero Blots is referred to as Immaculate. Any new Player, or a Player with no recorded Blots, shall be Immaculate. Blots may never be transferred between Players. A Player who is not Immaculate can't Win the Game. This Rule takes precedence over any other rule defining who is eligible to Win. History: Created by Proposal 1457, Mar. 1 1995 ---------------------------------------- Rule 1436/3 (Mutable, MI=1) The Tabulator Let there exist the Office of Tabulator. The Tabulator is the Officer responsible for keeping track of the Blots possessed by each Player, as well as all ex-Players who have Blots. The Tabulator may have other duties as defined in the Rules. Once a Week The Tabulator shall post to the Public Forum a report of the Blots held by each Player. If a Player has earned Blots since the last report, this report must publicize the reason for the gain in Blots. The Tabulator's salary shall be four Points per Week. If any Rule mandates a change in Blots, but does not also specifically state the Player who is Legally Responsible for detecting the change and reporting it to the Tabulator, then the change in Blots is canceled. If a Blot change is not reported within four Weeks of its occurrence, or by the end of the Game in which it occurred, whichever is sooner, the change in Blots is cancelled. History: Created by Proposal 1457, Mar. 1 1995 Amended(1) by Proposal 1494, Mar. 15 1995 Amended(2) by Proposal 1735, Oct. 15 1995 Amended(3) by Proposal 2442, Feb. 6 1996 ---------------------------------------- Rule 1439/1 (Mutable, MI=1) Blots Due to a CFJ If a Call For Judgment (CFJ) clearly alleging that a Player has violated a specific Rule is found to be TRUE, the Player receives Blots equal to the Mutability Index of the violated Rule rounded down to the nearest whole integer, or four Blots if its Mutability Index exceeds four. This Rule defers to the wording of the violated Rule when it defines a Blot penalty in the specific case of a CFJ, or specifically forbids Blot penalties in the case of a CFJ. The Player who initially called for the CFJ has the Legal Responsibility to report Blots due to the CFJ to the Tabulator. If such a Judgement is overturned upon appeal, then the Player who received Blots shall lose the same number of Blots as were given due to the initial Judgement of the CFJ, unless e already had fewer than that number of Blots, in which case e shall lose all his Blots. The Player losing the Blots has responsibility for reporting that loss to the Tabulator History: Created by Proposal 1460, Mar. 1 1995 Amended(1) by Proposal 1674, Aug. 22 1995 ---------------------------------------- Rule 1440/2 (Mutable, MI=1) Erasing Blots A Player who has at least one Blot is permitted to remove any or all of those Blots by sending a message to the Public Forum indicating how many Blots e wishes to remove. If that Player's Treasury contains at least five Points for each Blot to be removed, then that number of Points is transferred from the Player's Treasury, and the Blots are removed; otherwise, no Points are transferred and no Blots are removed. The Scorekeepor shall detect and report all transfers and Blot Changes resulting from the application of this Rule. History: Created by Proposal 1461, Mar. 1 1995 Amended(1) by Proposal 1613, Jul. 10 1995 Amended(2) by Proposal 2472, Feb. 16 1996 ---------------------------------------- Rule 1441/0 (Mutable, MI=1) Blots upon Starting a New Game Upon beginning a new Game, any Player with Blots immediately loses Points equal to the number of eir Blots. Every Player who is not Immaculate has eir total Blots halved, rounding down to the next lower integer. This halving will never reduce a Player's total Blots below one. Detecting and reporting this Blot change is the Tabulator's responsibility. The Tabulator reports the Point losses to the Scorekeepor. History: Created by Proposal 1462, Mar. 1 1995 ---------------------------------------- Rule 1437/0 (Mutable, MI=1) Blots and Reregistration If a Player who is not Immaculate is deregistered and subsequently returns to the Game, e returns with B/(2^T) Blots, where B is the number of Blots the Player had upon deregistering, and T is the number of months since eir deregistration. The number of Blots thus received is rounded down to the next whole integer, but not reduced below one Blot. If a Immaculate Player deregisters, e is also Immaculate upon returning to the Game. If a former Player returns to the Game and has no Blots recorded, e is Immaculate upon eir return. Blot Changes due to this Rule are detected and reported by the Tabulator. History: Created by Proposal 1458, Mar. 1 1995 ---------------------------------------- ======================================= Winning a Game, and the End of a Game This Category includes Rules specifying the winner of the Game and actions taken upon the end of a Game. ---------------------------------------- Rule 112/2 (Semimutable, MI=3) Ways to Win and Preclusions Thereof Ways for a Player to Win a Game may be defined by other Rules. Also, ways to prevent a Player from Winning a Game may be defined by other Rules. A Player Wins whenever a Win condition defined by one or more of those Rules occurs for that Player, provided that no Win-Preventing conditions are also occurring at that time for that Player. If no other Rule defining a way to Win exists, then a Player Wins upon each Winter and Summer Solstice, and upon each Vernal and Autumnal Equinox, with the Winner being chosen randomly by the Speaker from among all Voters not on Hold who are not ineligible to Win because of an applicable Win-preventing Rule. History: Initial Immutable Rule 112, Jun. 30 1993 Mutated from MI=Unanimity to MI=3 by Proposal 1268, Oct. 19 1994 Amended(1) by Proposal 1451, Mar. 1 1995 Amended(2) by Proposal 1735, Oct. 15 1995 ---------------------------------------- Rule 724/4 (Mutable, MI=1) Winning the Game A Player Wins the Game if e is an Active Voter, and e possesses a number of Points greater than or equal to the number of currently registered Players times eir handicap factor times ten. A Player's handicap factor is equal to one, plus the number of Games that Player has previously won divided by six. History: ... Amended(1) by Proposal 1403, Jan. 29 1995 Amended(2) by Proposal 1422, Feb. 7 1995 Amended(3) by Proposal 1449, Mar. 1 1995 Amended(4) by Proposal 2471, Feb. 16 1996 ---------------------------------------- Rule 1580/0 (Mutable, MI=1) Multiple Winners of a Single Game If two or more Players simultaneously acheive the same or different Win Conditions, all such Players Win the Game, except for those for which Win-Preventing Conditions are also true. History: Created by Proposal 2471, Feb. 16 1996 ---------------------------------------- Rule 1498/1 (Mutable, MI=1) Another Way to Win A Player Wins the Game if e is the only Immaculate Player, and e has correctly reported this fact to the Public Forum, provided that e did not Win the Previous Game in this same manner. History: Created by Proposal 1671, Aug. 22 1995 Amended(1) by Proposal 2471, Feb. 16 1996 ---------------------------------------- Rule 1433/3 (Mutable, MI=1) End of a Game Due to a Win A Game ends when a Win occurs. If there is more than one simultaneous Winner, there is nevertheless only one Game end. When a Game ends due to a Win: - If there is only one Winner, that Voter becomes the Speaker-Elect. If there was already a Speaker-Elect, the old Speaker-Elect ceases to be Speaker-Elect. - If there is more than one Winner, the Winner with the highest Point total becomes the Speaker-Elect. If more than one Winner is tied for the highest score, the Speaker randomly selects one of them to be Speaker-Elect. If there was already a Speaker-Elect, the old Speaker-Elect ceases to be Speaker-Elect. - For every Treasury other than the Bank, if that Treasury possesses Points, a commensurate number of Marks computed using the secondary Mark Exchange Rate are transferred from the Bank to that Treasury, and all Points in that Treasury are transferred to the Bank. These transfers are to be detected and reported by the Scorekeepor. - A new Game is begun. All Rules and Proposals retain the status they had at the end of the old Game. History: Created by Proposal 1450, Mar. 1 1995 Amended(1) by Proposal 1601, Jun. 19 1995 Amended(2) by Proposal 1691, Sep. 1 1995 Amended(3) by Proposal 2471, Feb. 16 1996 ---------------------------------------- Rule 1582/0 (Mutable, MI=1) Point Exchange upon Game End Whenever a Game Ends, for every Treasury other than the Bank, if that Treasury possesses Points, a commensurate number of Marks computed using the secondary Mark Exchange Rate are transferred from the Bank to that Treasury, and all Points in that Treasury are transferred to the Bank. These transfers are to be detected and reported by the Scorekeepor. History: Created by Proposal 2471, Feb. 16 1996 ---------------------------------------- Rule 755/2 (Mutable, MI=1) Champions Let there be known the Patent Title known as Champion. This Patent Title shall be given to every Player who Wins a Game of Agora Nomic, or who has Won a Game of Agora Nomic. This Patent Title shall be awarded automatically, without need for a Proposal. If a Player Wins a Game despite a handicap factor X, then that Player shall instead receive the Patent Title "Champion*X", substituting for X the ratio of the Points required for that Player to Win, over the Points required for an unhandicapped Player to Win. History: ... Amended(1) by Proposal 2042, Dec. 11 1995 Amended(2) by Proposal 2433, Jan. 30 1996 ---------------------------------------- Rule 1465/4 (Mutable, MI=1) Champion's Reward Any Player who wins a game after the creation of this Rule shall be granted the Champion's Reward: the right to cast a third vote on Proposals. The Champion's Reward shall be granted to a winning Player beginning at the start of the first full Nomic Week after the the legal and correct announcement that that Player has won a game. The Champion's Reward shall last for four Nomic weeks from this time, and is then withdrawn from that Player. In addition, ten Extra Votes shall be transferred from the Bank to any Player who wins a game after the creation of this Rule, at the commencement of that Player's Champion's Reward. This transfer is detected and reported by the Assessor. The Registrar shall maintain a list of all Champion's Rewards which have been granted and have not yet been withdrawn, including to whom they have been granted, and their times of commencement and conclusion. This list is known as the Green Pages, and is part of the Registrar's Report. History: Created by Proposal 1594, Jun. 2 1995 Amended(1) by Proposal 1663, Aug. 18 1995 Amended(2) by Proposal 1721, Oct. 6 1995 Amended(3) by Proposal 2484, Feb. 16 1996 Amended(4) by Proposal 2532, Mar. 10 1996 ---------------------------------------- Rule 388/1 (Mutable, MI=1) Game Status When a New Game Begins Whenever a new game of Nomic is begun, the status of the new Game when it begins shall be the same as the status of the old Game when it ended, in all respects where the Rules do not specify otherwise. History: ... Amended(1) by Proposal 1734, Oct. 15 1995 ---------------------------------------- Rule 1491/1 (Mutable, MI=1) Win Tokens and the Tabulator Win Tokens are a Currency. The Recordkeepor of Win Tokens is the Tabulator; the Mintor of Win Tokens is the Mint. The Tabulator shall, at least once per Nomic Week, post a report detailing the number of Win Tokens held in each Treasury and all transactions involving Win Tokens which have occured since the last report. Whenever a Game Ends, all Win Tokens in existence are destroyed. History: Created by Proposal 1653, Aug. 6 1995 Amended(1) by Proposal 2471, Feb. 16 1996 ---------------------------------------- Rule 1492/1 (Mutable, MI=1) Winning by Tokens A Player Wins when e is both not on Hold and possesses a number of Win Tokens which exceeds the number held by every other Player at that time by the number of registered Players at the time the current Game began. The Tabulator shall notify the Public Forum as soon as possible after a Player Wins by the application of this Rule. The Tabulator shall include in eir Report the number of Tokens currently required to Win by the application of this Rule. History: Created by Proposal 1653, Aug. 6 1995 Amended(1) by Proposal 2471, Feb. 16 1996 ---------------------------------------- Rule 1493/2 (Mutable, MI=1) Win Token Transfers Each Player is permitted to make up to 3 Win Token Transactions, of the sorts described in this Rule, per Nomic Week. A Currency Transfer, as defined elsewhere, which involves Win Tokens is not a Win Token Transaction. The legal Win Token Transactions are: * The creation of one Win Token, which is then placed in the Treasury of any Player other than the Player making the Transaction; and * The removal of one Win Token from the Treasury of any Player; this Win Token is then destroyed. A Player who wishes to make a Win Token Transaction shall do so by notifying the Tabulator of the Transaction. History: Created by Proposal 1653, Aug. 6 1995 Null-Amended(1) by Proposal 1705, Sep. 4 1995 Amended(2) by Proposal 2471, Feb. 16 1996 ---------------------------------------- Rule 1559/2 (Mutable, MI=1) Win Tokens Owned Only by Players Only those Treasuries which are the personal Treasuries of Players may contain Win Tokens. This rule takes precedence over all rules which would otherwise allow this restriction to be contravened. History: Created by Proposal 2466, Feb. 6 1996 Amended(1) by Proposal 2512, Mar. 3 1996 Null-Amended(2) by Proposal 2537, Mar. 13 1996 ---------------------------------------- ======================================= Changing Speakers This Category includes Rules regulating changing the Speaker. ---------------------------------------- Rule 785/3 (Mutable, MI=1) Abandonment of Speakerhood If any Player suspects that the Speaker has Abandoned, e may send a message to all Players calling on the Speaker to announce eir presence. The Speaker must reply to all Players within one week; if no communication from the Speaker is sent to all Players or to the Public Forum within that period, and the Speaker has not changed in that week, e is defined to have Abandoned. If the Speaker has Abandoned, then if there is already a Speaker-Elect e immediately becomes Speaker, and the old Speaker becomes a Voter. If not, a new Speaker shall be chosen according to the Order of Succession, defined elsewhere, with the first Player who called for the Speaker to announce eir Presence as the Arbiter of Succession. The new Speaker shall make reasonable effort to obtain the former Speaker's materials: proposal queue, voting records, etc. but if this is not possible, then the new Speaker shall request that these be resubmitted by the Players. A Speaker who Abandons commits a Class A Crime History: ... Amended(1) by Proposal 1424, Feb. 7 1995 Amended(2) by Proposal 1682, Aug. 22 1995 Amended(3) by Proposal 2533, Mar. 13 1996 ---------------------------------------- Rule 681/3 (Mutable, MI=1) Giving Up Speakership The Speaker may voluntarily give up Speakership by announcing the fact to all Players. If there is already a Speaker-Elect, e remains Speaker-Elect. If not, a Speaker-Elect is chosen according to the Order of Succession, defined elsewhere in the Rules, with the Speaker as the Arbiter of Succession. If a Speaker-Elect chosen by this method ceases to be a Player, a new Speaker-Elect shall be chosen according to the Order of Succession with the Speaker as the Arbiter of Succession. When a Speaker voluntarily gives up Speakership in this manner, the former Speaker shall lose 25 Marks, and e shall further be prevented from Winning until the start of the next Game. History: ... Amended(1) by Proposal 1423, Feb. 7 1995 Amended(2) by Proposal 1695, Sep. 1 1995 Amended(3) by Proposal 1734, Oct. 15 1995 ---------------------------------------- Rule 1375/3 (Mutable, MI=1) Speaker Going On Hold If the Speaker is On Hold, a new Speaker shall be chosen according to the Order of Succession. The Arbiter of Succession shall be the Registrar; unless the Speaker is also the Registrar, in which case the Arbiter of Succession is the first Voter to post a message to the Public Forum stating that e is willing to act as Arbiter of Succession. The new Speaker shall make reasonable effort to obtain the former Speaker's materials: proposal queue, voting records, etc., but if this is not possible, then the new Speaker shall request that these be resubmitted by the Players. A Speaker who goes on Hold while e is still Speaker commits a Class B Crime. History: Created by Proposal 1375, Jan. 17 1995 Amended(1) by Proposal 1428, Feb. 5 1995 Amended(2) by Proposal 1682, Aug. 22 1995 Amended(3) by Proposal 2442, Feb. 6 1996 ---------------------------------------- Rule 942/5 (Mutable, MI=1) Replacement of Impossible Speaker If a Speaker is determined by CFJ to have made further play impossible by eir actions or lack thereof, and the CFJ is not appealed within the allowed time, or if such a determination is made upon appeal of a CFJ; AND if the Speaker has not changed since the CFJ was made, then if there is a Speaker-Elect e immediately becomes Speaker, and the old Speaker becomes a Voter. If not, a new Speaker is selected according to the Order of Succession, as defined elsewhere, with the Player who made the CFJ as Arbiter of Succession. The new Speaker shall make reasonable effort to obtain the former Speaker's materials: proposal queue, voting records, etc., but if this is not possible, then the new Speaker shall request that these be resubmitted by the Players. A Speaker who makes further play impossible by eir actions or lack thereof commits a Class A Crime. "Impossible" is defined here to mean overwhelmingly psychotic behavior, a complete lack of interest in the Game, or uncooperativeness of the highest order. It does *not* include normal Speaker latitudes which have been taken by past Speakers for various reasons, whether justifiable or not, including but not limited to: temporary suspension of proposal distribution, resetting of scores, or accidental illegal actions. The Judge of the CFJ *must* take these extremely tight standards into account, and the accused Speaker *must* be given an opportunity to defend eirself. This Rule adds to the set of valid classes of Judgements, and takes precedence over other Rules which may attempt to prevent this class of Judgement. History: ... Amended(1) by Proposal 1425, Feb. 7 1995 Amended(2) by Proposal 1448, Feb. 21 1995 Amended(3) by Proposal 1601, Jun. 19 1995 Amended(4) by Proposal 1682, Aug. 22 1995 Amended(5) by Proposal 2506, Mar. 3 1996 ---------------------------------------- Rule 786/3 (Mutable, MI=1) Rule of Succession for Speaker or Speaker-Elect When a Speaker or Speaker-Elect is to be filled according to the Order of Succession, that order is defined to be: Promotor Assessor Justiciar Clerk of the Courts Rulekeepor Registrar Archivist with the order determined at the time the Call for Volunteers is made. Any Rule which requires a Speaker or Speaker-Elect to be filled according to the Order of Succession must specify an Arbiter of Succession; if it does not, a Speaker or Speaker-Elect shall not be chosen according to that Rule, and this Rule takes precedence over such Rules. When the position of Speaker or Speaker-Elect is to be filled, the Arbiter of Succession shall, as soon as possible, announce that fact to the Public Forum in a Call for Volunteers. All Voters who are willing to fill the position shall indicate such in a message to the Arbiter of Succession, within three days of the Call for Volunteers. If there are no volunteers, the Arbiter of Succession shall make another Call for Volunteers. As soon as possible after the end of the three-day period, and within four days after the end of that three-day period, the Arbiter of Succession shall announce which Voter, of those who indicated a willingness to fill the position, is highest on the order of succession. That Voter shall immediately become Speaker or Speaker-Elect, whichever position was to be filled. If e becomes Speaker, the old Speaker shall become a Voter. The Arbitration Period is defined as the period in the Order of Succession starting with the Call for Volunteers and ending with: 1) the announcement by the Arbiter of Succession of the new Speaker or Speaker-Elect; 2) the filling of the position to be filled by another method; 3) the time when it becomes no longer necessary to complete the Order of Succession, according to other Rules; 4) or seven days after the Call for Volunteers is issued; whichever comes first. If the Arbitration Period ends without any of the first three criteria for the end of the Arbitration Period being fulfilled, then a new Order of Succession shall begin to fill the required position, with the first Voter to post eir willingness to the Public Forum as Arbiter of Succession, excluding any Voters who have already served as Arbiter of Succession for this particular requirement to fill the position. History: ... Amended(1) by Proposal 1426, Feb. 7 1995 Amended(2) by Proposal 1539, Apr. 4 1995 Amended(3) by Proposal 2500, Mar. 3 1996 ---------------------------------------- Rule 402/2 (Mutable, MI=1) The Speaker-Elect There shall be a position known as the Speaker-Elect. Only Voters may be Speaker-Elect; whenever a Rule specifies that the Speaker-Elect becomes Speaker, e shall cease to be Speaker-Elect. Only one Voter may be Speaker-Elect at any one time. A Voter may not become Speaker-Elect except as specified in the Rules. The position of Speaker-Elect is not an Office. Whenever there is a Speaker-Elect: 1) The Speaker shall forward copies of all necessary materials for the performance of eir position, as soon as possible to the Speaker-Elect. 2) The Speaker-Elect shall acknowledge the receipt of said materials as soon as possible after step 1. 3) As soon as possible after step 2, the Speaker shall post a message to the Public Forum announcing that the Speaker-Elect has become the Speaker. At the "Date:" of the Speaker's posting, the old Speaker shall become a Voter and the Speaker-Elect shall become the Speaker. If the Speaker-Elect changes before the completion of this procedure, it must be begun again from step 1. If another Rule specifies that the Speaker-Elect becomes Speaker before the completion of step 3, then this Rule defers to it, and the procedure above need not be completed. History: ... Amended(1) by Proposal 1421, Feb. 7 1995 Amended(2) by Proposal 1700, Sep. 1 1995 ---------------------------------------- Rule 1427/0 (Mutable, MI=1) Precedence of Speaker/Speaker-Elect Selection If a Rule requires that the position of Speaker or Speaker-Elect is to be filled during the Arbitration Period for filling the position of Speaker, then that requirement is negated; this Rule takes precedence over such Rules. If a Rule requires that the position of Speaker-Elect is to be filled during the Arbitration Period for filling the position of Speaker-Elect, then that requirement is negated; this Rule takes precedence over such Rules. If a Rule requires that the position of Speaker is to be filled during the Arbitration Period for filling the position of Speaker-Elect, then the Order of Succession procedure for Speaker-Elect is not completed, and the position of Speaker is filled according to that Rule. This Rule takes precedence over Rules requiring the position of Speaker-Elect to be filled by the Order of Succession in such a case. If a Voter becomes Speaker-Elect during a Arbitration Period by winning the game, then the Order of Succession procedure shall not be completed, and the Speaker-Elect fills the position. That is, -if the position to be filled is Speaker-Elect, the Speaker-Elect remains Speaker-Elect. -if the position to be filled is Speaker, the Speaker-Elect immediately becomes Speaker and the old Speaker becomes a Voter. In such a case, this Rule takes precedence over any Rule requiring the Order of Succession to be completed. History: Created by Proposal 1427, Feb. 7 1995 ---------------------------------------- Rule 1581/0 (Mutable, MI=1) Speaker-Elect upon Game End If there is already a Speaker-Elect at the time a Game Ends, e ceases to be Speaker-Elect. When a Game Ends, the Winner with the greatest number of Points then becomes the Speaker-Elect; if two or more Winners are tied for the same number of Points, the Speaker shall randomly select one of them to become Speaker-Elect. If the application of this Rule would result in the Speaker becoming the Speaker-Elect, the Speaker shall instead remain Speaker, and the Speaker-Elect, if any, shall cease to be Speaker-Elect. History: Created by Proposal 2471, Feb. 16 1996 ---------------------------------------- ======================================= Subordinate Legal Codes This Category includes general Rules regulating Subordinate Legal Codes ---------------------------------------- Rule 1588/0 (Mutable, MI=1) Subordinate Legal Codes A Subordinate Legal Code (SLC) is a body of law organized under the Rules. A body of law is a SLC only if it is granted that status by the Rules and it meets all other requirements in the Rules for being a SLC. History: Created by Proposal 2490, Feb. 16 1996 ---------------------------------------- Rule 1595/0 (Mutable, MI=1) Precedence of SLCs Unless otherwise specified by the Rules, older SLCs take precedence over younger ones. This ordering is based on the time the SLC is first created. This Rule does not in any way establish an order of precedence for the components, if any, within a given SLC. History: Created by Proposal 2490, Feb. 16 1996 ---------------------------------------- Rule 1591/0 (Mutable, MI=1) Jurisdiction of SLCs A SLC has the power to constrain the actions of Players in the same manner as the Rules. However, a SLC has power over only those Players within its Jurisdiction, as defined in the Rules authorizing that SLC. The Jurisdiction of a SLC must be specified by the Rules, either directly or indirectly. If the Jurisdiction of a SLC might vary over the course of the existence of the SLC, the Rules must specify a Player who is required to maintain a record of which Players are within the Jurisdiction of that SLC. History: Created by Proposal 2490, Feb. 16 1996 ---------------------------------------- Rule 1594/0 (Mutable, MI=1) Violation of SLCs A Player who is within the Jurisdiction of a SLC is required to abide by it while e remains within its Jurisdiction, unless doing so would violate either the Rules or another SLC with higher precedence. A Player who fails to abide by a SLC is in violation of that SLC. A Player who is found by a CFJ to have violated a SLC shall suffer whatever penalties specified in the Rules authorizing the violated SLC, or, if there is no such penalty specified, a default penalty of three Blots, to be reported by the Judge of the CFJ. There shall be no additional penalty imposed upon a Player who violates this Rule by violating a SLC; this Rule takes precedence over any Rule which specifies penalties for violating Rules. History: Created by Proposal 2490, Feb. 16 1996 ---------------------------------------- Rule 1590/0 (Mutable, MI=1) Maintainer of SLCs For a SLC to be legally authorized, the Rules must specify a Player who is required to maintain a record of the content of that SLC; this Player is known as the Maintainer of that SLC. The Maintainer of a given SLC must provide a copy of it to any other Player who requests it, as soon as possible after the request is made. E must also provide an updated copy of the SLC to all Players within its Jurisdiction as soon as possible after the SLC changes for any reason.. [CFJ 860: It is sufficient for the Rules to name an Officer as Maintainer of an SLC.] History: Created by Proposal 2490, Feb. 16 1996 ---------------------------------------- Rule 1589/0 (Mutable, MI=1) Modification of SLCs A SLC shall not be changed except in accordance with the Rules. Notwithstanding any other method which may be defined, a SLC can always be changed by the adoption of a Directive to amend the SLC. The Proposal containing such a Directive shall have an AI of at least 1, and if adopted the Directive has the effect of modifying the SLC in the manner specified in the Directive. A SLC is permitted to define its own mechanisms for changing its own content, and any change to a SLC adopted in accordance with its own mechanisms is legal. History: Created by Proposal 2490, Feb. 16 1996 ---------------------------------------- Rule 1592/0 (Mutable, MI=1) Power of SLCs to Change Properties A SLC has the power to define the manner in which certain properties of entities are changed. This power shall be limited to any property solely defined by that SLC and to any other property to which the Rules grant that SLC this authority. History: Created by Proposal 2490, Feb. 16 1996 ---------------------------------------- Rule 1593/0 (Mutable, MI=1) Power of SLCs to require Currency Transfers Each SLC is empowered to require Currency transfers, subject to the restriction that any such transfer must originate from the Treasury of a Player within the Jurisdiction of that SLC. This Rule defers to any Rule or Rules which grant certain SLCs broader power to require Currency transfers. History: Created by Proposal 2490, Feb. 16 1996 ---------------------------------------- ======================================= Organizations This Category includes Rules regarding Organizations in general. ---------------------------------------- Rule 1528/2 (Mutable, MI=1) Organizations Let there be a class of entities called Organizations; any one member of this class is an Organization. An entity is an Organization only if the Rules make it an Organization. History: Created by Proposal 1760, Oct. 21 1995 Amended(1) by Proposal 2421, Jan. 30 1996 Amended(2) by Proposal 2525, Mar. 10 1996 ---------------------------------------- Rule 1546/1 (Mutable, MI=1) Classes of Organizations An entity is an Organization only if it is of a class of Organization specifically defined by the Rules. The class of an Organization is determined at the time the Organization is created and cannot be changed after that time. If the Rules are changed such that they no longer define a given class of Organization, all Organizations of that class are dissolved. History: Created by Proposal 2034, Dec. 4 1995 Amended(1) by Proposal 2525, Mar. 10 1996 ---------------------------------------- Rule 1614/0 (Mutable, MI=1) Organizations' Names An entity is an Organization only if it has a name defined for it, and if that name is distinnct from the name of every other Organization. The name of an Organization cannot be changed in a manner such that if, after that change, two or more Organizations would have the same name. An Organization cannot be created if after that creation, two or more Organization would have the same name. Otherwise, the name of an Organization cany only be changed as specified by its Compact, or, in lieu of any specific procedure in its Compact, with the unanimous consent of all the Players within its Compact's Jurisdiction. The Administrator of an Organization shall notify the Notary as soon as possible after the Organization's name is changed. History: Created by Proposal 2525, Mar. 10 1996 ---------------------------------------- Rule 1459/3 (Mutable, MI=1) Private Organizations An Organization can only be Private if the Rules defining its Class permit (or require) it to be Private. If its Class permits Privacy, but does not require it, an Organization is not Private unless its Compact claims Privacy. Any Organization which is not a Private Organization is a Public Organization. The Compact of a Private Organization are privileged, and may only be divulged by Players within the Compact's Jurisdiction. (This defers to the Compact where it forbids such disclosure.) The following are the only legal exceptions: i) Disclosure of any part of the Compact to a Player within its Jurisdiction. ii) Disclosure of any part of the Compact to the current Notary. iii) Disclosure of any part of the Compact to a Judge or Justice judging a CFJ, where the Caller of the CFJ is a Player within the Compact's Jurisdiction, and the evidence provided by the Caller of the CFJ contains text purported to be part or all of the Compact. This Rule takes precedence over any Rule which would require any Player to provide the Compact of a Private Organization upon request. History: Created by Proposal 1575, Apr. 18 1995 Amended(1) by Proposal 1684, Aug. 29 1995 Amended(2) by Proposal 1760, Oct. 21 1995 Amended(3) by Proposal 1789, Nov. 13 1995 ---------------------------------------- Rule 1501/4 (Mutable, MI=1) Public Organizations An Organization is Public unless the Rules defining its Class permit (or require) it to be Private. If its Class permits Privacy, but does not require it, an Organization is Public unless its Compact claims Privacy. The Compact of a Public Organization must be provided by the Administrator of that Organization to any Player As Soon As Possible on demand. If, between the time of the demand and the time the Administrator fulfills the demand, the Compact has changed, the Administrator must provide the Compact as it existed at the time of the demand, and must additionally document every change made to the Compact between the demand and its fulfillment. This Rule defers to all other Rules which do not contain this sentence. History: Created by Proposal 1680, Aug. 22 1995 Amended(1) by Proposal 1715, Sep. 12 1995 Amended(2) by Proposal 1760, Oct. 21 1995 Amended(3) by Proposal 1785, Nov. 13 1995 Infected and Amended(4) by Rule 1454, Mar. 8 1996 ---------------------------------------- Rule 1612/0 (Mutable, MI=1) Organizations' Compacts For each Organization, let there be a SLC associated with that Organization called its Compact. Unless otherwise specified in the Compact, a Compact can be changed by the unanimous consent of all the Players within its Jurisdiction. The Administrator of an Organization is the Maintainer of the Organization's Compact. The Jurisdiction of an Organization's Compact can vary over the period of its existence. the Administrator of the Organization shall maintain a record of the Compact's Jurisdiction. The Compact of an Organization ceases to exist when the Organization ceases to exist. History: Created by Proposal 2525, Mar. 10 1996 ---------------------------------------- Rule 1457/2 (Mutable, MI=1) Judicial Procedure for Compact Violations When any Player within the Jurisdiction of a Compact believes the Compact to have been Violated by another Player, e shall inform the Administrator of that Compact's Organization of that belief, along with the nature of the Violation, the Violated text of the Compact, and the identity of the Violating Player. The Administrator shall then, As Soon As Possible, distribute this information to all Players within the Jurisdiction of the Violated Compact. If, within seven days of this distribution, no Player within the Compact's Jurisdiction disputes the claim, the Administrator shall declare the Compact Violated. The Administrator is then allowed to initiate any corrections and penalties allowed by the Rules and eir Organization's Compact. If, however, any Player under the Compact's Jurisdiction disputes the claim of Violation within seven days, then any Player within the Compact's Jurisdiction may submit a Call for Judgement, alleging that a specific Player has Violated the Compact. Such a Call for Judgement cannot be made in any other circumstance. All Players within the Compact's Jurisdiction are automatically ineligible to Judge such a CFJ. In the event that such a CFJ is found TRUE, the Compact has been Violated and the Compact's Administrator shall perform the same duties as when no Player contests the claim. In the event that such a CFJ is found FALSE, the Player which called the CFJ shall lose 5 Marks to the Bank; this transfer shall be detected and reported by the Administrator of the Compact's Organization, if the Organization does not possess a Treasury, by its Executor otherwise. History: Created by Proposal 1575, Apr. 28 1995 Amended(1) by Proposal 1697, Sep. 1 1995 Amended(2) by Proposal 1760, Oct. 21 1995 ---------------------------------------- Rule 1531/1 (Mutable, MI=1) Administrators and Their Duties The Administrator of an Organization must be within the Jurisdiction of that Organization's Compact, unless the Rules specify otherwise for Organizations of that Organization's class. If an Organization has an Executor, e must also be within the Jurisdiction of that Organization's Compact, unless the Rules specify otherwise for Organizations of that Organization's class. History: Created by Proposal 1760, Oct. 21 1995 Amended(1) by Proposal 2525, Mar. 10 1996 ---------------------------------------- Rule 1613/1 (Mutable, MI=1) Organizations' Treasuries An Organization possesses a Treasury if and only if: a) the Rules specify that Organizations of its class possess one, and b) there is a Player who is that Organization's Executor. The Administrator of an Organization must notify the Notary as soon as possible after the identity of the Executor of that Organization, if any, changes. This Rule defers to all other Rules which do not contain this sentence History: Created by Proposal 2525, Mar. 10 1996 Infected and Amended(1) by Rule 1454, Mar. 24 1996 ---------------------------------------- Rule 1547/1 (Mutable, MI=1) Some Organizations Can Cast EVs If an Organization is defined as a Voting Entity and also possesses a Treasury, then it is permitted to cast extra Votes on Proposals as if it were a Player. Such extra Votes are cast by the Executor notifying the Assessor when the Votes are cast. History: Created by Proposal 2036, Dec. 4 1995 Amended(1) by Proposal 2525, Mar. 10 1996 ---------------------------------------- Rule 1533/4 (Mutable, MI=1) Creation of Organizations, and Their Compacts Any Player is permitted to submit to the Notary, at any time, an Application to Create an Organization. Such an Application, to have legal effect, must specify the proposed class, name, and Compact of the prospective Organization, along with any other information that is required in order to create an Organization of the class specified. If, within a period of seven days, the Notary receives identical Applications to Create an Organization from as many distinct Players as required by the Rules pertaining to the class of the Organization to be created, the Organization is created. The Players who submitted the Applications in question are known as the Foundors of the new Organization. History: Created by Proposal 1760, Oct. 21 1995 Amended(1) by Proposal 2035, Dec. 4 1995 Amended(2) by Proposal 2421, Jan. 30 1996 Amended(3) by Proposal 2506, Mar. 3 1996 Amended(4) by Proposal 2525, Mar. 10 1996 ---------------------------------------- Rule 1397/4 (Mutable, MI=1) Dissolution of Organizations An Organization is required to be dissolved when: a) its Compact's Jurisdiction becomes empty, and there is no way for it to cease to be empty; b) the continued existence of the Organization would require that the Organization have no legal Adminstrator; or c) the continued existence of the Organization would require that the Organization have no legal Executor, but only if the Organization possesses a Treasury. This Rule does not in any way prevent other Rules from requiring an Organization to dissolve under other circumstances. History: Created by Proposal 1397, Jan. 29 1995 Amended(1) by Proposal 1687, Sep. 1 1995 Amended(2) by Proposal 1760, Oct. 21 1995 Amended(3) by Proposal 2421, Jan. 30 1996 Amended(4) by Proposal 2525, Mar. 10 1996 ---------------------------------------- Rule 1615/0 (Mutable, MI=1) Required Actions upon Dissolution of an Organization An Organization shall only be dissolved when either the Rules require it or the Organization's Compact requires it. The event of an Organization being required to dissolve by the Rules is called an Administrative Dissolution. The Notary is required to detect when an Administrative Dissolution takes place. The event of an Organization being required to dissolve by its Compact is called a Voluntary Dissolution. The Administrator of an Organization is required to detect when a Voluntary Dissolution takes place and to report this to the Notary as soon as possible, as eir last duty as Administrator. History: Created by Proposal 2525, Mar. 10 1996 ---------------------------------------- Rule 1536/1 (Mutable, MI=1) Treasuries of Dissolving Organizations Immediately before an Organization which possesses a Treasury ceases to exist for any reason, the Currencies in its Treasury shall be divided up and transferred to the Players within its Compact's Jurisdiction. If the Compact specifies a manner in which this division is to take place, those specifications prevail, to the extent that the Rules permit it; otherwise, the Currencies are divided up as evenly as possible. The Executor of the Organization shall detect and report these transfers. If an Organization has no valid Executor at the time it dissolves, no disbursement of the Treasury takes place. History: Created by Proposal 1760, Oct. 21 1995 Amended(1) by Proposal 2525, Mar. 10 1996 ---------------------------------------- Rule 1616/0 (Mutable, MI=1) Report of Dissolution of an Organization Upon the dissolution of an Organization, that Organization ceases to exist. As soon as possible after an Organization dissolves, for any reason, the Notary shall report that dissolution to the Public Forum. History: Created by Proposal 2525, Mar. 10 1996 ---------------------------------------- Rule 1534/3 (Mutable, MI=1) Compacts Can Require Some Currency Transfers An Organization's Compact is empowered to initiate Currency transfers, subject to the restriction that any such transfer must originate from either the Treasury of a Player within the Compact's Jurisdiction, or from the Treasury of the Organization itself. Unless the Compact specifies otherwise, such transfers shall be detected and reported by the Organization's Executor, or, if it has no Executor, its Administrator. History: Created by Proposal 1760, Oct. 21 1995 Amended(1) by Proposal 2035, Dec. 4 1995 Amended(2) by Proposal 2475, Feb. 16 1996 Amended(3) by Proposal 2525, Mar. 10 1996 ---------------------------------------- Rule 1617/0 (Mutable, MI=1) Changing the Jurisdiction of a Compact The Jurisdiction of a Compact shall only be changed in accordance with that Compact and the Rules. In any case, no Player shall ever be made part of the Jurisdiction of any Compact without eir consent. The Administrator of a Compact shall notify the Notary as soon as possible after that Compact's Jurisdiction changes. History: Created by Proposal 2525, Mar. 10 1996 ---------------------------------------- ======================================= The Notary This Category includes Rules concerning the Office of Notary. ---------------------------------------- Rule 1458/2 (Mutable, MI=1) The Notary There shall exist an Officer called the Notary. The Notary shall generally be responsible for maintaining a Record of Organizations and the Players under the Jurisdiction of their Compacts. The Notary shall maintain an up-to-date list of the Names of all Organizations, and an up-to-date list of the Players under the Jurisdiction of the Compacts of those Organizations. E Shall also keep track of the Administrators of each Organization, and the Executors of those Organizations with Treasuries. History: Created by Proposal 1575, Apr. 28 1995 Amended(1) by Proposal 1760, Oct. 21 1995 Amended(2) by Proposal 2451, Feb. 6 1996 ---------------------------------------- Rule 717/1 (Mutable, MI=1) Public Organization Report Not less than once each Nomic Week, the Notary must post a report of all Public Organizations in the Public Forum. This report shall contain: i) The Name and Class of each Public Organization. ii) The Players within the Jurisdiction of each Public Organization's Compact. iii) The identity of the Administrator of each Public Organization. iv) The identity of the Executor of each Public Organization which has Treasuries. History: ... Amended(1) by Proposal 1760, Oct. 21 1995 ---------------------------------------- ======================================= Groups and Contests This Category includes Rules regulating Groups and Contests. ---------------------------------------- Rule 766/6 (Mutable, MI=1) Groups A "Group" is an Organization of Class Group; this Class is a valid Class of Organization. All Groups are Public Organizations. The Jurisdiction of a Group's Compact is permitted to contain any Player, but no Player is permitted to be part of the Jurisdictions of the Compacts of more than one Group simultaneously. Each Group shall possess exactly one Treasury. A Group must have exactly three Foundors, who constitute the Group's initial Jurisdiction. Both the Administrator and the Executor of a Group must be part of the Jurisdiction of that Group's Compact. The following definitions pertain to Groups: * Ordinances: a synonym for a Group's Compact. * Ordinancekeepor: a synonym for the Group's Administrator * Vizier: a synonym for the Group's Executor * Membership: the Jurisdiction of the Group's Compact. [CFJ 816: There may exist more than one Group.] History: ... Amended(1) by Proposal 1415, Feb. 1 1995 Amended(2) by Proposal 1601, Jun. 19 1995 Amended(3) by Proposal 1760, Oct. 21 1995 Amended(4) by Proposal 2035, Dec. 4 1995 Amended(5) by Proposal 2470, Feb. 16 1996 Amended(6) by Proposal 2563, Apr. 6 1996 ---------------------------------------- Rule 716/4 (Mutable, MI=1) How to Form a Group An Application to Create a Group must contain, in addition to any information required elsewhere, a list of the prospective initial Members and the identity of the prospective initial Ordinancekeepor and Vizier of the the Group to be created. Further, no Player on the list of prospective initial Members may be a Member of another Group. History: ... Amended(1) by Proposal 1680, Aug. 22 1995 Amended(2) by Proposal 1754, Oct. 21 1995 Amended(3) by Proposal 1760, Oct. 21 1995 Amended(4) by Proposal 2653, Apr. 6 1996 ---------------------------------------- Rule 1621/0 (Mutable, MI=1) Notary Must Announce Group Creation As soon as possible after a Group is created, the Notary shall publish the name of the Group, its initial Membership, and the identities of its Vizier and Ordinancekeepor to the Public Forum. History: Created by Proposal 2563, Apr. 6 1996 ---------------------------------------- Rule 719/2 (Mutable, MI=1) Joining a Group A Player shall be added to the Membership of a Group only when: a) the Player to be added is not already a Member of another Group; b) the Player to be added has sent the Vizier of the Group in question a message requesting to be added to the Membership of that Group; and c) the addition of that Player to that Group's Membership is otherwise permitted by that Group's Ordinances and the Rules. History: ... Amended(1) by Proposal 1760, Oct. 21 1995 Amended(2) by Proposal 2563, Apr. 6 1996 ---------------------------------------- Rule 721/3 (Mutable, MI=1) The Ordinances, and Defaults Unless the Ordinances of a Group specify otherwise, the Vizier of a Group shall be that Founder of the Group whose Application was received first by the Notary. If this person is no longer a Member of the Group, then the Group shall be dissolved. Unless the Ordinances of a Group specify otherwise, the Ordinancekeepor of a Group shall be its Vizier. If a given Group is a Voting Entity, then it shall be entitled to cast Vote(s) only as specified by its Ordinances. If the Ordinances of the Group do not specify how the Group shall cast its Vote(s), it may not do so. A Group is not entitled to cast Votes on a Proposal if it did not exist at the beginning of the Voting Period of that Proposal. A Group with fewer than three Members is not entitled to cast Votes. The Vizier of a Group is responsible to communicate the Group's Votes to the Assessor. History: ... Amended(1) by Proposal 1641, Aug. 1 1995 Amended(2) by Proposal 1760, Oct. 21 1995 Amended(3) by Proposal 2563, Apr. 6 1996 ---------------------------------------- Rule 1620/0 (Mutable, MI=1) Group Coins Each Group has associated with it a Currency. This Currency is created when the Group is created. The Name of this Currency is formed by appending the word "Coins" to the Name of the Group. The Recordkeepor of this Currency is the Vizier of the Group. The Mintor of this Currency is the Group itself. Each Group has Mint Authority. History: Created by Proposal 2563, Apr. 6 1996 ---------------------------------------- Rule 718/2 (Mutable, MI=1) Resignation from a Group A Player who is a Member of a Group shall be removed from the Jurisdiction of that Group's Compact when that Player sends a message to the Notary and the Vizier of that Group, indicating that e is resigning from that Group. The Ordinances of a Group are not permitted to prohibit a Player from sending such a message. This Rule does not in any way prevent a Player from being removed from the Jurisdiction of a Group's Compact by other means specified by the Rules or the Ordinances of that Group. History: ... Amended(1) by Proposal 1760, Oct. 21 1995 Amended(2) by Proposal 2563, Apr. 6 1995 ---------------------------------------- Rule 1446/8 (Mutable, MI=1) Contests A "Contest" is an Organization of Class Contest; this Class is a valid Class of Organization. All Contests are Public Organizations. The Jurisdiction of a Contest is permitted to contain any Player. Each Contest shall possess exactly one Treasury. The Executor of a Contest is, at all times, its Administrator. A Contest must have exactly one Foundor, who becomes the Contest's initial Administrator. The following definitions pertain to Contests: * Regulations: a synonym for a Contest's Compact. * Contestmaster: a synonym for a Contest's Administrator. * Contest Fund: a synonym for a Contest's Treasury. * Contestant: a Player who is part of a Contest's Jurisdiction, but who is not the Contest's Administrator. A Contest is created by distributing a copy of its initial Regulations to the Public Forum, along with the Contest's Name, any provisions to the contrary in the default Organization Rules notwithstanding. [CFJ 760: If the Regulations specify that the position of Contestmaster is to be vacated, that is without effect. CFJ 800: A Contest need not be a game in the strict sense of the word.] History: Created by Proposal 1509, Mar. 24 1995 Amended(1) by Proposal 1574, Apr. 28 1995 Amended(2) by Proposal 1601, Jun. 19 1995 Amended(3) by Proposal 1644, Aug. 1 1995 Amended(4) by Proposal 1670, Aug. 18 1995 Amended(5) by Proposal 1760, Oct. 21 1995 Null-Amended(6) by Proposal 1763, Oct. 31 1995 Amended(7) by Proposal 2401, Jan. 20 1996 Amended(8) by Proposal 2562, Apr. 6 1996 ---------------------------------------- Rule 1539/0 (Mutable, MI=1) Regulations and Membership of Contests A Contest's Regulations consist only of Statutes, any one of which is referred to as a Regulation. No Player within Jurisdiction of a Contest's Regulations is bound by a Regulation or combination of Regulations that conflict with the Rules. The Regulations can specify the following: i) How a Contestmaster is replaced. No person may become Contestmaster without eir consent. If left unspecified, the Contestmaster cannot change while the Contest exists. ii) How the Currencies in the Contest Fund shall be spent. If this is not specified, they may only be spent when the Rules require it. iii) The amount of the Entry Fee for the Contest, in the form of units of any specific Currency. iv) Additional restrictions on Players to become Contestants, and conditions under which Contestants cease to be Contestants. A Player becomes a Contestant by notifying the Contestmaster and paying the prescribed Entry Fee to the Contest Fund. A Contestant may quit a Contest at any time by so notifying the Contestmaster. A Contestmaster may resign at any time by posting a message to that effect to the Public Forum, at which time e ceases to be Contestmaster. History: Created by Proposal 1760, Oct. 21 1995 ---------------------------------------- ======================================= Contracts This Category includes Rules defining and regulating Contracts and Bearerbonds. ---------------------------------------- Rule 1455/1 (Mutable, MI=1) Contracts Let there be a class of Organization known as a Contract, whose Compact can also be referred to as a Contract. A Contract consists only of Warranties, which are known as its Terms, the Players within its Jurisdiction are known as the Parties to the Contract, and the Administrator for all Contracts is the Notary. Contracts do not possess Treasuries, nor do they possess Executors. Contracts have the legal force to impose penalties upon Parties that do not abide by the Terms of the Contract. Parties that are unwilling or unable to abide by the Terms are said to be in Breach of the Contract. A Contract may specify the following: i) What actions the parties to the contract are required to perform, or are prohibited from performing, and under what conditions these requirements or prohibitions have force. ii) What penalties are imposed upon a party who Breaches the Contract. The Foundors of a Contract must be the set of all Parties to the Contract. In addition to what other Rules require them to provide to the Notary, the Foundors must also specify the following information: i) The identity of each Party to the Contract, each of whom must be named in the Terms of the Contract itself. Providing a unique Name for the Contract is optional, this takes precedence over the general requirements for information provided. If no Name is provided, the Notary must provide a unique Name for the Contract and provide this Name to all Parties. Parties can then change the Name as provided for in the Contract or in other Rules. A Contract is Private, and the Notary shall send a notification to all the Parties of a Contract As Soon As Possible after it has been legally entered into. The Contract shall be in force no sooner than the moment of that notification. A Contract ceases to have force at the moment it is dissolved in accordance with its Terms, or one or more of the Parties of the Contract ceases to be a Player, or the Contract is breached as described elsewhere. When a Contract is changed (including any change in the Parties) a current Party to the Contract must inform the Notary of the change as soon as possible after it occurs. If a Party is being added to, or removed from, the Contract, the change only has effect if _that_ Party sends the notification. The Notary shall forward this notification of change to all current Parties of the Contract As Soon As Possible thereafter. History: Created by Proposal 1575, Apr. 28 1995 Amended(1) by Proposal 1760, Oct. 21 1995 ---------------------------------------- Rule 1456/3 (Mutable, MI=1) Breach of Contract: Definition and Penalties A Contract is Breached if any party to the Contract fails, for any reason, to perform any action required of em by the Contract, or performs, for any reason, any action prohibited of em by the Contract. A Breach is officially determined when the Notary finds a Player in Violation of the Contract's Terms, as described in other Rules. If a Party cannot fulfill the Terms of the Contract because to do so would conflict with the Rules, e is required to Breach the Contract and must suffer the penalties for a Breach. (This applies even if other Rules absolve the Party from obeying the Terms.) The following shall take place in the event that a party of a Contract breaches that contract: i) 20 Marks shall be immediately transferred from the breaching Player to the Bank. ii) The breaching Player shall gain 3 Blots. iii) 30 Marks shall be divided as evenly as possible and transferred from the breaching Player to each of the other parties of the Contract. A Contract may specify additional penalties which are to be imposed in the event of a breach; however, such penalties shall be limited to the transfer of Currencies from the party who breached the Contract to any or all of the other Parties of the Contract. The Notary shall be responsible for reporting all Currency and Blot changes which arise as a result of this Rule. In the event of a breach, the Notary shall have the authority to order all specifically enumerated Currency transfers required by the Rules pertaining to Contracts and by the Contract which has been Breached. This authority is limited to ordering the transfer of Currencies from the Party in breach to the Bank and/or to other Parties of the Contract. History: Created by Proposal 1575, Apr. 28 1995 Amended(1) by Proposal 1682, Aug. 22 1995 Amended(2) by Proposal 1696, Sep. 1 1995 Amended(3) by Proposal 1760, Oct. 21 1995 ---------------------------------------- ======================================= Honour This Category includes Rules regulating Honour and Kudos. ---------------------------------------- Rule 1062/1 (Mutable, MI=1) Kudos and Honour Let there be an Entity called the Kudo (plural: Kudos). The amount of Kudos a Player holds is called eir Honour. All Players possess at all times an integral number of Kudos not less than 0. A new Player, or a Player with no Kudo record starts with 20 Kudos. If a Player is deregistered but returns within three months, e starts with the same number of Kudos e had when e left. If e returns after a longer time than three months, e is treated as a new Player with respect to Kudos. History: ... Amended(1) by Proposal 1376, Jan. 17 1995 ---------------------------------------- Rule 1377/2 (Mutable, MI=1) The Herald Let there exist the Office of "Herald". The Herald shall maintain a record of the Honour of every Player and of every non-Player who has been a Player during the past three months. The Herald shall, once each Week, post a Report to the Public Forum; this Report shall report on the Honour of every entity for which the Herald is required to maintain records, and all changes to the above since the last such Report. The report of changes shall include the reason for each change; this shall include (but not be limited to) any justification provided by a Player as part of a Player-caused Kudo transfer. History: Created by Proposal 1377, Jan. 17 1995 Infected and Amended(1) by Rule 1454, Jan. 29 1996 Amended(2) by Proposal 2503, Mar. 3 1996 ---------------------------------------- Rule 1378/3 (Mutable, MI=1) Kudo Transfers A single Kudo shall be transferred from one Player (the "Victim") to a second Player (the "Beneficiary") when a Player (the "Transferer") sends a message to the Herald indicating that e is transferring a Kudo from the Victim to the Beneficiary, and all the following conditions hold: a) the Transferer has not, during the current Nomic Week, previously caused two or more Kudo transfers; b) the Transferer is not the same Player as the Beneficiary; c) The Transferer has not, during the current Nomic Week, previously transferred a Kudo away from the Victim or to the Beneficiary; d) the Victim has at least one Kudo; and e) the message contains a justification for the transfer. This Rule does not in any way prohibit other Rules from causing changes to a Player's Honour. History: Created by Proposal 1378, Jan. 17 1995 Amended(1) by Proposal 1497, Mar. 15 1995 Amended(2) by Proposal 1628, Jul. 17 1995 Amended(3) by Proposal 2501, Mar. 3 1996 ---------------------------------------- Rule 1008/1 (Mutable, MI=1) The Shogun Let there exist the Patent Title of "Shogun". The Patent Title of Shogun is awarded automatically to a Player when e both has at least 30 Kudos and has at least as much Honour as every other Player. The Patent Title of Shogun is revoked automatically from any Player who holds it when eir Honour drops below 30 Kudos. This Patent Title shall never be awarded or revoked by Directive. The Herald shall announce in the Public Forum whenever a Player receives or loses this Title, as soon as possible after such award or revocation occurs. History: ... Amended(1) by Proposal 2502, Mar. 3 1996 ----------------------------------------