Home

[Proposals 301-325] [Proposals 326-350] [Proposals 351-375] [Proposals 376-400] [Proposals 401-425] [Proposals 426-450] [Proposals 451-475]

Proposal 351/0 : AWAY players - slight change
Change the second sentence of rule 307 to read as follows:

If at any time a player has not voted in the last three nweeks the Administrator shall, within a reasonable amount of time, grant them the [Away] attribute by posting a message to that effect to the public forum.

0. Poulenc made a Proposal [351], 23 Nov 2000 17:23:28
0. Administrator recognized Proposal 351/0, 23 Nov 2000 19:14:00
0. Proposal 351/0 passed (5-3-1-3), 01 Dec 2000 00:00:00

Proposal 352/0 : Salaries for Officers and Judges
Enact a new rule with the title "Salaries for Officers and Judges" and with text as follows:

The Offical Salary and the Judicial Salary are values associated with this game. They may be changed only as specified by the rules. Initially, the value of each is zero.

At the end of each nweek the Banker shall, within a reasonable length of time, transfer a number of points equal to the Official Salary from the Bank to the holder each elective office and the Administrator. E shall not transfer more points than one Official Salary to any agent, even if that agent holds more than one office.

When a judge returns a judgement, the Banker shall transfer a number of points equal to the Judicial Salary from the Bank to that judge.

Once per nweek, with a post to the public forum the Banker may set the values of the Official Salary and the Judicial Salary such that the value of each is neither less than zero nor greater than twenty.

Proposal 352/1 : Salaries for Officers and Judges

Enact a new rule with the title "Salaries for Officers and Judges" and with text as follows:

The Offical Salary and the Judicial Salary are values associated with this game. They may be changed only as specified by the rules. Initially, the value of each is zero.

At the end of each nweek, the bank owes one Official Salary, in points, to each agent who hold one or more paid offices. An agent that holds multiple offices cannot recieve more that one Official Salary.

When a judge returns a judgement, the bank owes one Judicial Salary to em.

Once per nweek, with a post to the public forum, the Banker may set the values of the Official Salary and the Judicial Salary such that the value of each is neither less than zero nor greater than twenty.

Proposal 352/2 : Salaries for Officers and Judges

Enact a new rule with the title "Salaries for Officers and Judges" and with text as follows:

The Offical Salary and the Judicial Salary are values associated with this game. They may be changed only as specified by the rules. Initially, the value of each is zero.

At the end of each nweek, the bank owes one Official Salary, in points, to each agent who holds one or more paid offices. An agent that holds multiple offices cannot recieve more that one Official Salary.

When a judge returns a judgement, the bank owes one Judicial Salary to em.

Once per nweek, with a post to the public forum, the Banker may set the values of the Official Salary and the Judicial Salary such that the value of each is neither less than zero nor greater than twenty.

_____

Delete the paragraph following the numerical list in rule 273

0. Poulenc made a Proposal [352], 23 Nov 2000 17:38:39
0. Administrator recognized Proposal 352/0, 23 Nov 2000 19:14:00
1. Poulenc revised Proposal 352, 24 Nov 2000 00:35:46
1. Administrator recognized Proposal 352/1, 24 Nov 2000 02:52:28
2. Poulenc revised Proposal 352, 24 Nov 2000 02:58:18
2. Administrator recognized Proposal 352/2, 28 Nov 2000 05:11:49
2. Proposal 352/2 passed (5-4-0-3), 01 Dec 2000 00:00:00

Proposal 353/0 : Tax and Spend
1. Repeal R232.

2. Repeal R233.

3. Replace R231 with the following text, entitled "Proposal Scoring":

"Whenever a Proposal is adopted, the Bank owes:

1. the Adopted Proposal Award to the Proposal's owner
2. the Opposed Minority Award to each Agent who voted against the Proposal

Whenever a Proposal fails, the Bank is owed:

1. the Failed Proposal Fine by the Proposal's owner"

4. Create a rule entitled "Proposal Disbursements" with the following text:

Once per nweek, the Banker may set the Point values of the Adopted Proposal and Opposed Minority Awards such that the value of each is neither less than zero no r greater than twenty.

Once per nweek, the Tax Collector may set the Point value of the Failed Proposal Fine such that its value is neither less than zero nor greater than twenty.

5. Create a Rule entitled "Office of the Tax Collector", with the following text :

"The Office of The Tax Collector is an Elective Office. It is the responsibility of the Tax Collector to recover from Agents debts owed the Bank."

6. Create a Rule entitled "Bankruptcy":

"If ever the Bank's Point debts exceed its Point holdings plus the total Points it is owed, the Bank has become bankrupt.

Whenever the Bank is bankrupt, the Banker and Tax Collector are fined 20 Points each, with the excpetion that the Bankruptcy Fine may be imposed no more than on ce per turn."

0. Joel Uckelman made a Proposal [353], 23 Nov 2000 20:39:33
0. Administrator recognized Proposal 353/0, 24 Nov 2000 02:52:28
0. Proposal 353/0 passed (6-3-0-3), 01 Dec 2000 00:00:00

