add rule 329/0 l 10 January 2001 00:00:00 Contracts P370/0 A Contract is an object. Each contract must consist of a list of signatory agents and a set of requirements placed upon those agents. Contracts are revisable objects. Their base serial number is 1000. Contracts may be created, destroyed, or otherwise altered only as specified by the rules. Signatories to a contract are required to follow all requirements and restrictions placed upon them by the text of that contract. Any contract with no signatories is automatically destroyed. ---- add rule 330/0 l 10 January 2001 00:00:00 Optional Contract Parts P370/0 A contract may optionally specify conditions under which agents may become signatories, although it may not require anything of non-signatories. A contract may optionally specify conditions under which an agent is removed from its list of signatories. A contract may specify conditions under which it is destroyed. This is equivalent to removing all signatories from its list of signatories. ---- add rule 331/0 l 10 January 2001 00:00:00 Contract Offers P370/0 An agent may create a contract offer at any time, by posting the offer to the public forum. A contract offer is an object with a title and text that describes a contract object to be created, and the activation condition for that contract. The agent creating the contract offer may destroy it at any time before the activation condition has been met. An contract offer may optionally specify which agents are eligible for the contract, either by name, serial number, or eligibility conditions. If unspecified every agent is eligible. When the activation condition is met, the described contract is created. Eligible agents who have posted eir agreement to the terms in the Public Forum are signatories to the new contract. ---- add rule 332/0 l 10 January 2001 00:00:00 Contract Restrictions P370/0 No contract may exempt any agent from any rule of this game. Contracts have only the power to require action from their signatories: they are not part of the rules of this game and never take precedence over the rules of this game. No contract may require any action from, or put limits on the action of a nonsignatory. No contract may require any transfer of property to a nonsignatory. ---- add rule 333/0 l 10 January 2001 00:00:00 Contract records P370/0 It is the responsibility of the Official Bean Counter to recognize the creation and destruction of, and changes to contracts and contract offers. A list of all contracts and their signatories; and all contract offers and their potential signatories shall be part of the Official Bean Counter's nweekly report. ---- add rule 334/0 l 10 January 2001 00:00:00 The Motion to Escape a Contract P370/0 The Motion to Escape is a Secondary motion, Approvable by four-day unanimous consent or by voting. The Motion to Escape should list one or more Agents to be released from a specified contract. The motive order corresponding to a Motion to Escape directs the Official Bean Counter to remove the specified agent or agents from the list of signatories of the specified contract. ---- add rule 230/5 l 10 January 2001 00:00:00 Unanimous Consent P371/1 An Agent introducing a Approvable Motion may request unanimous consent at the time of its introduction, or until such time as the granting of unanimous consent could still occur prior to the nweek's voting, unless the Rules explicitly prohibit it. N-unanimous consent on a Motion is granted if no eligible voters object to the Motion within time N after the Motion is recognized. Unanimous consent is considered to have been requested for any Approvable Motions which may be adopted only by unanimous consent. ---- add rule 335/0 l 10 January 2001 00:00:00 Motion Duplication P371/1 The recognition by any Officer of any Motion which would have the same effect another live Motion is prohibited. ---- add rule 336/0 l 10 January 2001 00:00:00 Challenge/response games P372/0 Each instance of a Challenge/Response Game (C/RG) is governed by this set of rules and when it is defined, must include the following attributes: game name, admin title, period of duration, repetitive or not (if yes, how often), and entry fee. It should also describe the limits and guidelines for the challenge(s) and methods by which to judge the correctness of the answers, and either specify the (first) Admin or describe how to determine who the (first) Admin is. Statements in the rule(s) defining the instance of the C/RG take preference over this rule. The Administrator of the C/RG (Admin) should post the/a Challenge to a public forum (once in each period of duration if the game is repetitive). The other Players may, if they choose, submit to the Admin an answer (response) to the challenge. Answers must be submitted privately via a time-stampable medium (e.g. e-mail) within the period of duration after the challenge was posted. Each player may submit up to one complete answer. Partial or incomplete answers (as determined by the Admin) are not considered submissions. For each answer submitted, (entry fee)*2 points shall be transferred from each submitting player to the Admin. After the period of duration after posting the challenge, the Admin will judge the answers e received and select a winner. This judgement should be made in a reasonable amount of time [[like 2 days at most]]. If more than one answer is judged (most) correct, the answer submitted earliest will be selected the winner. Half the total of the entry fees shall be transferred to the winner of the challenge [[the Admin keeps the other half]]. If the C/RG is repetitive, the winner of the challenge shall be the Admin for the following challenge. If less than 2 answers are submitted, the game is considered finished with no winner. All points taken from players as entry fees for the game are returned to their original owners. If it is a repetitive game, then the Admin does not change and play proceeds as normal for the next challenge. [[The changing paid Admin is not only an extra incentive for people to want to win, but also for the Admin to create a challenge to which a lot of people will respond.]] If the Admin fails to change after two consectutive periods of duration, a Secondary Unilateral Motion may me made naming a new (different) Admin for the game which will pass after 2 days if no objections are voiced in public fora. ---- add rule 337/0 l 10 January 2001 00:00:00 Three of these things belong together P373/0 The Similarity Game The Similarity Game is an instance of a challenge/response game with the following attributes: game name: The Similarity Game admin title: Similarity Officer duration: until repealed repetitive: yes, nweekly entry fee: 2 Once every nweek, the Similarity Officer (S.O.) should post a Challenge to a public forum. Limits and guidelines: The Challenge will take the following form: The S.O. will describe a list of items. The answer should be an attribute which is shared between all the items. Judging: More specific attributes are 'more correct' than general attributes [[e.g. 'round' is better than 'same shape']] and multiple attributes are 'more correct' than single attributes [[e.g. 'striped and round' is better than 'striped' or 'round' individually]]. first Admin: The first Admin of the game is Benjamin. [[ Three of these things belong together Three of these things are kind of the same Can you guess which one of these doesn't belong here? Now it's time to play our game! ]] ---- add rule 338/0 l 10 January 2001 00:00:00 Contests P374/0 A Contest is structure within the Game consisting of Contest Rules, Contestants, Prizes, and a Contestmaster. An Agent may become a Contestant of a Contest by publicly consenting to inclusion in it, and by meeting any other qualifications established by the Contest Rules. Contest Rules are binding on Contestants, but may not supersede any Game Rules. ----