spoon-business: Revised ptime proposal

["Donald Whytock" <dwhytock@xxxxxxxxxxxxx>]

Okay, I held a seance and asked Dad the Lawyer how I should go about the proposal.  He came up with something, but because y'all don't recognize noncorporeal players I'll just have to shamelessly take full credit for it myself...

{{ _The Pause that Refreshes_

Create the following rule with serial number 0:

{{ _Emergency Management_

There exists, in the context of the game that contains this rule (hereafter in this rule known as "The Game"), a procedure called the Emergency Management procedure.  The Emergency Management procedure (hereafter in this rule known as "The Procedure") will be followed in the event of an Emergency, as recognized by the majority of the most recently formally recognized body of players in The Game.

An Emergency, in the context of this rule, is any event or circumstance, not already provided for in the rules of the Game, that prevents the continuance of the Game.  Emergencies include, but are not limited to, the following:

- The failure of, or lack of access to, the hosting services and/or equipment used to administer the Game (hereafter in this rule known as "The Host") for a period of seven days.

- The failure of, or absence of, the person recognized as performing the administrative duties of the Game (hereafter in this rule known as "The Administrator") for a period of seven days.

- The existence of a paradoxical condition that cannot be resolved under the current set of rules.

The Procedure is as follows:

1. Game time is stopped.  Whatever means used in the Game to track time is stopped as of the beginning of the Emergency.  Pending events and deadlines relative to Game time, with the exception of those specified in this rule, are postponed until Game time resumes.  Pending events and deadlines with absolute dates and times do not occur.

2. A Forum is established.  The Procedure depends upon the availability of a means for players and an Administrator to communicate (hereafter in this rule known as "The Forum").  If a Forum does not exist or is not available, players will establish one by contacting one another and agreeing upon a new Forum.  If a new Forum cannot be agreed upon, the Game ends.

3. An Administrator is established.  If an Administrator does not exist or is not available, players will establish one from amongst themselves via the Forum.  If an Administrator cannot be agreed upon, the Game ends.

4. The Pause is initialized.  The Procedure tracks time spent using the Pause.  When the Procedure is begun, the Pause is zero; thereafter, until the completion of the Procedure, the Pause is increased by one each day at 00:00:00 UTC.

5. Refresh Proposals are submitted.  The Forum will be used to submit, discuss, select and implement proposed changes to the state of the Game (hereafter in this rule known as "Refresh Proposals") for the purpose of either resuming or ending the Game.  Players and the Administrator may each submit a Refresh Proposal.  Refresh Proposals may affect any aspect of the Game or the state of the Game, including, but not limited to: rules, scores or other player attributes, the valid list of players, the identity of the Host or the Administrator, the legitimacy and/or actuality of any action taken in the context of the Game, etc.

6. A first-round Ballot is formed.  When the value of the Pause is 5, the Administrator will gather all submitted Refresh Proposals into a Ballot on which players will vote.

7. First-round votes are cast.  Each player and the Administrator casts a single vote to select one of the Refresh Proposals in the Ballot.  Votes are cast by announcing them via the Forum.

8. First-round votes are counted.  When the value of the Pause is 7, the Administrator will count all the submitted votes and announce to the Forum which Refresh Proposal received the largest number of votes.  If only one Refresh Proposal received the largest number of votes, it is implemented by the Administrator and the Procedure ends; otherwise the Procedure continues to Step 9.

9. A second-round Ballot is formed. Refresh Proposals that tied for the largest number of votes received in the prior Ballot will be gathered into a second Ballot on which players will vote.

10. Second-round votes are cast.  Each player and the Administrator casts a single vote to select one of the Refresh Proposals in the second Ballot.  Votes are cast by announcing them via the Forum.

11. Second-round votes are counted.  When the value of the Pause is 9, the Administrator will count all the submitted votes and announce to the Forum which Refresh Proposal in the second Ballot received the largest number of votes.  If only one Refresh Proposal received the largest number of votes, it is selected for implementation; otherwise the Administrator selects one of the Refresh Proposals.

12. Selected Refresh Proposal is implemented.  The Refresh Proposal selected from the second Ballot is implemented by the Administrator and the Procedure ends.

}}

}}