Proposal 354/0 : Nomic: not just a game but a way of life!
Append "The Rules of this game" to the list of recognized religious texts in rule 302.
0. Poulenc made a Proposal [354], 23 Nov 2000 21:53:20
0. Administrator recognized Proposal 354/0, 24 Nov 2000 02:52:28
0. Proposal 354/0 failed (2-7-0-3), 01 Dec 2000 00:00:00

Proposal 355/0 : Rule Cleanup
1. Repeal R6/0. [["Passage ratio" has superseeded all of the technical uses of "majority".]]

2. Repeal R209/0. [[This Rule applies only to the frist nweek of play.]]

0. Joel Uckelman made a Proposal [355], 24 Nov 2000 03:36:03
0. Administrator recognized Proposal 355/0, 28 Nov 2000 05:11:49
0. Proposal 355/0 passed (6-3-0-3), 01 Dec 2000 00:00:00

Proposal 356/0 : Who owns the Rules?
Create a Rule entitled 'Who owns the Rules?' with the following text:

"Rules are Objects. When a new Rule is created the owner of the proposal that created the Rule becomes the owner of the Rule. When an existing Rule is modified the owner of the proposal that modified the Rule becomes the owner of the Rule, regardless of who the previous owner was. When a Rule is repealed it ceases to exist and as such is not able to be owned."

Change the text of Rule 211/0 : Winning to the following text:

"Whenever an Agent's score reaches or exceeds 500 points, and that Agent owns 20 or more Rules, the Administrator shall credit em with a Win."

For all existing Rules, determine which proposal created or most recently modified them, and transfer ownership of the Rule to the player who submitted that proposal. For any Rules that were not created or modified [[i.e. those Initial Rules which have not been modified]] transfer ownership to the Bank, or if there is no Agent defined as the Bank, then these Rules shall remain unowned.

0. The Kid made a Proposal [356], 24 Nov 2000 17:38:24
0. Administrator recognized Proposal 356/0, 28 Nov 2000 05:11:49
0. Proposal 356/0 passed (5-4-0-3), 01 Dec 2000 00:00:00

Proposal 357/0 : Win Tokens
1. Amend R211 to read:

"Whenever an Agent owns at least the required number of Win Tokens, the Administrator shall credit em with a Win."

2. Amend R122 to read:

"In the event of a Win being awarded, the Administrator shall redistribute all Objects to their initial Owners as specified in the Rules and play shall continue normally, if possible; otherwise, play ceases."

3. Create a new Rule entitled "Win Tokens" with the following text:

"Win Tokens are transferrable Objects. The Administrator shall award an Agent with a Win Token if that Agent meets any of the following conditions:

1. possesses 500 or more Points
2. holds some Elected Office for a full Term
3. renders a Judgment as a Judge

Once an Agent has been awarded a Win Token for a condition, e may not receive another Win Token for that condition until after the next Win is awarded."

0. Joel Uckelman made a Proposal [357], 24 Nov 2000 23:05:52
0. Administrator recognized Proposal 357/0, 28 Nov 2000 05:11:49
0. Proposal 357/0 failed (2-6-1-3), 01 Dec 2000 00:00:00

Proposal 358/0 : No place like home
If Proposal 345/0 passes, enact a new rule with the title "No place like home" and with text as follows:

"A Place is a special instance of Object, which has the additional variables 'position', 'Player-capacity' and 'Object-capacity'. A Place may hold a given number of Players and a given number of Objects, and may be owned by more than one Player at one time. Places may be subdivided, but only into subcatagories such as 'rooms' which belong strictly to that Place - this part of this rule supersedes the relevant part of the rule entitle 'Objects'."

0. M'cachessilnath made a Proposal [358], 25 Nov 2000 14:47:58
0. Administrator recognized Proposal 358/0, 28 Nov 2000 05:11:49
0. Proposal 358/0 passed (8-1-0-3), 01 Dec 2000 00:00:00

Proposal 359/0 : The Name Game
Revise Rule 1/0, entitled "The Game", to the following text:

"'A Nomic' shall refer to the specific instance of Nomic game which possesses the body of rules containing this definition, unless it is made clear, whether explicitly or via the context, that 'A Nomic' refers to something else. Only the permutation of letter case which has both the initial A and the initial N of the second word capitalised may be take in this context, since the name in any other permutation case may be ambiguous."

0. M'cachessilnath made a Proposal [359], 25 Nov 2000 14:21:44
0. Administrator recognized Proposal 359/0, 28 Nov 2000 05:11:49
0. Proposal 359/0 passed (5-4-0-3), 01 Dec 2000 00:00:00

Proposal 360/0 : naming the nameless
enact a new rule entitled 'proposal titles' with the following text:

This rule applies only to proposals which (propose to) create a single new rule.

When the appropriate officer recognizes a new proposal, then: if the proposal lacks a title but the proposed new rule would have a title, the title of the proposal becomes the same same as the title of the rule; if the new rule lacks a title but the proposal has a title, the new rule's title becomes the same as the title of the proposal.

