[s-b] Emergency Management Procedure

["Peter Cooper Jr." <pete+bnomic@xxxxxxxxxxxxx>]

Since nobody else proposed one yet, and we really *ought* to have
something soon, I'm proposing this emergency management
procedure. It's quite similar to ones B Nomic has had in the past. It
should at least get us by until we want to change it.

I submit a proposal:

__Emergency Management Procedure__
{{

Create a new rule, with number 0, as follows:

__In Case of Emergency ==
{{

For the purposes of this rule, the term "Potential Emergency
Participant" (or PEP) shall mean each of the current players of the
game as defined by other rules. However, if who the current players
are in the game is unclear, uncertain, or ambiguous, or if there are
less than four such players, then it shall instead mean who the
players were before such uncertainty or drop in player count.

Each PEP has in eir possession a Game Object called a Panic Button. If
a PEP does not have such an object, a Panic Button is created and
given to em. If a PEP has more than one Panic Button, all except one
are destroyed. If an Object that is not a PEP has a Panic Button, eir
Panic Button is destroyed.

Each Panic Button has a state of being Off or On. All Panic Buttons
are initially Off.

A PEP may post a message to a Public Forum or any forum that within
the past month was a Public Forum stating that e is Hitting eir Panic
Button. If e does so, eir Panic Button becomes On.

A PEP may post a message to a Public Forum or any forum that within
the past month was a Public Forum stating that e is Stopping eir Panic
Button. If e does so, eir Panic Button becomes Off.

If there exist at least four Panic Buttons which are On, B Nomic
becomes in a State Of Emergency. When this occurs, the following
Procedure happens:

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 PEPs and an Emergency Coordinator to communicate
   (hereafter in this rule known as the "Forum"). If a Forum does not
   exist or is not available, PEPs 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 Emergency Coordinator is established. This Emergency Coordinator
   may also be a PEP and/or Administrator. If an Emergency Coordinator
   does not exist or is not available, PEPs will establish one from
   amongst themselves via the Forum. If an Emergency Coordinator
   cannot be agreed upon, the Game ends.

4. The Pause is initialized. The Procedure tracks time spent using the
   Pause. When the Emergency Coordinator is selected, 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. PEPs and the
   Emergency Coordinator may each submit a Refresh Proposal. A Refresh
   Proposal consists of a list of changes to the game which 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 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 Emergency Coordinator will gather all submitted Refresh
   Proposals into a Ballot on which PEPs will vote.

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

8. When the value of the Pause is 7, first-round votes are
   counted. The Emergency Coordinator 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 selected and the Procedure skips to
   step 12; 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 PEP 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. When the value of the Pause is 9, second-round votes are
    counted. The Emergency Coordinator 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; otherwise the Emergency Coordinator selects one of the
    Refresh Proposals.

12. All changes listed in the selected Refresh Proposal occur,
    implemented by the Emergency Coordinator as needed. All Panic
    Buttons become Off.

If at any point during the procedure, there are less than four Panic
Buttons On, the procedure stops and B Nomic stops being in a State of
Emergency, and normal Game time resumes.

}}
}}


-- 
Peter C.
_______________________________________________
spoon-business mailing list
spoon-business@xxxxxxxxx
http://lists.ellipsis.cx/mailman/listinfo/spoon-business