well if you want to do the FLR you can still deputise for rulekeepor and yoink it from PSS...
On Mon, Oct 23, 2017 at 2:36 PM, Reuben Staley <reuben.sta...@gmail.com> wrote: > As PSS has beaten me to the publishing of an SLR by deputisation, this > doesn't really count, but I tried to fix some of the errors and make it look > overall more pretty. Here it is. Please tell me of any errors I may have > made. > > ======================================================================== > > THE SHORT LOGICAL RULESET > > Most Recent Ruleset Change Recorded: > Adoption of Proposal 7929, 2017-10-22 > > Online documents: > https://agoranomic.github.io/ruleset/slr.txt (SLR) > https://agoranomic.github.io/ruleset/flr.txt (FLR) > https://agoranomic.github.io/ruleset/ (HLR, not legally part of my > report but always in sync with the other two) > > ======================================================================== > Agora > ------------------------------------------------------------------------ > > Rule 101/17 (Power=4) > The Game of Agora > > Agora is a game of Nomic, wherein Persons, acting in accordance > with the Rules, communicate their game Actions and/or results of > these actions via Fora in order to play the game. The game may be > won, but the game never ends. > > Please treat Agora Right Good Forever. > > ------------------------------------------------------------------------ > > Rule 1698/5 (Power=4) > Agora Is A Nomic > > Agora is ossified if it is IMPOSSIBLE for any reasonable > combination of actions by players to cause arbitrary rule changes > to be made and/or arbitrary proposals to be adopted within a > four-week period. > > If, but for this rule, the net effect of a proposal would cause > Agora to become ossified, or would cause Agora to cease to exist, > it cannot take effect, rules to the contrary notwithstanding. Any > other single change or inseparable group of changes to the > gamestate would cause Agora to become ossified, or would cause > Agora to cease to exist, it is cancelled and does not occur, rules > to the contrary notwithstanding. > > ------------------------------------------------------------------------ > > Rule 478/34 (Power=3) > Fora > > Freedom of speech being essential for the healthy functioning of > any non-Imperial nomic, it is hereby resolved that no Player shall > be prohibited from participating in the Fora, nor shall any person > create physical or technological obstacles that unduly favor some > players' fora access over others. > > Publicity is a forum switch with values Public, Discussion, and > Foreign (default), tracked by the Registrar. Changes to publicity > are secured. > > The Registrar may change the publicity of a forum without > objection as long as: > > 1. e sends eir announcement of intent to that forum; and > > 2. if the forum is to be made public, the announcement by which > the Registrar makes that forum public is sent to all existing > public fora. > > Each player should ensure e can receive messages via each public > forum. > > A public message is a message sent via a public forum, or sent to > all players and containing a clear designation of intent to be > public. A rule can also designate that a part of one public > message is considered a public message in its own right. A person > "publishes" or "announces" something by sending a public message. > > Where the rules define an action that CAN be performed "by > announcement", a person performs that action by unambiguously and > clearly specifying the action and announcing that e performs it. > Any action performed by sending a message is performed at the time > date-stamped on that message. Actions in messages (including > sub-messages) are performed in the order they appear in the > message, unless otherwise specified. > > ------------------------------------------------------------------------ > > ======================================================================== > Players > ------------------------------------------------------------------------ > > Rule 869/40 (Power=3) > How to Join and Leave Agora > > Any organism that is generally capable of freely originating and > communicating independent thoughts and ideas is a person. Rules > to the contrary notwithstanding, no other entities are persons. > > Citizenship is a person switch with values Unregistered (default) > and Registered, tracked by the Registrar. Changes to citizenship > are secured. A registered person is a Player. > > A person CAN (unless explicitly forbidden or prevented by the > rules) register by publishing a message that indicates reasonably > clearly and reasonably unambiguously that e intends to become a > player at that time. A person, by registering, agrees to abide by > the Rules. The Rules CANNOT otherwise bind a person to abide by > any agreement without that person's willful consent. > > A player CAN deregister (cease being a player) by announcement. If > e does so, e CANNOT register by announcement for 30 days. > > If a player has not sent a message to a public forum in the last > month, then any player CAN deregister em without objection. > > The Rules CANNOT compel non-players to act without their express > or reasonably implied consent. The rules CANNOT compel players to > unduly harass non-players. A non-person CANNOT be a player, rules > to the contrary notwithstanding. > > ------------------------------------------------------------------------ > > Rule 2139/10 (Power=2) > The Registrar > > The Registrar is an office; its holder is responsible for keeping > track of players. > > The Registrar's weekly report includes: > > 1. A list of all players, including information sufficient to > identify and contact each player. > > 2. The date on which each player most recently became a player. > > 3. For each forum with non-Foreign publicity, sufficient > instructions for players to receive messages there. > > The Registrar's monthly report includes: > > 1. For each former player for which the information is reasonbaly > available, the dates on which e registered and deregistered. > > In the first week of every month the Registrar SHALL attempt to > deregister every player that has not sent a message to a public > forum in the preceding month. > > The Registrar's duties and abilities also include: > > * Changing the publicity of a forum, as described in Rule 478. > > * Publishing Cantus Cygnei and Writs of FAGE as described in Rule > 1789. > > The Registrar is also responsible for tracking any switches, > defined in a rule, that would otherwise lack an officer to track > them, unless the switch is defined as untracked. > > ------------------------------------------------------------------------ > > Rule 1789/9 (Power=2) > Cantus Cygneus > > Whenever a Player feels that e has been treated so egregiously by > the Agoran community that e can no longer abide to be a part of > it, e may submit a document to the Registrar, clearly labeled a > Cantus Cygneus, detailing eir grievances and expressing eir > reproach for those who e feels have treated em so badly. > > In a timely fashion after receiving a Cantus Cygneus, the > Registrar shall publish this document along with a Writ of > Fugiendae Agorae Grandissima Exprobratione, commanding the Player > to be deregistered. The Registrar shall note the method of > deregistration for that Player in subsequent Registrar Reports. > > The Player is deregistered as of the posting of the Writ, and the > notation in the Registrar's Report will ensure that, henceforth, > all may know said Player deregistered in a Writ of FAGE. > > ------------------------------------------------------------------------ > > ======================================================================== > Rules & Power > ------------------------------------------------------------------------ > > Rule 2141/9 (Power=3) > Role and Attributes of Rules > > A rule is a type of instrument with the capacity to govern the > game generally, and is always taking effect. A rule's content > takes the form of a text, and is unlimited in scope. > > Every rule has power between 0.1 and 4.0 inclusive. It is not > possible for a rule to have a power outside this range. > > Rules have ID numbers, to be assigned by the Rulekeepor. > > Every rule shall have a title to aid in identification. If a rule > ever does not have a title, the Rulekeepor SHALL assign a title to > it by announcement in a timely fashion. > > For the purposes of rules governing modification of instruments, > the text, power, ID number, and title of a rule are all > substantive aspects of the rule. However, rules to the contrary > notwithstanding, the Rulekeepor CAN set rule aspects as described > elsewhere in this rule. > > ------------------------------------------------------------------------ > > Rule 1688/8 (Power=3) > Power > > The Power of an entity is a non-negative rational number. An > Instrument is an entity with positive Power. > > The Power of an entity cannot be set or modified except as > stipulated by the Rules. All entities have Power zero except where > specifically allowed by the rules. > > Power less than one is called Ephemeral power, and an instrument > with a power less than one is an Ephemeral instrument. > > A Rule that makes a change, action, or value secured (hereafter > the securing Rule) thereby makes it IMPOSSIBLE to perform that > change or action, or to set or modify that value, except as > allowed by an Instrument with Power greater than or equal to the > change's Power Threshold. This Threshold defaults to the securing > Rule's Power, but CAN be lowered as allowed by that Rule > (including by the Rule itself). > > > > ------------------------------------------------------------------------ > > Rule 2140/2 (Power=3) > Power Controls Mutability > > No entity with power below the power of this rule can > > 1. cause an entity to have power greater than its own. > > 2. adjust the power of an instrument with power greater than its > own. > > 3. set or modify any other substantive aspect of an instrument > with power greater than its own. A "substantive" aspect of an > instrument is any aspect that affects the instrument's > operation. > > ------------------------------------------------------------------------ > > Rule 217/11 (Power=3) > Interpreting the Rules > > When interpreting and applying the rules, the text of the rules > takes precedence. Where the text is silent, inconsistent, or > unclear, it is to be augmented by game custom, common sense, past > judgements, and consideration of the best interests of the game. > > Definitions and prescriptions in the rules are only to be applied > using direct, forward reasoning; in particular, an absurdity that > can be concluded from the assumption that a statement about > rule-defined concepts is false does not constitute proof that it > is true. Definitions in lower-powered Rules do not overrule > common-sense interpretations or common definitions of terms in > higher-powered rules. > > Rules to the contrary notwithstanding, any rule change that would > (1) prevent a person from initiating a formal process to resolve > matters of controversy, in the reasonable expectation that the > controversy will thereby be resolved; or (2) prevent a person from > causing formal reconsideration of any judicial determination that > e should be punished, is wholly void and without effect. > > ------------------------------------------------------------------------ > > Rule 1030/11 (Power=3.2) > Precedence between Rules > > In a conflict between Rules, the conflict shall be resolved by > performing the following comparisons in the sequence written in > this rule, until the conflict is resolved. > > - In a conflict between Rules with different Power, the Rule with > the higher Power takes precedence over the Rule with the lower > Power; otherwise, > > - 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 be used to resolve the > conflicts; otherwise, > > - 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 be used to resolve the conflict, unless they lead > to contradictions between each other; otherwise, > > - If any of the rules in conflict have ID numbers, then the Rule > with the lowest ID number takes precedence; otherwise, > > - The Rule enacted earliest takes precedence. > > Clauses in any other rule that broadly claim precedence (e.g. over > "all rules" of a certain class) shall be, prima facie, considered > to be limited claims of precedence or deference that are > applicable only when such claims are evaluated as described within > the above sequence. > > No change to the Ruleset can occur that would cause a Rule to > directly claim precedence over this Rule as a means of determining > precedence. This applies to changes by the enactment or amendment > of a Rule, or of any other form. This Rule takes precedence over > any Rule that would permit such a change to the Ruleset. > > ------------------------------------------------------------------------ > > Rule 2240/1 (Power=3) > No Cretans Need Apply > > In a conflict between clauses of the same Rule, if exactly one > claims precedence over the other, then it takes precedence; > otherwise, the later clause takes precedence. > > ------------------------------------------------------------------------ > > Rule 105/14 (Power=3) > Rule Changes > > Where permitted by other rules, an instrument generally can, as > part of its effect, > > 1. enact a rule. The new rule has power equal to the minimum of > the power specified by the enacting instrument, defaulting to > one if the enacting instrument does not specify or if it > specifies a power less than 0.1, and the maximum power > permitted by other rules. The enacting instrument may specify a > title for the new rule, which if present shall prevail. > The ID number of the new rule cannot be specified by the > enacting instrument; any attempt to so specify is null and > void. > > 2. repeal a rule. When a rule is repealed, it ceases to be a rule, > and the Rulekeepor need no longer maintain a record of it. > > 3. reenact a rule. A repealed rule identified by its most recent > rule number MUST be reenacted with the same ID number and the > next change identifier. If no text is specified, the rule is > reenacted with the same text it had when it was most recently > repealed. If the reenacting proposal provides new text for the > rule, the rule must have materially the same purpose as did the > repealed version; otherwise, the attempt to reenact the rule is > null and void. > > 4. amend the text of a rule. > > 5. retitle a rule. > > 6. change the power of a rule. > > A rule change is any effect that falls into the above classes. > Rule changes always occur sequentially, never simultaneously. > > Any ambiguity in the specification of a rule change causes that > change to be void and without effect.An inconsequential variation > in the quotation of an existing rule does not constitute ambiguity > for the purposes of this rule, but any other variation does. > > A rule change is wholly prevented from taking effect unless its > full text was published, along with an unambiguous and clear > specification of the method to be used for changing the rule, at > least 4 days and no more than 60 days before it would otherwise > take effect. > > This rule provides the only mechanism by which rules can be > created, modified, or destroyed, or by which an entity can become > a rule or cease to be a rule. > > ------------------------------------------------------------------------ > > Rule 2445/10 (Power=1) > The Propose-O-Matic > > The Fearmongor is an Office. Its holder is responsible for > ensuring the continuous change of the ruleset. > > Each month, the Fearmongor SHALL do the following as part of eir > duties: > > 1. Select two existing rules at random. For each of those rules, > submit an Official proposal with AI equal to that rules' > power. One proposal SHALL specify only to repeal its rule; > the other SHALL specify only to amend its rule. > > 2. Select a previous rule that was repealed over 1 year ago, and > has not been so selected in the past 6 months. Submit an > Official proposal of the appropriate AI to re-enact the rule > at its previous power, using any past version of the rule as a > basis and making minimal modifications to that text to allow > the rule to function in the current ruleset. > > ------------------------------------------------------------------------ > > ======================================================================== > Reusable Definitions > ------------------------------------------------------------------------ > > Rule 2152/7 (Power=3) > Mother, May I? > > The following terms are defined. These definitions are used > when a rule includes a term in all caps, and provide guidance in > determining the ordinary-language meaning of a term when a rule > includes a term otherwise. Earlier definitions take precedence > over later ones. If a rule specifies one or more persons in > connection with a term, then the term applies only to the > specified person(s). > > 1. CANNOT, IMPOSSIBLE, INEFFECTIVE, INVALID: Attempts to > perform the described action are unsuccessful. > > 2. MUST NOT, MAY NOT, SHALL NOT, ILLEGAL, PROHIBITED: Performing > the described action violates the rule in question. > > 3. NEED NOT, OPTIONAL: Failing to perform the described action > does not violate the rules. > > 4. SHOULD NOT, DISCOURAGED, DEPRECATED: Before performing the > described action, the full implications of performing it > should be understood and carefully weighed. > > 5. CAN: Attempts to perform the described action are successful. > > 6. MAY: Performing the described action does not violate the > rules. > > 7. MUST, SHALL, REQUIRED, MANDATORY: Failing to perform the > described action violates the rule in question. > > 8. SHOULD, ENCOURAGED, RECOMMENDED: Before failing to perform > the described action, the full implications of failing to > perform it should (in the ordinary-language sense) be > understood and carefully weighed. > > ------------------------------------------------------------------------ > > Rule 2162/9 (Power=2) > Switches > > A type of switch is a property that the rules define as a switch, > and specify the following: > > 1. The type(s) of entity possessing an instance of that switch. No > other entity possesses an instance of that switch. > > 2. One or more possible values for instances of that switch, > exactly one of which is designated as the default. No other > values are possible for instances of that switch. > > 3. Optionally, exactly one office whose holder tracks instances of > that switch. That officer's (weekly, if not specified > otherwise) report includes the value of each instance of that > switch whose value is not its default value; a public document > purporting to be this portion of that officer's report is > self-ratifying, and implies that other instances are at their > default value. > > At any given time, each instance of a switch has exactly one > possible value for that type of switch. If an instance of a switch > comes to have a value, it ceases to have any other value. If an > instance of a switch would otherwise fail to have a possible > value, it comes to have its default value. > > "To flip an instance of a switch" is to make it come to have a > given value. "To become X" (where X is a possible value of exactly > one of the subject's switches) is to flip that switch to X. > > If an action or set of actions would cause the value of an > instance of a switch to become indeterminate, the instance > instead takes on its last determinate and possible value, if > any, otherwise it takes on its default value. > > A singleton switch is a switch for which Agora Nomic is the only > entity possessing an instance of that switch. > > A boolean switch is a switch with values True and False. A > positive boolean switch has a default of True; a negative boolean > switch has a default of False. > > Attempting to flip an instance of a switch to a value it already > has does not flip the switch. However, if a person is REQUIRED to > flip a switch instance to a value it already has, then either > attempting to do so using the required mechanism, or announcing > that the switch already has the required value, fulfills the > requirement without flipping the switch. > > ------------------------------------------------------------------------ > Rule 2509/0 (Power=2) > Numerical Switches > > If a switch is defined as being associated with a specified set of > numbers (a numerical switch), then the possible values for that > switch are the numbers in that set. In particular, a "natural" > switch is a switch with possible values of the non-negative > integers. If a limit is further defined, the possible values are > the numbers of the set within the specified limits. > > If 0 is in the specified values for a numerical switch and no > default value is otherwise specified, 0 is the default value for > that switch. > > If the rules describe mathematical operations to be used in > flipping an instance of a numerical switch, the operations are > interpreted as having common-sense mathematical application to > determine that instance's resulting value. For example, > "increasing a switch instance by M" is equivalent to "flipping a > switch instance from its current value N to the value N+M". If the > specified mathematical operation would result in a value outside > that switch's defined set, the flipping CANNOT be performed, rules > to the contrary notwithstanding. > > ------------------------------------------------------------------------ > > Rule 2125/10 (Power=3) > Regulated Actions > > An action is restricted if: (1) the Rules limit, allow, enable, or > permit its performance; (2) describe the circumstances under which > the action would succeed or fail; or (3) the action would, as part > of its effect, modify information for which some player > is required to be a recordkeepor. > > Restricted Actions CAN only be performed as described by the > Rules, and only using the methods explicitly specified in the > Rules for performing the given action. The Rules SHALL NOT be > interpreted so as to proscribe unrestricted actions. > > ------------------------------------------------------------------------ > > Rule 1023/37 (Power=2) > Agoran Time > > The following terms are defined: > > 1. The phrase "in a timely fashion" means "within 7 days". This > time period is set when the requirement is created (i.e. X days > before the limit ends). A requirement to perform an action at > an exact instant (e.g. "when X, Y SHALL Z"), but not "in the > same message", is instead interpreted as a requirement to > perform that action in a timely fashion after that instant. > > 2. Agoran epochs: > > 1. Agoran days begin at midnight UTC. > > 2. Agoran weeks begin at midnight UTC on Monday. > > 3. Agoran months begin at midnight UTC on the first day of > each Gregorian month. > > 4. Agoran quarters begin when the Agoran months of January, > April, July, and October begin. > > 5. Agoran years begin when the Agoran month of January > begins. > > 6. A pivot is either the instant at which Agora Nomic began > (June 30, 1993, 00:04:30 GMT +1200) or an instant at > which at least one person won the game. When used as a > period of time, a "Round" (historical syn: "game") is > the period of time between a pivot and the next pivot. > > These definitions do not apply to relative durations (e.g. > "within <number> days after <event>"). > > 3. Two points in time are within a month of each other if: > > 1. they occur in the same Agoran month; > > 2. they occur in two consecutive Agoran months, and the later > of the two occurs in an earlier day in the month than the > earlier one; > > 3. they occur in two consecutive Agoran months on the same day > of the month, and the later of the two occurs at the same > or earlier time of day. > > ------------------------------------------------------------------------ > > Rule 1728/37 (Power=3) > Dependent Actions > > A rule which purports to allow a person (the performer) to perform > perform an action by a set of one or more of the following methods > (N is 1 unless otherwise specified): > > 1. Without N Objections, where N is a positive integer no greater > than 8. ("Without Objection" is shorthand for this method with > N = 1.) > 2. With N Supporters, where N is a positive integer. ("With > Support" is shorthand for this method with N = 1.) > 3. With N Agoran Consent, where N is an integer multiple of 0.1 > with a minimum of 1. > 4. With Notice. > 5. With T Notice, where T is a time period. > > thereby allows em to perform the action by announcement if all of > the following are true: > > 1. A person (the initiator) announced intent to perform the > action, unambiguously and clearly specifying the action and > method(s) (including the value of N and/or T for each method), > at most fourteen days earlier. > > 2. If the action is to be performed Without N Objections, With N > Agoran Consent, or With Notice, if the intent was announced at > least 4 days earlier > > 3. If the action is to be performed With T Notice, if the intent > was announced at least T earlier. > > 4. At least one of the following is true: > > 1. The performer is the initiator. > > 2. The initiator was authorized to perform the action due to > holding a rule-defined position now held by the > performer. > > 3. The initiator is authorized to perform the action, the > action depends on support, the performer has supported the > intent, and the rule authorizing the performance does not > explicitly prohibit supporters from performing it. > > 5. Agora is Satisfied with the announced intent, as defined by > other rules. > > 6. If a set of conditions for the performance of the action was > given in the announcement of intent to perform the action, all > those conditions are met. > > The actor SHOULD publish a list of supporters if the action > depends on support, and a list of objectors if it depends on > objections. > > ------------------------------------------------------------------------ > > Rule 2486/0 (Power=3.14) > The Royal Parade > > _ > _\ /_ > >_X_< > .---._ /_\ _.---. > /`.---._`{/ \}`_.---.`\ > | / ___`{\_/}`___ \ | > \ \."`* `"{_}"` *`"./ / > \ \ )\ _\ /_ /( / / > \ *<()( >_X_< )()>* / > |._)/._./_\._.\(_.| > jgs |() () () () () ()| > <<o>><<o>><o>><<o>> > `"""""""""""""""""""` > IN CELEBRATION of Alexis being crowned Princess of Agora, > without prejudice to Any before or since > who may come to hold a Title > whether Patent or otherwise; > IT IS HEREBY PROCLAIMED that a Royal Parade be established, > imbued in this very Rule, > which shall travel around Agora to Rules of import; > AND THEREFORE, the Rulekeepor SHOULD place this Rule > near recently-amended rules of high Power; > AND FURTHERMORE, additions to this Parade are most welcome > when Events suiting the honour should occur. > > ------------------------------------------------------------------------ > > Rule 2124/20 (Power=2) > Agoran Satisfaction > > > A Supporter of a dependent action is an eligible entity who has > publicly posted (and not withdrawn) support (syn. "consent") for > an announcement of intent to perform the action.An Objector to a > dependent action is an eligible entity who has publicly posted > (and not withdrawn) an objection to the announcement of intent to > perform the action. > > The entities eligible to support or object to a dependent action > are, by default, all players, subject to modification by the > document authorizing the dependent action.However, the previous > sentence notwithstanding, the Executor of the announcement of > intent is not eligible to support it. > > Agora is Satisfied with an intent to perform a specific action if > and only if: > > 1. if the action is to be performed Without N Objections, then it > has fewer than N objectors; > > 2. if the action is to be performed With N supporters, then it has > N or more supporters; and > > 3. if the action is to be performed with N Agoran Consent, then > the ratio of supporters to objectors is greater than N, or the > action has at least one supporter and no objectors. > > 4. if the action is to be performed With Notice or With T Notice. > > The above notwithstanding, if the action depends on objections, > and an objection to it has been withdrawn within the past 24 > hours, then Agora is not Satisfied with the intent. > > The above notwithstanding, Agora is not satisfied with the intent > if the Speaker has objected to it in the last 48 hours. > > A person CANNOT support or object to an announcement of intent > before the intent is announced, or after e has withdrawn the same > type of response. > > ------------------------------------------------------------------------ > > Rule 2466/2 (Power=3) > Acting on Behalf > > When a rule allows one person (the agent) to act on behalf of > another (the principal) to perform an action, that agent CAN > perform the action if it is POSSIBLE for the principal to do so, > taking into account any prerequisites for the action. If the > enabling rule does not specify the mechanism by which the agent > may do so, then the agent CAN perform the action in the same > manner in which the principal CAN do so, with the additional > requirement that the agent must, in the message in which the > action is performed, uniquely identify the principal and that the > action is being taken on behalf of that person. > > A person SHALL NOT act on behalf of another person if doing so > causes the second person to violate the rules. A person CANNOT act > on behalf of another person to do anything except perform a game > action; in particular, a person CANNOT act on behalf of another > person to send a message, only to perform specific actions that > might be taken within a message. > > When an action is performed on behalf of a principal, then the > action is considered for all game purposes to have been performed > by the principal, unless a rule specifically states that it is > treated differently for some purpose, in which case it is treated > as described by that rule. > > Allowing a person to act on behalf of another person is secured at > power 2.0. This rule takes precedence over any rule that would > prohibit a person from taking an action, except that it defers to > any rule that imposes limitations specifically on actions taken on > behalf of another person. > > ------------------------------------------------------------------------ > > Rule 2166/23 (Power=3) > Assets > > An asset is an entity defined as such by a (a) rule, (b) > authorized regulation, (c) group of rules and/or authorized > regulations (but if such regulations modify a preexisting asset > class defined by a rule or another title of regulations, they must > be authorized specifically to do so by their parent rule), or (d) > contract (hereafter its backing document), and existing solely > because its backing document defines its existence. An asset's > backing document can specify when and how that asset is created, > destroyed, and transferred. > > Each asset has exactly one owner. If an asset would otherwise lack > an owner, it is owned by Agora. If an asset's backing document > restricts its ownership to a class of entities, then that asset > CANNOT be gained by or transferred to an entity outside that > class, and is destroyed if it is owned by an entity outside that > class (except if it is owned by Agora, in which case any player > CAN transfer or destroy it without objection). The restrictions in > the previous sentence are subject to modification by its backing > document. > > Unless modified by an asset's backing document, ownership of an > asset is restricted to Agora, players, and contracts. As an > exception to the last sentence, non-player persons are generally > able to own assets defined by a contract they are a party to, > subject to modification by the contract in question. > > A contract's text can specify whether or not that contract is > willing to receive assets or a class of assets. Generally, a > contract CANNOT be given assets it is unwilling to receive. If the > contract is silent on the matter, or if its willingness is > indeterminate or the subject of a inextricable conditional, the > procedure to determine its willingness is as follows: > > 1. If the contract appears to anticipate being given assets, other > than for sustenance (e.g. by authorizing parties to spend the > contract's assets), then the contract is willing to receive all > assets. > 2. Otherwise, it is unwilling to receive all assets. > > The previous paragraph (including the list) notwithstanding, a > contract CAN be given 1 shiny a month for its sustenance payment, > so long as it never has more than 1 shiny at a time. > > The recordkeepor of a class of assets is the entity (if any) > defined as such by, and bound by, its backing document. That > entity's report includes a list of all instances of that class > and their owners. This portion of that entity's report is > self-ratifying. Rules to the contrary notwithstanding, a contract > CANNOT oblige a person who isn't a member to record its internal > state, nor is the default recordkeepor responsible for tracking a > contract's internal state. For the purposes of this rule, the > promulgator of a regulation is bound by it. > > An asset generally CAN be destroyed by its owner by announcement, > subject to modification by its backing document. An indestructible > asset is one defined as such by it backing document, and CANNOT > be destroyed except by a rule, other than this one, specifically > addressing the destruction of indestructible assets or that asset > in particular; any other asset is destructible. In circumstances > where another asset would be destroyed, an indestructible asset is > generally transferred to Agora, subject to modification by its > backing document and the intervention of other rules. > > To "lose" an asset is to have it destroyed from one's possession; > to "revoke" an asset from an entity is to destroy it from that > entity's possession. > > An asset generally CAN be transferred (syn. paid, given) by > announcement by its owner to another entity, subject to > modification by its backing document. A fixed asset is one defined > as such by its backing document, and CANNOT be transferred; any > other asset is liquid. > > When a rule indicates transferring an amount that is not a natural > number, the specified amount is rounded up to the nearest natural > number. > > A currency is a class of asset defined as such by its backing > document. Instances of a currency with the same owner are > fungible. > > The "x balance of an entity", where x is a currency, is the number > of x that entity possesses. If a rule, proposal, or other > competent authority attempts to increase or decrease the balance > of an entity without specifying a source or destination, then the > currency is created or destroyed as needed. > > When a player causes one or more balances to change, e is > ENCOURAGED to specify the resulting balance(s). Players SHOULD NOT > specify inaccurate balances. > > Where it resolves ambiguity, the asset or currency being referred > to is the currency designated as "Agora's official currency", if > there is one. > > An asset or class of assets is private, rather than public, if its > backing document is a contract. > > ------------------------------------------------------------------------ > > Rule 2515/0 (Power=1) > Distributing Assets > > To "distribute" a quantity of a fungible asset to a set of > recipients is to transfer one instance of that asset at a time to > the recipient that owns the least number of instances of that > asset, until either no more instances of the asset are eligible to > be distributed, or the number of instances so transferred equals > the quantity to be distributed. If, when distributing a specific > asset, two or more recipients each own the least number of > instances of that asset, then the recipient that most recently > became eligible to own the asset SHALL receive the asset being > distributed. > > ------------------------------------------------------------------------ > > Rule 2493/2 (Power=3.1) > Regulations > > A Regulation is an textual entity defined as such by this rule. A > regulation allows an officer (known as the Promulgator) to > exercise rule defined powers. A regulation is in effect > continuously from the time of its creation to the time of either > its revocation or the repeal of the rule that allowed for its > creation. When recommending a regulation, its Promulgator must > specify by number the rule(s) upon which it is based (the parent > rules), the list of which becomes an integral part of the > regulation. The list of rules can generally be modified by the > Promulgator according to the procedure for text changes. > > A regulation must be authorized by at least one rule in order for > it to exist. A regulation has effect on the game (only) insofar as > the rule or rules that authorized it permit it to have effect. If > reasonably possible, a regulation should be interpreted so as to > defer to other rules. The procedure for resolving conflict between > regulations is the same as it is for rules (for the purposes of > resolving conflicts only, a regulation is treated as if it had the > power of its least powerful parent rule). > > Regulations are generally issued according to the following > procedures, and they can be repealed by the announcement of their > Promulgator. Alternate procedures may be used if provided for by > all of the regulations's parent rules. If one parent rule > specifies procedures that are more stringent than those that the > other(s) specifies, those apply. Creating, modifying, revoking, or > allowing for a regulation is secured at power 1. > > A regulation (or set of regulations), authorized by another rule, > CAN generally be enacted or modified by its promulgator without 2 > objections, or with Agoran consent. A notice pursuant to the to > the previous sentence is known as a "recommendation", and the > regulation(s) are said to be "recommended" to Agora. > > ------------------------------------------------------------------------ > > Rule 2494/0 (Power=1) > The Regkeepor > > The Regkeepor is an office, responsible for the maintenance of the > Regulations. The Regulations are contained in the Regkeepor's > weekly report, know as the Agora Nomic Code of Regulations > (ACORN). E MAY publish multiple versions or editions of the ACORN. > > The ACORN is divided into titles, assigned by the Regkeepor, which > are each given an integer. Generally, each office with the power > to create regulations SHOULD be assigned the next successive > natural number. Title 0 of the ACORN is reserved for use by the > Regkeepor, and nothing in that title need be a regulation. > Non-regulations printed in the ACORN have no binding effect, and > SHALL clearly be marked by the Regkeepor. > > Each regulation SHALL be assigned an ID number by the Regkeepor, > consisting of a string of the characters [0-9] and separator > characters. The Regkeepor SHOULD establish some way of keeping > track of the version of a regulations. The Regkeepor MAY also, at > eir discretion, create ways of marking special types of Regulation > (even in violation of the previous restrictions of this > paragraph), mark sections or titles as reserved for future use, > and make such other discussions of arrangement, annotation, and > marking as are necessary and proper in the execution of eir > duties. > > The Regkeepor SHOULD remember that the purpose of the ACORN is to > make the regulations easily readable, and e SHALL not act in a > manner intended to deceive others in eir official capacity. > > ------------------------------------------------------------------------ > > Rule 2505/0 (Power=1.0) > Random Choices > > When a Rule specifies that a random choice be made, then the > choice shall be made using whatever probability distribution among > the possible outcomes the Rule specifies, defaulting to a uniform > probability distribution. > > The choice CAN be made using any physical or computational process > whose probability distribution among the possible outcomes is > reasonably close to that required by the Rules, and for which the > final choice is not trivially predictable by the selecting person > in advance.The selecting person SHOULD make the selection method > public, and SHOULD use a method for which the final probability > distribution can be readily confirmed. > > ------------------------------------------------------------------------ > > Rule 2500/0 (Power=1) > Action Points > > At the beginning of every Agoran Week, every player has 2 Action > Points. When a player 'spends' an Action Point, e has one less > Action Point. If a player has 0 Action Points, e may not spend any > more Action Points, rules to the contrary notwithstanding. > > ------------------------------------------------------------------------ > > Rule 2517/0 (Power=3) > Conditionals and Extricability > > A conditional is any textual structure that attempts to make a > statement (the substrate) affecting any part or aspect of the > gamestate, or the permissibility, possibility, or effect of any > action affecting such a part or aspect, dependent on the truth > value or other state of a textual structure (the condition). The > condition is said to be "affixed" to the substrate (inverse "to be > conditional upon"). > > A condition is inextricable if it is unclear, ambiguous, circular, > inconsistent, paradoxical, depends on information that is > indeterminate, or is impossible or unreasonably difficult to > determine, or otherwise requires an unreasonable effort to > resolve; otherwise it is extricable. A conditional is inextricable > if its condition is inextricable; otherwise it is extricable. A > player SHOULD NOT use an inextricable conditional for any purpose. > > An action is said to be "subject to" a conditional if its > possibility, permissibility, or effect (depending on context) is > determined by the conditional. A value is said to be subject to a > conditional of the state of the value is determined by the > conditional. > > ------------------------------------------------------------------------ > > Rule 2518/0 (Power=3) > Determinacy > > If a value CANNOT be reasonably determined (without circularity or > paradox) from information reasonably available, or if it > alternates indefinitely between values, then the value is > considered to be indeterminate, otherwise it is determinate. > > ------------------------------------------------------------------------ > > Rule 1586/9 (Power=2) > Definition and Continuity of Entities > > If multiple rules attempt to define an entity with the same name, > then they refer to the same entity. A rule-defined entity's name > CANNOT be changed to be the same as another rule-defined entity's > name. > > A rule, contract, or regulation that refers to an entity by name > refers to the entity that had that name when the rule first came > to include that reference, even if the entity's name has since > changed. > > If the entity that defines another entity is amended such that it > no longer defines the second entity, then the second entity and > its attributes cease to exist. > > If the entity that defines another entity is amended such that it > defines the second entity both before and after the amendment, but > with different attributes, then the second entity and its > attributes continue to exist to whatever extent is possible under > the new definitions. > > ------------------------------------------------------------------------ > > Rule 2519 (Power=3) > Consent > > A person gives consent (syn. consents) to an action when e, acting > as emself, publicly states that e agrees to the action. This > agreement may be implied, but only if it is reasonably clear from > context that the person wanted the agreement to take place. > > ======================================================================== > Proposals > ------------------------------------------------------------------------ > > Rule 2350/9 (Power=3) > Proposals > > A proposal is a type of entity consisting of a body of text and > other attributes. A player CAN create a proposal by > announcement, specifying its text and optionally specifying any > of the following attributes: > > - An associated title. > - A list of co-authors (which must be persons other than the > author). > - An adoption index. > > Creating a proposal adds it to the Proposal Pool. Once a proposal > is created, nether its text nor any of the aforementioned > attributes can be changed. The author (syn. proposer) of a > proposal is the person who submitted it. > > If a decision of whether to adopt a proposal was resolved as > FAILED QUORUM in the last seven days, the Promotor CAN once add > the proposal back to the Proposal Pool by announcement. > > The author of a proposal in the Proposal Pool CAN remove (syn. > retract, withdraw) it from the Pool by announcement. > > The Promotor CAN remove a proposal from the Proposal Pool by > announcement if it is not pending and has been added to the Pool > more than 14 days ago. > > > ------------------------------------------------------------------------ > > Rule 2445/10 (Power=1) > How to Pend a Proposal > > Imminence is a switch, tracked by the Promotor, possessed by > proposals in the Proposal Pool, whose value is either "pending" or > "not pending" (default). > > Any player CAN flip a specified proposal's imminence to "pending" > by announcement by: > > a) spending 1 Action Point, OR > > b) spending the current Pend Cost in shinies > > An Official Proposal is a proposal designated as such by the > Rules; generally official proposals that are created as part of an > Officer's duties. Rules to the contrary notwithstanding, an > Official proposal is always pending. Rules to the contrary > notwithstanding, players CANNOT claim rewards for the adoption of > an Official proposal. > > ------------------------------------------------------------------------ > > Rule 1607/45 (Power=3) > Distribution > > The Promotor is an office; its holder is responsible for receiving > and distributing proposals. > > Determining whether to adopt a proposal is an Agoran decision. For > this decision, the vote collector is the Assessor, the adoption > index is initially the adoption index of the proposal, or 1.0 if > the proposal does not have one, and the text, author, and > coauthors of the proposal are essential parameters. Initiating > such a decision is known as distribution, and removes the proposal > from the Proposal Pool. > > The Promotor CAN distribute a proposal which is in the Proposal > Pool at any time, by announcement. The Promotor SHALL NOT > distribute proposals which are not pending. > > In a given Agoran week, the Promotor SHALL, as part of eir weekly > duties, distribute all pending proposals except for those exempted > from automatic distribution by other rules. > > Distributed proposals have ID numbers, to be assigned by the > Promotor. > > If there is a Proposal in the Pool that it would otherwise be > IMPOSSIBLE for any player to distribute, then any player CAN > distribute that Proposal Without 3 Objections. > > The Promotor's report includes a list of all proposals in the > Proposal Pool, along with their text and attributes.This portion > of a public document purporting to be a Promotor's report is > self-ratifying. > > ------------------------------------------------------------------------ > > Rule 2137/2 (Power=1) > The Assessor > > The Assessor is an office; its holder is responsible for > collecting votes and keeping track of related properties. > > ------------------------------------------------------------------------ > > Rule 106/36 (Power=3) > Adopting Proposals > > When a decision about whether to adopt a proposal is resolved, if > the outcome is ADOPTED, then the proposal in question is adopted, > and unless other rules prevent it from taking effect, its power is > set to the minimum of four and its adoption index, and then it > takes effect.Except as prohibited by other rules, a proposal that > takes effect CAN and does, as part of its effect, apply the > changes that it specifies.If the proposal cannot make some such > changes, this does not preclude the other changes from taking > place. > > If there is no Agoran Decision to adopt a particular proposal that > has an outcome of ADOPTED, that proposal CANNOT take effect, rules > to the contrary notwithstanding. > > Preventing a proposal from taking effect is a secured change; this > does not apply to generally preventing changes to specified areas > of the gamestate, nor to a proposal preventing itself from taking > effect (its no- effect clause is generally interpreted as applying > only to the rest of the proposal). > > ------------------------------------------------------------------------ > > Rule 2443/1 (Power=3) > Expediting Proposals > > A player CAN expedite a proposal whose adoption index is at most > 1.5, in a message containing the character string "[Expedition]" > in the subject line, > > 1. by specially deputising for the Promotor to distribute the > proposal, if it has not been distributed; or > 2. by announcement, otherwise. > > If, in an Agoran Decision to adopt a proposal, the strength of > AGAINST is zero, and the proposal was expedited at least 7 days > earlier, then any player CAN specially deputise for the Assessor > to resolve the decision. > > ------------------------------------------------------------------------ > > Rule 2431/1 (Power=1) > Proposal Competitions > > Any player CAN, with Agoran Consent, initiate a Proposal > Competition with a specified Objective. Only one Competition may > be in progress at a time. The Objective should be a > specification of effects of a proposal, and SHOULD NOT depend on > factors that could not be determined from the text of a > proposal. > > During the Agoran Week following the initiation of a Proposal > Competition, any player CAN specify that a Proposal e submits is > a Competition Proposal for that Competition. Players are > ENCOURAGED to describe how their Competition Proposals fulfill > the Objective. > > The Promotor SHALL distribute all Competition Proposals for a > given Competition in the same message. The Assessor SHALL > resolve all the Agoran Decisions to adopt the Competition > Proposals for a given Competition in the same message. > > Once all Agoran decisions to adopt Competition Proposals for a > given Competition have been resolved, the Competition ends. > > ------------------------------------------------------------------------ > > Rule 1650/2 (Power=1) > Silliness > > Each Nomic Week a Player is designated the Silly Person. The Silly > Person SHALL in that week, by announcement (1) designate another > player, who has not been the Silly Person in the past two weeks, > to be the next week's Silly Person; (2) submit a Silly Proposal. > If there is ever no Silly Person or the Silly Person is not a > player, then the next week's Silly Person is the first player that > any player publicly designates to be the next week's Silly Person. > > A Silly Proposal is a Proposal whose sole contents are one of the > following: > > i) A limerick. > ii) A rhymed poem no longer than fourteen lines. (No free > verse!) > iii) A joke of no more than a hundred words. > iv) A truly hideous pun. > > The first Silly Proposal submitted by the week's Silly Person is > an Official Proposal. > > ------------------------------------------------------------------------ > > ======================================================================== > Voting & Elections > ------------------------------------------------------------------------ > > Rule 693/16 (Power=3) > Agoran Decisions > > When the rules calls for an Agoran decision to be made, the > decision-making process takes place in the following three stages, > each described elsewhere: > > 1. Initiation of the decision. > 2. Voting of the people. > 3. Resolution of the decision. > > ------------------------------------------------------------------------ > > Rule 107/19 (Power=3) > Initiating Agoran Decisions > > An Agoran decision is initiated when a person authorized to > initiate it publishes a valid notice which sets forth the intent > to initiate the decision. This notice is invalid if it lacks any > of the following information, and the lack is correctly identified > within one week after the notice is published: > > 1. The matter to be decided (for example, "the adoption of > proposal 4781"). > > 2. A clear indication of the set of valid votes. > > 3. The identity of the vote collector. > > 4. Any additional information defined by the rules as essential > parameters. > > The publication of such a valid notice initiates the voting period > for the decision. The voting period lasts for 7 days. The minimum > voting period for a decision with at least two options is five > days. The vote collector for a decision with less than two options > CAN and SHALL end the voting period by announcement, if it has not > ended already, and provided that e resolves the decision in the > same message. > > The voting period for a decision cannot be set or changed to a > duration longer than fourteen days. > > > ------------------------------------------------------------------------ > > Rule 683/25 (Power=3) > Voting on Agoran Decisions > > An entity submits a ballot on an Agoran decision by publishing a > notice satisfying the following conditions: > > 1. The ballot is submitted during the voting period for the > decision. > > 2. The entity casting the ballot (the voter) was, at the > initiation of the decision, a player. > > 3. The ballot clearly identifies the matter to be decided. > > 4. The ballot clearly identifies a valid vote, as determined by > the voting method. > > 5. The ballot clearly sets forth the voter's intent to place > the identified vote. > > 6. The voter has no other valid ballots on the same decision. > > A valid ballot is a ballot, correctly submitted, that has not been > withdrawn. During the voting period of an Agoran decision, a > player CAN by announcement withdraw (syn. retract) a ballot that e > submitted on that decision. To "change" one's vote is to retract > eir previous ballot (if any), then submit a new one. > > > ------------------------------------------------------------------------ > > Rule 208/12 (Power=3) > Resolving Agoran Decisions > > The vote collector for an unresolved Agoran decision CAN resolve > it by announcement, indicating the outcome. If it was required > to be initiated, then e SHALL resolve it in a timely fashion > after the end of the voting period. To be valid, this > announcement must satisfy the following conditions: > > 1. It is published after the voting period has ended. > > 2. It clearly identifies the matter to be resolved. > > 3. It specifies the outcome, as described elsewhere, and, if > there was more than one valid option, provides a tally of > the voters' valid ballots. > > Each Agoran decision has exactly one vote collector, defaulting > to the initiator of the decision. If the vote collector is > defined by reference to a position (or, in the default case, if > the initiator was so defined), then the vote collector is the > current holder of that position. > > This rule takes precedence over any rule that would provide > another mechanism by which an Agoran decision may be resolved. > > In general, changes to the gamestate due to the outcome of an > Agoran decision take effect when the decision is resolved. > > ------------------------------------------------------------------------ > > Rule 955/23 (Power=3) > Determining the Will of Agora > > Each Agoran decision has a voting method, which determines how > voters may vote on it and how to calculate the outcome. The > strength of a ballot is the voting strength of the voter who cast > it on that Agoran decision. > > The following voting methods are defined: > > 1. AI-majority: the valid votes are FOR and AGAINST. Let F be > the total strength of all valid ballots cast FOR a decision, > A be the same for AGAINST, and AI be the adoption index of > the decision. The outcome is ADOPTED if F/A >= AI and F/A > > 1 (or F>0 and A=0), otherwise REJECTED. > > 2. Instant runoff: the valid votes are ordered lists of > options, and the outcome is whichever option wins according > to the standard definition of instant runoff. For this > purpose, a ballot of strength N is treated as if it were N > distinct ballots expressing the same preferences. In case > multiple valid options tie for the lowest number of votes at > any stage, the vote collector CAN and must, in the > announcement of the decision's resolution, select one such > option to eliminate; if, for M > 1, all eir possible choices > in the next M stages would result in the same set of options > being eliminated, e need not specify the order of > elimination. > > 3. First-past-the-post (default): the valid votes are the > options, and the outcome is whichever option received the > highest total strength of valid ballots. In case of a tie, > the vote collector CAN and must, in the announcement of the > decision's resolution, select one of the leaders as the > outcome. > > The previous notwithstanding: > > - If there is more than one option, and the number of valid > ballots is less than the quorum of that decision, the outcome > is instead FAILED QUORUM. > - PRESENT is always a valid vote, with no effect on the outcome > except counting towards quorum. > - If there are no valid options, the outcome is null. > > The outcome of a decision is determined when it is resolved, and > cannot change thereafter. > > The rule providing for an Agoran Decision by instant runoff may > disqualify one or more options; in such a case, they are > eliminated prior to beginning the first stage of the vote count. > > ------------------------------------------------------------------------ > > Rule 879/33 (Power=2) > Quorum > > Each Agoran Decision has a quorum. This is a number set when the > decision is created, and thereafter cannot be changed. When a > person initiates an Agoran Decision, that person SHALL state the > quorum of that decision. However, incorrectly stating the quorum > of a decision does not invalidate the initiation, nor does it > actually change the quorum of the decision. > > The quorum that an Agoran Decision gains as it is created can be > defined by other rules of power 2 or greater. If no other rule > defines the quorum of an Agoran Decision, the quorum for that > decision is equal to the number of players who voted on the Agoran > Decision to adopt a proposal that had been most recently resolved > at the time of that decision's initiation, minus 2. > > As an exception to the previous paragraph, the quorum of an Agoran > Decision can never be less than 2. If the rules would attempt to > set the quorum of an Agoran Decision to less than 2, it is set to > 2 instead. > > ------------------------------------------------------------------------ > > Rule 2422/2 (Power=3) > Voting Strength > > The voting strength of an entity on an Agoran decision is an > integer between 0 and 5 inclusive, defined by rules of power 2 or > greater. If not otherwise specified, the voting strength of an > entity on an Agoran decision is 1. > > When multiple rules set or modify an entity's voting strength on > an Agoran decision, it shall be determined by first applying the > rule(s) which set it to a specific value, using the ordinary > precedence of rules, and then applying the rules, other than this > one, which modify it, in numerical order by ID. Finally, if > theresult of the calculation is not an integer, it is rounded up, > and then if it is outside the allowable range of values for voting > strength, it is set to the the minimum value if it was less and > the maximum value if it was more. > > ------------------------------------------------------------------------ > > Rule 2127/9 (Power=3) > Conditional Votes > > If a vote on an Agoran decision is submitted conditionally (e.g. > "FOR if <X> is true, otherwise AGAINST"), then the selected option > is evaluated based on the value of the condition(s) at the end of > the voting period, and, rules to the contrary notwithstanding, is > clearly specified if and only if the value of the condition(s) > is/are determinate at the end of the voting period. If the option > cannot be clearly identified, a vote of PRESENT is cast. > > Casting a vote endorsing another voter is equivalent to > conditionally casting a vote whose value is the same as the most > common value (if any) among that voter's valid votes on that > decision. > > Casting a vote denouncing another voter is equivalent to > conditionally casting a vote whose value is opposite to the most > common value (if any) among that voter's valid votes on that > decision. FOR and AGAINST are opposites. > > ------------------------------------------------------------------------ > > Rule 2168/7 (Power=1) > Extending the Voting Period > > Whenever the voting period of an Agoran decision would end, and > the result would be FAILED QUORUM, the length of the voting period > for that decision is instead increased to 14 days, except if it is > already that length, provided this has not already happened for > the decision in question. > > Upon such an occurrence, the vote collector for the decision SHALL > issue a humiliating public reminder to the slackers who have not > yet cast any votes on it despite being eligible, and CAN end its > voting period by announcement (resolving it constitutes an > implicit announcement that its voting period is first ended) if > the result would no longer be FAILED QUORUM, or if the decision is > whether to adopt a proposal and no voter (other than possibly the > proposal's author) has voted FOR. > > ------------------------------------------------------------------------ > > Rule 1950/32 (Power=3) > Decisions with Adoption Indices > > Adoption index is an untracked switch possessed by Agoran > decisions and proposals, whose value is either "none" (default) or > an integral multiple of 0.1 from 1.0 to 9.9. > > Adoption index is secured with a power threshold of 2. > > Adoption index is an essential parameter of an Agoran decision if > that decision has an adoption index. > > For any Agoran decision with an adoption index, the voting method > is AI-majority. > > ------------------------------------------------------------------------ > > Rule 2034/9 (Power=3) > Vote Protection and Cutoff for Challenges > > A public message purporting to resolve an Agoran decision > constitutes self-ratifying claims that: > > 1. such a decision existed, > 2. it was resolved as indicated, and > 3. (if the indicated outcome was to adopt a proposal) such a > proposal existed, was adopted, and took effect. > > ------------------------------------------------------------------------ > > Rule 2154/51 (Power=2) > Election Procedure > > A player CAN initiate an election for a specified office: > > 1. With 2 Support, if either the office is interim or the most > recent election for that office was resolved more than 90 days > prior, and provided that the initiator becomes a candidate in > the same message. > 2. By announcement, if e is the ADoP and if the office is interim, > or if e is the holder of that office. > > The above notwithstanding, an election for an office CANNOT be > initiated if one is already in progress. > > After an election is initiated and until nominations close, any > player CAN become a candidate by announcement. A candidate ceases > to be a candidate if e ceases to be a player during the election. > An election is contested if it has two or more candidates at the > end of the nomination period, and uncontested otherwise. For a > contested election, nominations close at the end of the poll's > voting period. For an uncontested election, nominations close at > the end of the nomination period. > > When an election is initiated, it enters the nomination period, > which lasts for 7 days. In a timely fashion after the nomination > period ends, the ADoP CAN and SHALL, in the same message: > > 1. If the election is contested, initiate an Agoran decision to > select the winner of the election (the poll). For this > decision, the Vote Collector is the Assessor, the valid options > are the candidates for that election (including those who > become candidates after its initiation), and the voting method > is instant runoff. > 2. Distribute all pending Campaign Proposals associated with the > election. > 3. If POSSIBLE per the following paragraph, end the election > immediately. > > If at any point an uncontested election has a single candidate, > and that candidate either is not the author of a Committed Campaign > Proposal for that election or that proposal was adopted, then any > player CAN declare them the winner of the election by > announcement. If at any point an uncontested election has no > candidates, or a single candidate who is the author of a failed > Committed Campaign Proposal for that election, then any player CAN > declare the election ended with no winner by announcement. The > Assessor SHALL do one or the other in the same message in which e > resolves a decision to adopt a Campaign Proposal for an ongoing > uncontested election. > > A poll CANNOT be resolved until the decisions to adopt all > associated Campaign Proposals are resolved. When resolving the > poll, if a given candidate authored one of the associated > Campaign Proposals, that proposal is Committed, and it was not > adopted, then that player is disqualified. > > When the poll is resolved, its outcome, if a player, wins the > election. When a player wins an election, e is installed into the > associated office and the election ends. > > ------------------------------------------------------------------------ > > Rule 2513/0 (Power=3) > Campaign Proposals > > During the nomination period of an election, any candidate for > that election CAN submit a Campaign Proposal for that election, > provided e does not currently have a pending Campaign Proposal for > that election, using the normal mechanism for proposal submission. > Campaign Proposals SHOULD relate to the duties of the office up > for election. Commitment is an untracked Campaign Proposal switch > with values Committed (default) and Uncommitted. The author of a > Committed proposal may flip it to Uncommitted by announcement. > > A Campaign Proposal is an Official Proposal exempt from automatic > distribution, and SHALL NOT be distributed as required by the > rules. The election with which a Campaign Proposal is associated, > as well as its Commitment, are essential parameters for an Agoran > decision to adopt a Campaign Proposal. > > When a Campaign Proposal is adopted, it CANNOT take effect until > the associated election ends. When the election ends, if the > winner was the proposal's author, then any player CAN once make it > take effect by announcement (with its power set as usual for an > adopted proposal). If the conditions for a Campaign Proposal to > take effect are met as a result of an action in a public message, > the author of the message SHALL make it take effect in that > message. > > ------------------------------------------------------------------------ > > ======================================================================== > Offices & Reporting > ------------------------------------------------------------------------ > > Rule 1006/39 (Power=2) > Offices > > Officeholder is an office switch tracked by the ADoP, with > possible values of any person or "vacant". An officer is the > holder of an office, who may be referred to by the name of that > office. If the holder of an office is ever not a player, it > becomes vacant. > > An imposed office is an office described as such by the rule > defining it. All others are elected. A person CANNOT be made the > holder of an elected office without eir explicit or reasonably > implied consent. > > A holder of an elected office who did not become its holder by > winning an election, and has not won an election for that office > since, is an interim holder. An elected office that is either > vacant or has an interim holder is an interim office. > > The holder of an elected office CAN resign it by announcement, > causing it to become vacant. Any player CAN cause an office to > become vacant without 2 objections. > > When a proposal takes effect and creates a new office, if the > proposal does not specify otherwise, the author of that proposal > becomes the holder of the office. > > ------------------------------------------------------------------------ > > Rule 2143/26 (Power=1) > Official Reports and Duties > > For each person: > > 1. If any task is defined by the rules as part of that person's > weekly duties, then e SHALL perform it at least once each > week. If any information is defined by the rules as part of > that person's weekly report, then e SHALL maintain all such > information, and the publication of all such information is > part of eir weekly duties. > > 2. If any task is defined by the rules as part of that person's > monthly duties, then e SHALL perform it at least once each -- >From V.J. Rada