If neither the proposal nor the new rule have titles, this rule has no effect.

0. Benjamin made a Proposal [360], 27 Nov 2000 16:59:59
0. Administrator recognized Proposal 360/0, 28 Nov 2000 05:11:49
0. Proposal 360/0 passed (7-2-0-3), 01 Dec 2000 00:00:00

Proposal 361/0 : Paper-Rock-Scissors
Create a rule entitled "Paper-Rock-Scissors" with the following text:

Paper-Rock-Scissors is a two-player Game. Each player shall, without the other's knowledge, select one of "paper", "rock", or "scissors", and submit eir choice to the referee. The referee shall determine a winner thusly:

1. Paper beats rock.
2. Rock beats scissors.
3. Scissors beats paper.

In the event that both players make the same selection, neither wins and Paper-Rock-Scissors must be repeated.

Proposal 361/1 : Paper-Rock-Scissors : inactive

Create a rule entitled "Paper-Rock-Scissors" with the following text:

Paper-Rock-Scissors is a Contest for exactly two Contestants. To play, each Contestant shall notify the Contestmaster of eir choice of paper, rock, or scissors. Once the Contestmaster has received the selections of both Contestants, e shall announce a winner and transfer the Prizes to em.

The Contestmaster shall determine the winner as follows:

1. Paper beats rock.
2. Rock beats scissors.
3. Scissors beats paper.

In the event that both Contestants make the same selection, neither wins, and the Contest must be repeated.

The winner of the previous Paper-Rock-Scissors becomes its new Contestmaster.

0. Joel Uckelman made a Proposal [361], 02 Dec 2000 02:30:12
0. Administrator recognized Proposal 361/0, 07 Dec 2000 15:47:12
0. Joel Uckelman deactivated Proposal 361/0, 07 Dec 2000 15:47:12
1. Joel Uckelman revised Proposal 361, 04 Jan 2001 20:28:16
1. Administrator recognized Proposal 361/1, 07 Jan 2001 04:04:01

Proposal 362/0 : Political Go
Create a Rule entitled "Subgames" with the following text:

"Subgames may be played by any Agent who publicly indicates a desire to participate.

Each Subgame must have a Subgame Administrator."

