[spoon-discuss] Less Is More: Proposals

[bd <bdonlan@xxxxxxxxxxxx>]

Can anyone see any flaws in this?

{{
__Less is More: Proposals__

Create the following rule:
{{
__Less is More: Proposals__

If rule A conflicts with this rule, and A does not specify precedence over 
this rule, this rule takes precedence over rule A, unless rule A is rule 0.

A. Definitions

A.1 Revisions

 Every modification to a revisable object that does not eliminate it from play 
creates a new version of it.

 Revision numbers differentiate versions of revisable objects. Each time a 
revisable object is altered, its revision number is incremented. The initial 
revision number is 0

A.2 Serial numbers

 Every revisable object has a unique serial number, assigned by The 
Administrator. The serial number of a revisable object is defined as the 
interpolated string "n/r", where n is the object's unique identification 
number and r is the object's revision number. 

[[Example: The serial number for version 0 of Rule 101 would be 101/0, while 
the serial number for Rule 203, version 17 would be 203/17.]] 

The base identification number [[ n ]] is 100. 

Proposals, Rules and other objects requiring serial numbers, unless specified 
by the entities that create them, are assigned unique identification numbers 
that consist of the smallest integer that is larger than the largest 
identification number in use at the time of the object's creation. 
Identification numbers for Calls for Judgment cannot be specified by the 
Players creating them. 

A.3 Comments

The following two non-whitespace characters:
 
[ ]
 
are considered "reserved characters" when appearing in Official Documents in 
ways defined herein.

 Excepting any text in this section prior to and including this sentence, any 
text appearing within doubled square brackets ("[[" and "]]") shall be 
considered "comment" text. Comment text shall not have the force of Rule; its 
purpose is solely elucidative or demonstrative.

A.4 Rules & the Ruleset

 The Ruleset is the collective body of current Rule versions. The Ruleset may 
be altered only as provided therein. Rules are revisable objects.

 Every Rule must have a unique Rule number. 

A.4 Self-Reference and Self-Application in Rules

 Rule Changes that affect Rules needed to allow or apply Rule Changes are 
permissible. Even Rule Changes that amend or repeal their own authority are 
permissible. No Rule Change is impermissible solely on account of its 
self-reference or self-application.

B. Procedures

B.1 Nweekly Voting

 Voting on a nweek's Ballot opens at the start of the third to last nday of 
that nweek, and closes at the end of the last nday of that nweek. 

B.2 Proposals

 A proposal is a formal request for a set of Rule Changes or other changes to 
the game state. [[ A player could conceivably make a proposal to the effect 
of "I get 100,000 points" but this sort of thing is unlikely to pass. ]] 

Proposals are revisable. Proposals may only be revised by their original 
author. Proposals may not be revised during Voting unless the revision was 
issued before voting. A proposal is not considered "recognized" until it has 
been assigned a serial number by the Administrator. A proposal is not revised 
until the Administrator updates its serial number. 

Only players and the Administrator can make proposals. 

B.3 Eligible Voters

 Each Player is eligible to vote on a Ballot if they became a Player in the 
manner prescribed in the rules at least one full nday prior to the time at 
which Voting on that nweek's Ballot begins. Players who became a Player less 
than one full nday prior to the time at which Voting on that given nweek's 
Ballot begins may not vote until the following nweek's Voting. 

Each Player is eligible to vote on each issue on any given Ballot for the 
duration of the voting for which the Ballot was issued. 

B.4 The Ballot

 The Administrator shall, at least 48 hours prior to the close of voting each 
nweek, distribute to all Players the Ballot for that nweek. The Ballot shall 
list all proposals that were issued between the start of the previous nweek's 
voting period and the start of the current nweek's voting period. 

B.5 Vote Counting

 Each Player may cast exactly one vote on each proposal on any given Ballot. 

To cast a vote, a Player must either submit eir vote to the Administrator or 
to a Public Forum. Votes which are not publicly known shall not be revealed 
by the Administrator until voting ends, at which point they must be revealed. 
During Voting, players may change eir vote on a given issue by submitting a 
different vote for that issue. Votes may only be cast during the Voting. 

Players may abstain from voting on a given issue by not submitting a vote on 
that issue or by explicitly indicating their abstention. Explicit abstentions 
shall be treated like votes during Voting, but when Voting has ended, they 
shall be treated as if the player had not submitted a vote. 

B.6 Proposal Passage

 At the end of each voting period, after the votes on all proposals voted on 
during that voting period have been counted, the proposals that have received 
a majority of affirmative votes out of all votes they received are deemed to 
have passed. The others are deemed to have failed. All proposals that have 
been voted on during that voting period are then processed in numerical 
order. If the proposal was submitted by the player named "bd", it 
automatically passes.

Proposals are processed in numerical order. When a proposal is processed, the 
following events happen in order: 

1. If and only if the proposal passed, its actions (such as Rule Changes and 
other changes to the state of the game) are put into effect in the order in 
which they are described. 

2. Other events related to the passage or failure of the proposal, such as 
awarding or deducting points, occur. 

Proposals may not take effect retroactively. 

If the Administrator is not a player, e may veto a proposal by stating that e 
does so on a public forum. If a proposal is vetoed in this manner, but at 
least 3/4 of the votes counted for it were affirmative, the veto has no 
effect. Otherwise, the proposal is deemed to have failed. The player named 
"bd" may veto proposals in the same way as the Administrator, but without the 
requirement of not being a Player.

If a proposal would have passed, but is deemed failed *only* due to the 
Administrator's veto or bd's veto, then: 

a) The author of the proposal shall not gain or lose Charm. 

b) The author of the vetoed proposal also shall not lose points from eir 
Score, but gain nd3 points, where n is the number of yes votes received by 
the vetoed proposal minus the number of no votes received by the proposal. If 
n is greater than 5, the author shall instead receive 5d3 points. 

Any player wishing to override veto of a proposal may do so if the proposal is 
resubmitted in a subsequent nweek and at least 3/4 of the votes counted for 
it are affirmative. 

B.7 Conflict

 Each Rule has an attribute called Chutzpah, which is a positive integer. In 
the event of a conflict between two or more rules, the rule with the highest 
Chutzpah takes precedence. 

If two or more rules have equal Chutzpah, the rule with the lowest 
identification number takes precedence. 

If at least one of the rules in conflict explicity says of itself that it 
defers to another rule (or type of rule), then such provisions shall 
supersede the Chutzpah method for determining precedence. 

If two or more rules claim to take precedence over each other or to defer to 
one another, then the Chutzpah method again governs. 

Whenever one section of a rule conflicts with another section of the same 
rule, the section which appears later in the rule takes precedence over the 
earlier section. 

B.8 Proposal Scoring

 When a player's proposal passes, e recieves 3d6 points.

 When a player's proposal fails, e loses 1d6 points, unless e does not have 
that many points, in which case eir score simply becomes 0. 

All dice rolls for the purpose of scoring shall be performed by the 
Administrator. 
}}

Repeal rules 4, 5, 8, 11, 12, 15, 19, 20, 23, 30, 32, 33, and 124
}}

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