[[There's a little more to say about this, obviously. Something about generalized features of Subgames. Actually, this should probably be a separate proposal.]]

Create a Rule entitled "Political Go" with the following text:

"There exists a Subgame called Political Go. The Go Consul is the Subgame Administrator.

Political Go is played on a square grid of 19 rank lines and 19 file lines, lettered horizontally from "a" to "s" and vertically from "1" to "19".

Each vertex on the grid must, at all times, either be empty or have a stone on it. Two vertices are adjacent if a grid line can be followed from one to the other without crossing any other vertices. A set of vertices is mutually adjacent if it is possible, by passing through only vertices in the set, to trace a path along grid lines from one vertex in the set to all other vertices in the set.

The stone is the playing piece in Political Go. Each stone is owned by one and only one Go player. Two stones are friendly if they are owned by the same Go player or by allies; otherwise, the stones are unfriendly. A set of stones is mutually friendly if all pairs of stones in the set are friendly. Two stones are adjacent if they occupy adjacent vertices. A stone is adjacent to a vertex if the vertex it occupies is adjacent to that vertex.

A dragon is defined as any set of mutually friendly stones occupying mutually adjacent vertices in which no stone in the set is adjacent to a mutually friendly stone not in the set. A dragon is adjacent to all of the vertices adjacent to the vertices occupied by its stones. A dragon has a number of liberties equal to the number of unoccupied vertices to which it is adjacent, with no vertex being counted more than once. A dragon is considered dead if has only one liberty; otherwise, the dragon is live. A dragon is friendly to a Go player if it contains only friendly stones. Each vertex from which no path may be traced to a dragon unfriendly to a Go player is counted as one territory for that Go player. A dragon has an eye if its liberties are territory for a Go player to whom it is friendly, and, barring a change of alliances, it would be impossible for that territory to be lost. Any dragon with two distinct eyes, barring a change of alliances, may never become dead.

The turn list is a list the names of all Go players. The first Go player on the turn list must make exactly one move, after which eir name is moved from the head of the list to the tail.

For each move, a Go player must do one of the following:

1. Place a stone.
2. Pass.
3. Offer an alliance.
4. Declare war on an ally.

If a Go player places a stone, e may place a single stone on any unoccupied vertex, with the following exceptions:

1. Stones may not be placed on vertices on which the Go player had a stone during eir previous turn.

2. Stones may not be place on vertices on which the placement of a stone would cause the formation of a friendly dragon with no liberties, unless it would also cause the formation of an enemy dragon with no liberties.

If a Go player passes, eir turn ends.

If a Go player offers an alliance, e must name a Go player whose stones are not friendly to whom e is making the offer. If that Go player accepts the offer, the two Go players become allied.

If a Go player declares war on an ally, the two Go players cease to be allies, and eir former ally's stones are no longer friendly.

On making a legal move, a Go player's turn ends. Before the next Go player's turn starts, the stones of enemy dragons with no liberties are captured and removed from the grid.

If a captured dragon is adjacent only to stones owned by a single Go player, that player is credited with all of the stones in the captured dragon. If a captured dragon is adjacent to stones owned by more than one Go player, the captured stones are divided thusly by the Go players whose stones are adjacent to the captured dragon:

The Go player with the most stones adjacent to the captured dragon receives the first stone, the next most the next stone, and so on, with ties broken randomly, until all captured stones are exhausted or every Go player capturing from that dragon has received a stone. The process is repeated until all stones from the captured dragon are exhausted.

If ever all Go players pass three times consecutively or no Go player may legally place a stone, the Subgame ends.

At the end of the game, all live dragons which could not gain two distinct eyes if play were to continue without a change of alliances are considered dead. All dead dragons are captured by the Go players whose unfriendly dragons are adjacent to them. Live unfriendly dragons adjacent to the liberties of dead dragons are considered to be adjacent to the dead dragons for the purpose of dividing the captured stones. After the removal of dead stones, each Go player's territory is counted. A Go player's Go score is the sum of eir territories and captured stones. The Go player with the highest Go score is the winner of the Subgame.

Proposal 362/1 : Political Go

Create a Rule entitled "Political Go" with the following text:

"There exists a Contest called Political Go. The Go Consul is the Contestmaster.
Political Go is played on a square grid of 19 rank lines and 19 file lines, lettered horizontally from "a" to "s" and vertically from "1" to "19".

Each vertex on the grid must, at all times, either be empty or have a stone on it. Two vertices are adjacent if a grid line can be followed from one to the other without crossing any other vertices. A set of vertices is mutually adjacent if it is possible, by passing through only vertices in the set, to trace a path along grid lines from one vertex in the set to all other vertices in the set.

The stone is the playing piece in Political Go. Each stone is owned by one and only one Go player. Two stones are friendly if they are owned by the same Go player or by allies; otherwise, the stones are unfriendly. A set of stones is mutually friendly if all pairs of stones in the set are friendly. Two stones are adjacent if they occupy adjacent vertices. A stone is adjacent to a vertex if the vertex it occupies is adjacent to that vertex.

A dragon is defined as any set of mutually friendly stones occupying mutually adjacent vertices in which no stone in the set is adjacent to a mutually friendly stone not in the set. A dragon is adjacent to all of the vertices adjacent to the vertices occupied by its stones. A dragon has a number of liberties equal to the number of unoccupied vertices to which it is adjacent, with no vertex being counted more than once. A dragon is considered dead if has only one liberty; otherwise, the dragon is live. A dragon is friendly to a Go player if it contains only friendly stones. Each vertex from which no path may be traced to a dragon unfriendly to a Go player is counted as one territory for that Go player. A dragon has an eye if its liberties are territory for a Go player to whom it is friendly, and, barring a change of alliances, it would be impossible for that territory to be lost. Any dragon with two distinct eyes, barring a change of alliances, may never become dead.

The turn list is a list the names of all Go players. The first Go player on the turn list must make exactly one move, after which eir name is moved from the head of the list to the tail.

For each move, a Go player must do one of the following:

1. Place a stone.
2. Pass.
3. Offer an alliance.
4. Declare war on an ally.

If a Go player places a stone, e may place a single stone on any unoccupied vertex, with the following exceptions:

1. Stones may not be placed on vertices on which the Go player had a stone during eir previous turn.

2. Stones may not be place on vertices on which the placement of a stone would cause the formation of a friendly dragon with no liberties, unless it would also cause the formation of an enemy dragon with no liberties.

If a Go player passes, eir turn ends.

If a Go player offers an alliance, e must name a Go player whose stones are not friendly to whom e is making the offer. If that Go player accepts the offer, the two Go players become allied.

If a Go player declares war on an ally, the two Go players cease to be allies, and eir former ally's stones are no longer friendly.

On making a legal move, a Go player's turn ends. Before the next Go player's turn starts, the stones of enemy dragons with no liberties are captured and removed from the grid.

If a captured dragon is adjacent only to stones owned by a single Go player, that player is credited with all of the stones in the captured dragon. If a captured dragon is adjacent to stones owned by more than one Go player, the captured stones are divided thusly by the Go players whose stones are adjacent to the captured dragon:

The Go player with the most stones adjacent to the captured dragon receives the first stone, the next most the next stone, and so on, with ties broken randomly, until all captured stones are exhausted or every Go player capturing from that dragon has received a stone. The process is repeated until all stones from the captured dragon are exhausted.

If ever all Go players pass three times consecutively or no Go player may legally place a stone, the Contest ends.

At the end of the game, all live dragons which could not gain two distinct eyes if play were to continue without a change of alliances are considered dead. All dead dragons are captured by the Go players whose unfriendly dragons are adjacent to them. Live unfriendly dragons adjacent to the liberties of dead dragons are considered to be adjacent to the dead dragons for the purpose of dividing the captured stones. After the removal of dead stones, each Go player's territory is counted. A Go player's Go score is the sum of eir territories and captured stones. The Go player with the highest Go score is the winner of the Contest.

Proposal 362/2 : Political Go

1. Create a Rule entitled "Political Go" with the following text:

"There exists a Contest called Political Go. The Go Consul is the Contestmaster. The first Go Consul is Joel.

The Go Board is empty at the start of Political Go. Players become Go players by making a Go move. Go players are unallied by default. Each Go player may make no more than one Go move per Game day, and may never place two Stones consecutively.

A game of Political Go ends if it is no longer legal to place a Stone, or if a nweek passes in which no Player places a Stone.

The Go player with the highest Go score is the winner of the Contest."

2. Create a Rule entitled "Go Board" with the following text:

'The Go Board is a square grid of 19 rank lines and 19 file lines, lettered horizontally from "a" to "s" and vertically from "1" to "19".

Each vertex on the grid must, at all times, either be empty or be occupied by a single Stone. Two vertices are adjacent if a grid line can be followed from one to the other without crossing any other vertices. A set of vertices is mutually adjacent if it is possible, by passing only through vertices in the set, to trace a path along grid lines from one vertex in the set to all other vertices in the set.'

3. Create a Rule entitled "Stones, Dragons, and Liberties" with the following text:

"The Stone is the playing piece in Political Go. Each Stone is owned by one and only one Go player. Two Stones are friendly if they are owned by the same Go player or by allies; otherwise, the stones are unfriendly. A set of Stones is mutually friendly if all pairs of Stones in the set are friendly. Two Stones are adjacent if they occupy adjacent vertices. A Stone is adjacent to a vertex if the vertex it occupies is adjacent to that vertex.

A Dragon is defined as any set of mutually friendly Stones occupying mutually adjacent vertices in which no Stone in the set is adjacent to a mutually friendly Stone not in the set. A Dragon is adjacent to all of the vertices adjacent to the vertices occupied by its Stones. A Dragon has a number of liberties equal to the number of unoccupied vertices to which it is adjacent, with no vertex being counted more than once. A Dragon is considered dead if has only one liberty; otherwise, the Dragon is live. A Dragon is friendly to a Go player if it contains only friendly Stones.

Each vertex from which no clear path may be traced to a Dragon unfriendly to a Go player is counted as one territory for that Go player. A Dragon has an eye if its liberties are territory for a Go player to whom it is friendly, and, barring a change of alliances, it would be impossible for that territory to be lost. Any Dragon with two distinct eyes, barring a change of alliances, may never become dead."

4. Create a Rule entitled "Go Moves" with the following text:

"For each move, a Go player must do one of the following:

1. Place a Stone. 2. Offer an alliance to an enemy. 3. Declare war on an ally.

If a Go player places a Stone, e may place a single Stone on any unoccupied vertex, with the following exceptions:

1. Stones may not be placed so as to repeat a previous Board configuration.

2. Stones may not be placed on vertices on which the placement of a Stone would cause the formation of a friendly Dragon with no liberties, unless it would also cause the formation of an enemy Dragon with no liberties.

If a Go player offers an alliance, e must name an enemy Go player to whom e is making the offer. If that Go player accepts the offer, the two Go players become allied.

If a Go player declares war on an ally, the two Go players cease to be allies, and eir former ally's Stones are no longer friendly."

5. Create a Rule entitled "Stone Capture" with the following text:

"Following each Go move, the Stones of Dragons with no liberties unfriendly to the moving Go player are captured.

If a captured Dragon is adjacent only to Stones owned by a single Go player, that Go player captures all of the Stones in the captured Dragon. If a captured Dragon is adjacent to Stones owned by more than one Go player, the captured Stones are divided among the owners of those Stones as follows:

The Go player with the most Stones adjacent to the captured Dragon receives the first Stone, the next most the next Stone, and so on, with ties broken randomly, until all captured Stones are exhausted or every Go player capturing from the Dragon has received a Stone. This process is repeated until all Stones from the captured Dragon are exhausted."

6. Create a Rule entitled "Go Scoring" with the following text:

"At the end of the game, all dead Dragons are captured by the Go players whose unfriendly Dragons are adjacent to them. After the removal of dead Stones, each Go player's territory is counted. A Go player's Go score is the sum of eir territories and captured Stones."

7. Create a Rule entitled "Clearing the Board" with the following text:

"Following Go scoring, a number of captured Stones equal to eir territories is created in each Go player's possession, and all of eir Stones in play are added to eir pool of captured Stones, thus removing all Stones from the Go Board."

0. Joel Uckelman made a Proposal [362], 02 Dec 2000 22:52:21
0. Administrator recognized Proposal 362/0, 07 Dec 2000 15:47:12
0. Joel Uckelman deactivated Proposal 362/0, 07 Dec 2000 15:47:12
1. Joel Uckelman revised Proposal 362, 04 Jan 2001 20:28:16
1. Administrator recognized Proposal 362/1, 07 Jan 2001 04:04:01
0. Joel activated Proposal 362/0, 15 Mar 2001 19:28:00
2. Joel revised Proposal 362, 17 Mar 2001 18:51:39
2. Administrator recognized Proposal 362/2, 18 Mar 2001 01:07:46
2. Proposal 362/2 passed (8-4-0-6), 21 Mar 2001 00:00:00

Proposal 363/0 : [no title]
1. Strike the paragraph in R327/2 beginning with "Upon".

2. Strike the comment text in R304/0.

Proposal 363/1 : Cleanup

1. Strike the paragraph in R237/2 beginning with "Upon".

2. Strike the comment text in R304/0.

0. Joel Uckelman made a Proposal [363], 04 Dec 2000 22:33:51
0. Administrator recognized Proposal 363/0, 07 Dec 2000 15:47:12
0. Joel Uckelman deactivated Proposal 363/0, 07 Dec 2000 15:47:12
1. Joel Uckelman revised Proposal 363, 15 Jan 2001 06:30:42
1. Joel Uckelman activated Proposal 363/1, 15 Jan 2001 06:30:42
1. Administrator recognized Proposal 363/1, 15 Jan 2001 22:56:09
1. Proposal 363/1 passed (4-1-0-6), 20 Jan 2001 00:00:00

Proposal 364/0 : Loans
Enact a new rule titled "Loans" with text as follows:

An agent may request a loan for a certain number of points and duration from the bank by posting eir request in the public forum. The Banker may then, within 1 nweek, offer that agent eir loan with an amount of interest at eir discression.

If the requesting agent, the Banker, and the Tax Collector publicly agree on the terms for the loan, the Banker shall issue the loan by ordering the transfer from the bank to the requesting agent of a number of points equal to the agreed amount of the loan, to be performed as soon as possible. A debt shall then be recorded of the agreed amount plus the agreed amount of interest, to be repayed in the agreed amount of time.

A loan to be issued to the Banker or the Tax collector requires the public approval of at least one of the Administrator and the Bean Counter.

0. Poulenc made a Proposal [364], 07 Dec 2000 03:03:17
0. Administrator recognized Proposal 364/0, 07 Dec 2000 15:47:12
0. Poulenc deactivated Proposal 364/0, 07 Dec 2000 21:05:02
0. Poulenc activated Proposal 364/0, 22 Dec 2000 05:38:34
0. Proposal 364/0 held (2-1-0-9), 31 Dec 2000 00:00:00
0. Proposal 364/0 failed (4-4-0-3), 10 Jan 2001 00:00:00

Proposal 365/0 : The Price of Nomic
Enact a new rule entitled "The Price of Nomic"

The Proposal fee is a value associated with the game; it can be changed only as specified by the rules. Initially the value is zero.

At the start of the voting period a debt of one Proposal Fee shall be recorded for the author of each proposal on the ballot, payable one nweek from the start of voting by the author of that proposal to the bank.

Once per week the Tax Collector may set the value of the Proposal Fee such that it is neither less than zero nor greater than twenty.

Proposal 365/1 : The Price of Nomic

1. Enact a new rule entitled "The Price of Nomic" which reads as follows:

The submission fee and the revision fee are values associated with the game; each may be changed only as specified by the rules. Initially the value of each is zero.

Once per week the Tax Collector may set the value of the submisison fee and the revision fee, such that the value of the proposal submission fee is neither greater than twenty nor less than zero, and the value of the proposal revision fee is neither greater than five nor less than zero.

2. Amend rule 120 to read as follows:

The Agent who submits a Motion is its owner. An Agent may never own more than ten live Motions of any one type, and may never submit more than ten Motions of any one type in a single day; otherwise an Agent may make a new Motion of any type at any time. Upon the submission of a Motion its owner owes one submission fee to the bank, due at the end of the next voting period.

New Motions are live and active by default. Motions are revisable. Unless the Rules allow other Agents to do so, only the owner of a live Motion may alter its parts, or activate, deactivate, or withdraw it. Withdrawn Motions are dead. Only live Motions may be altered or be Under Consideration. No Motion may be altered while Under Consideration. Upon performing a revision, withdrawal, activation, or deactivation of a Motion the revising agent owes one revision fee to the bank.

Each Motion is either Approvable or Unilateral, and Primary or Secondary. Approvable Motions are subject to voting or unanimous consent, as per the Rules. Unilateral Motions need no such approval to take effect. Primary Motions are assigned serial numbers by type, while Secondary Motions are assigned serial numbers as a group.

0. Poulenc made a Proposal [365], 07 Dec 2000 03:19:18
0. Administrator recognized Proposal 365/0, 07 Dec 2000 15:47:12
1. Poulenc revised Proposal 365, 07 Dec 2000 20:43:22
0. Poulenc deactivated Proposal 365/0, 07 Dec 2000 21:05:02
1. Administrator recognized Proposal 365/1, 21 Dec 2000 01:53:54
1. Poulenc activated Proposal 365/1, 22 Dec 2000 05:38:34
1. Proposal 365/1 held (1-2-0-9), 31 Dec 2000 00:00:00
1. Proposal 365/1 failed (1-7-0-3), 10 Jan 2001 00:00:00

Proposal 366/0 : How to Nominate
Insert the text "by posting eir nomination to a public forum" at the end of the last sentence of the first paragraph of Rule 312/0.
0. The Kid made a Proposal [366], 05 Dec 2000 15:26:00
0. Administrator recognized Proposal 366/0, 21 Dec 2000 01:53:54
0. Proposal 366/0 held (3-0-0-9), 31 Dec 2000 00:00:00
0. Proposal 366/0 failed (3-4-1-3), 10 Jan 2001 00:00:00

Proposal 367/0 : Win condition fix
Amend rule 211/1 to read as follows:

Whenever an Agent's score minus debts reaches or exceeds 500 points, and that Agent owns 20 or more Rules, the Administrator shall credit em with a Win.

0. Poulenc made a Proposal [367], 07 Dec 2000 20:03:16
0. Administrator recognized Proposal 367/0, 21 Dec 2000 01:53:54
0. Proposal 367/0 held (1-2-0-9), 31 Dec 2000 00:00:00
0. Proposal 367/0 failed (4-4-0-3), 10 Jan 2001 00:00:00

Proposal 368/0 : rescinding actions fix
Amend rule 301, "Rescinding Actions", to read as follows:

An Agent may rescind any unrecognized action e has taken at any time by publicly indicating that e is doing so. The recognition of a rescinded action by any Officer is prohibited. If the rescinded action created a debt then that debt is also rescinded.

0. Poulenc made a Proposal [368], 07 Dec 2000 20:46:48
0. Administrator recognized Proposal 368/0, 21 Dec 2000 01:53:54
0. Proposal 368/0 held (2-1-0-9), 31 Dec 2000 00:00:00
0. Proposal 368/0 failed (4-4-0-3), 10 Jan 2001 00:00:00

Proposal 369/0 : The price of justice
1. Enact a new rule titled "The price of Justice", text as follows:

The court fee is a value associated with the game that can only be changed as specified by the rules. Initially the value of the court fee is zero.

Once per nweek the Tax Collector may change the value of the court fee such that it is neither greater than twenty nor less than zero.

2. Amend the text of rule 234, "Requests for Judgement", to read as follows:

A Request for Judgment is a Primary Unilateral Motion. An Agent may, at any time, initiate judicial proceedings in any matter by making a Request for Judgment. That Agent shall be known as the Plaintiff with regard to the Request. A Request for Judgment consists of a Statement to be judged, and analysis as the Plaintiff deems appropriate. A Request for Judgment is dead once a Judgment has been issued on it.

Upon the creation of a Request for Judgement the creating Agent owes one court fee to the bank, due two weeks from the date of creation.

0. Poulenc made a Proposal [369], 07 Dec 2000 20:57:53
0. Administrator recognized Proposal 369/0, 21 Dec 2000 01:53:54
0. Proposal 369/0 held (1-2-0-9), 31 Dec 2000 00:00:00
0. Proposal 369/0 failed (1-7-0-3), 10 Jan 2001 00:00:00

Proposal 370/0 : Binding Contracts
1. Enact a new rule entitled "Contracts", with text as follows:

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.

2. Enact a new rule entitled "Optional Contract Parts", with text as follows:

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.

3. Enact a new rule entitled "Contract Offers", with text as follows:

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.

4. Create a new rule titled "Contract Restrictions", text as follows:

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.

5. Create a new rule titled "Contract records", text as follows:

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.

6. Create a new rule titled "The Motion to Escape a Contract", text as follows:

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.

0. Poulenc made a Proposal [370], 08 Dec 2000 08:04:31
0. Administrator recognized Proposal 370/0, 21 Dec 2000 01:53:54
0. Proposal 370/0 held (2-1-0-9), 31 Dec 2000 00:00:00
0. Proposal 370/0 passed (5-3-0-3), 10 Jan 2001 00:00:00

Proposal 371/0 : UC and Motion Fix
1. Amend R230/3 to read as follows:

"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."

2. Create a new Rule entitled "Motion Duplication" which reads:

"The recognition by any Officer of any Motion which would have the same effect another live Motion is prohibited."

Proposal 371/1 : UC and Motion Fix

1. Amend R230/3 to read as follows:

"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."

2. Create a new Rule entitled "Motion Duplication" which reads:

"The recognition by any Officer of any Motion which would have the same effect another live Motion is prohibited."

3. Motions 6/0, 7/0, and 8/0 are considered to have received unanimous consent as of the passage of this Proposal.

0. Joel Uckelman made a Proposal [371], 14 Dec 2000 01:01:22
0. Administrator recognized Proposal 371/0, 21 Dec 2000 01:53:54
1. Joel Uckelman revised Proposal 371, 22 Dec 2000 04:20:42
1. Administrator recognized Proposal 371/1, 22 Dec 2000 04:22:18
1. Proposal 371/1 held (2-1-0-9), 31 Dec 2000 00:00:00
1. Proposal 371/1 passed (4-3-0-4), 10 Jan 2001 00:00:00

Proposal 372/0 : challenge/response games
Enact a new rule entitled "Challenge/response games" with the following text:

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.

0. Benjamin made a Proposal [372], 30 Dec 2000 09:34:28
0. Administrator recognized Proposal 372/0, 31 Dec 2000 21:28:05
0. Proposal 372/0 passed (5-3-0-3), 10 Jan 2001 00:00:00

Proposal 373/0 : Similarity game
If the proposal entitled "challenge/response games" doesn't pass/hasn't passed, then discount the remainder of this proposal:

Enact a new rule entitled "Three of these things belong together" with the following text:

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!
]]

0. Benjamin made a Proposal [373], 30 Dec 2000 09:34:28
0. Administrator recognized Proposal 373/0, 31 Dec 2000 21:32:43
0. Proposal 373/0 passed (5-3-0-3), 10 Jan 2001 00:00:00

Proposal 374/0 : Contests
Create a Rule entitled "Contests" with the following text:

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.

0. Joel Uckelman made a Proposal [374], 04 Jan 2001 20:28:16
0. Administrator recognized Proposal 374/0, 07 Jan 2001 04:04:01
0. Proposal 374/0 passed (5-3-0-3), 10 Jan 2001 00:00:00

Proposal 375/0 : A Resolution for Point Amnesty
Whereas, the Failed Proposal Fine and Adopted Proposal and Opposed Minority Awards in effect during voting for nweek 10 were set several nweeks prior, and

Whereas, these were set in order to discourage further activity only until the Adminstrator was able to catch up with eir duties, and

Whereas, the Administrator is now mostly caught up, and

Whereas, the Failed Proposal Fine and Opposed Minority Award are exorbitantly high, and the Adopted Proposal Award shamefully low given now-normal conditions, and

Whereas, everyone forgot that these were still in effect, and

Whereas, the Bank itself was not well looked-after during this period, nor were the duties of the Banker discharged in a timely fashion, and

Whereas, the first version of the Banker's Nweekly Report for this nweek seems a more equitable solution, and

Whereas, it would be too much work to properly rectify the situation,

Therefore, be it resolved that:

1. Scores and the Bank's holdings are to be calculated based on the Banker's first (erroneous) Report, not the second.

2. Debts incurred by the Bank in the form of Salaries prior to Nweek 10 are hereby forgiven, and the Officers and former Officers are no longer owed them.

3. Fines incurred by Officers due to bankruptcy of the Bank, the point transfers for which have yet to made, are hereby forgiven.

Be it further resolved that the Banker should consider altering the Failed Proposal Fine and Adopted Proposal and Opposed Minority Awards sometime during the current nweek.

Proposal 375/1 : A Resolution for Point Amnesty

Whereas, the Failed Proposal Fine and Adopted Proposal and Opposed Minority Awards in effect during voting for nweek 10 were set several nweeks prior, and

Whereas, these were set in order to discourage further activity only until the Adminstrator was able to catch up with eir duties, and

Whereas, the Administrator is now mostly caught up, and

Whereas, the Failed Proposal Fine and Opposed Minority Award are exorbitantly high, and the Adopted Proposal Award shamefully low given now-normal conditions, and

Whereas, everyone forgot that these were still in effect, and

Whereas, the Bank itself was not well looked-after during this period, nor were the duties of the Banker discharged in a timely fashion, and

Whereas, the first version of the Banker's Nweekly Report for this nweek seems a more equitable solution, and

Whereas, it would be too much work to properly rectify the situation,

Therefore, be it resolved that:

1. Scores and the Bank's holdings are to be calculated based on the Banker's first (erroneous) Report, not the second.

2. Debts incurred by the Bank in the form of Salaries prior to Nweek 10 are hereby forgiven, and the Officers and former Officers are no longer owed them.

3. Fines incurred by Officers due to bankruptcy of the Bank, the point transfers for which have yet to made, are hereby forgiven.

4. 500 Points shall be created in the possession of the Bank, so as to provide sufficient reserves for operation.

0. Joel Uckelman made a Proposal [375], 12 Jan 2001 04:20:38
0. Administrator recognized Proposal 375/0, 12 Jan 2001 21:32:42
1. Joel Uckelman revised Proposal 375, 15 Jan 2001 06:30:42
1. Administrator recognized Proposal 375/1, 15 Jan 2001 22:56:09
1. Proposal 375/1 held (2-2-0-7), 20 Jan 2001 00:00:00
1. Proposal 375/1 held (2-0-0-9), 30 Jan 2001 00:00:00
1. Proposal 375/1 passed (5-1-0-8), 09 Feb 2001 00:00:00

[Proposals 301-325] [Proposals 326-350] [Proposals 351-375] [Proposals 376-400] [Proposals 401-425] [Proposals 426-450] [Proposals 451-475]

Tue 26 Jun 2001 17:19:00 UTC
Home