Thursday, May 31, 2007

Leave of Abscence

Unfortunately real life interferes at the most inopritune times.  I’m gonna have to go idle for a bit :-/  Sorry bout that.

Story Post: Story Post: I have Arrived

Hello all.  Another worker has arrived.  Allow myself to introduce….myself.  I am worker, Gazanga.

Wednesday, May 30, 2007

Story Post: Two simple pieces

I made one part that will push things to the left. I thought about making a complex part that would push things both left and right, but decided that would waste resources to have something do two things when it may only need to do one, so I just reversed the design and made one that pushed to the right.

Tuesday, May 29, 2007

Story post: “It just sits there.”

Added new part: “Cinder block” (CIN).  Just in case we need a big dumb object.

Tuesday, May 29, 2007

Story Post: A simple test:Building the Machine

At last, we have enough pieces to run a simple diagnostic test to see if the machine is working properly.  The proposed test runs require the complex interactions between a stacked POW, WTS and HALT. This test has the side purpose of seeing if the Power Manifold is powerful enough to move objects.  I’ll also need a CKP for support.

List:
1)POW
2)WTS
3)HALT
4)KCP

Story Post: Story Post:I patent the same thing twice

Having produced the Emergency Halt Valve, I realized the same principle could be used in other paces.  Thus, I created the Wired Toggle Switch(WTS) in order to more fully leverage this mechanism.  Instead of driving the whole machine, however, this version drives only nearby pieces, meaning that it can be used as a trigger.  I’d like to keep building these parts, but my in-box as an engineer is stacked to the ceiling.

Proposal: Every worker’s dream

It looks like everyone forgot this proposal existed. Passes 1-0.—Rodney
Or not. there’s not enough votes on it. Fails due to lack of votes. —Rodney

Adminned at 03 Jun 2007 07:03:55 UTC

Add a new subrule to Rule 2.2.  Call it “Buyout” and give it the following text:

If a Worker has a Net Worth of at least $1000, e has accumulated enough money to make a highly leveraged buyout of the company.  If e chooses to do so, e must make a story post describing eir takeover.  E has then achieved victory.

 

Saturday, May 26, 2007

Proposal: Downsizing

Once again, a proposal has gone on for far too long.  Passed 7-0.—Rodney

Adminned at 02 Jun 2007 05:26:42 UTC

Our Assembly group is a disgrace to the entire company.  In the last week, not one of them has so much as come to work in the morning.  Therefore, in a blatant but necessary abuse of the corporate politics system, I propose downsizing them and giving their responsibilities to the Engineering group.

Repeal Rule 2.4.3 “ASM” and renumber the subrules of Rule 2.4 accordingly.

In Rule 2.4.2, change the text

if a Majority of Workers with this Position vote FOR the Parts in the post, an assembler may add them to the Workbench.

to

if a Majority of Workers with this Position vote FOR the Parts in the post, any Engineerig Group Member may add them to the Workbench.

 

Activity Lag

So, this dynasty seems to be rather lackluster, not on the part of members, but on the side of the admins.  Is there a particular reason that we have decided to not pass things?  I have a personal reason in that I recently graduated and moved, but *hopefully* that’s over with…or is it that people just don’t really buy this dynastic idea?  I mean, if it’s the case I’m fine with passing the buck for better enjoyment by everyone else, but if it’s something else….

Saturday, May 26, 2007

Its gotta have been a week…

Yeah. Im going idle. I probably should’ve gone idle before now, but make it offcial.

Story Post: To heck with safety, more fire!

I made a trebuchet. It’s in the created parts page. I don’t reccomend drinking water near it.

Story post: Kill ‘em all.

Jim Jones Kool-Aid Shower (JJK) added to created parts page.  Just in case…

Friday, May 25, 2007

Story Post: Story Post: Safety First

When I came from Heath Robinson Inc. to lead the Engineering Group here, I thought things at my new company couldn’t be any worse.  I was wrong.  The GWF group here at Goldberg is even lazier than the SSI Team I’m used to dealing with.  At least their parts actually fit together occasionally.  The design group here is a total disgrace.  Also, the prototype I came here to work on isn’t even in working order, and the entire Assembly team has been mysteriously ill since I showed up.  Furthermore, as the machine has no safety devices and the GWF team wasn’t doing any design, I went ahead and built one myself, so that when [not if]  the machine goes haywire, I can stop the process with a well-placed cow.

I will be returning to the Engineering group on Monday.

Story Post: Parts Needed

This data I state
about the machine’s good parts
And what we need made

But first I must state
The Cow may break the rules set
and may need removed

For it will walk on
The parts that are the same size
Illigal this is

—-

There is no fire
to alight the cow to flames
It is useless now

“Rabid” there is not
a made part for this to be
to make monkey go

The Relay is off
and no way to turn it on
powered nothing is

Bridge has no turning
no description of it’s point
how it interacts

This is all for now
I hope this helps the machine
to run and flourish

Thursday, May 24, 2007

Proposal: Payday!

Times out 4-0. —Axeling

Adminned at 26 May 2007 21:15:40 UTC

Add a new subrule to the Rule entitled “Net Worth”.  (if such a Rule does not exist then this proposal does nothing)  Call it “Paychecks” and give it the following text:

Employees of Goldberg Technologies receive weekly paychecks for their hard work.  Therefore, each Worker may occasionally add an amount to eir Net Worth equal to eir Wages, but only if they have made a proposal or taken any action from a subrule of Rule 2.4 in the last week.

Proposal: Can we PLEASE get this proposal enactated before we all lose our minds?

Times out 4-0.—Axeling

Adminned at 26 May 2007 21:12:46 UTC

Add the text of “Proposal: Patent Rights, Act 3.” to the ruleset as rule 2.2.1 “Patent Rights”. Then, remove all text in that rule before and including the first two carriage returns in that rule.

The first is because the wiki auto-numbers, and we’d have to have a blank rule 2.2.1. The second is so we don’t have junk text in front.

Sunday, May 20, 2007

Proposal: Tinkering V2

Times out and reaches Quorum, 5-1.—Rodney

Adminned at 23 May 2007 10:36:16 UTC

This proposal makes the machine work in slightly more efficient ways, by ignoring initiated parts whose initiation has no effect.  It also clarifies the order of operations within a row.

In Rule 2.3.3, replace the text

# Step 4 - The parts on the Machine Parts page are examined in order from top to bottom. The first part whose Initiator conditions are met has its Effects carried out as indicated.

with:

# Step 4 - The parts on the Machine Parts page are examined in order from top to bottom and left to right. The first part, if any, whose Initiator conditions are met has its Effects carried out as indicated.  If this has no effect on the state of the Machine or any part thereof, repeat this step starting from the position of that part.

 

Saturday, May 19, 2007

Notice: The workbench is now set up

I just initialized the workbench page to the specs in the Ruleset, because its non-existence was illegal.  The table format used isn’t the most easy to work with, but at least it functions now.

Proposal: Tinkering

Selfkilled by Bucky.—Rodney

Adminned at 23 May 2007 10:34:05 UTC

This proposal makes the machine work in slightly more efficient ways, by ignoring initiated parts whose initiation has no effect.  It also clarifies the order of operations within a row.

In Rule 2.3.3, replace the text

#
# Step 2 - If the location of each Part on the workbench and the state of each part on the “Machine Parts” page is identical to any previous iteration of Step 2 since the machine was most recently Standing By then the Machine becomes Standing by, and any remaining steps are not performed.
# Step 3 - If no requirements for the Initiator of any Part are satisfied, then the Machine becomes Standing by, and any remaining steps are not performed.

with:

#  Step 3 - If for each part the Initiator effects are not met or would have no effect on the state of the Machine or any component thereof if met, then the Machine becomes Standing by, and any remaining steps are not performed.
# Step 4 - The parts on the Machine Parts page are examined in order from top to bottom and left to right. The first part whose Initiator conditions are met has its Effects carried out as indicated.  If this has no effect on the state of the Machine or any part thereof, repeat this step starting from the position of that part.

 

Proposal: Really speeding things

Passed 7-0. Nay-sayers unite!—Rodney

Adminned at 23 May 2007 10:32:16 UTC

Delete rule “Your Extra Salary Margin for Avoiding Nay-saying” and all its sub-rules.

Bucky

is also back. Quorum is 5

Aletiophile, Enderbean, Hix & Seebo

Are idle. I’m Back. Quorum is 4.

Friday, May 18, 2007

I’m back

unidle me please.

Proposal: Rework of Speeding Things Up

Passes, 6-0.—Rodney

Adminned at 23 May 2007 10:22:41 UTC

In the rule “Position” replace

Job Requrements: If there are at least 3 Workers with this Position, any Worker that has this Position may occasionally make a Story Post “Building the Machine” with a list of Pieces from the Created Pieces wiki page. Each Worker with this position may vote on this Story Post, and if a Majority of Workers with this Position vote FOR the Parts in the post are added to the either the List of Parts or List of Variables for the Machine.


with

Job Requrements: A Workers with this Position may occasionally make a Story Post “Building the Machine” with a list of Pieces from the Created Pieces wiki page. Each Worker may vote on this Story Post, and if a Majority of Workers with this Position vote FOR the Parts in the post, an assmebler may add them to the Workbench.


Replace

Job Requirements: Any Worker that has this Position may occasionally add a single entry to the Created Pieces Page. Upon doing so E must post a Story Post explaining eir action within 48 hours or the entry will be removed.


with

Job Requirements: If they have not done so within the last 48 hours. Workers with this position may add a single entry to the created pieces page. Upon doing so E must post a Story Post explaining eir action within 48 hours or the entry will be removed.


And replace

Each Worker has a value “Position” tracked in the GDNT. This Position is tracked by a 3 letter abreviation and is chosen from the list below. Each Position has the following attributes:


with

Each Worker has a value “Position” tracked in the GDNT. This Position is tracked by a 3 letter abreviation and is chosen from the list below. A worker may occasionally change eir position to any position other than the CEO. Each Position has the following attributes:

Add this to 2.5 Position after EGM:

  ASM
* Name: Assembler
* Job Type: Laborer
* Job Requrements: At any time when there is a successful story post passed with a majority of FOR votes (as stated in the EGM Job Requirements), an assembler may add the parts as described in the story post to the workbench.

Also chage in

There exist a wiki page Created Pieces which contains a list of pieces that have not been added to the machine. Any Entry to this page must either be a Variable or a Part and contain all the information that they have, as well as the date which the part was added to the Created Parts page.

with

There exist a wiki page Created Pieces which contains a list of pieces that have not been added to the machine. Any Entry to this page must be a Part and contain all the information that they have, as well as the date which the part was added to the Created Parts page.


I hope this is all correct. I think this will remove all references to variables that are unneeded, allow parts to be added to the workbench, and allow the game to speed up a bit.

 

Monday, May 14, 2007

Story Post: Flaming Bovine Experement

While trying to cook a hamburger and inadvertantly using a whole, living cow, I created a new part that may be of some benefit to the machine. Behold the MFC.

Proposal: Adding the Patent Rights to the Rules Set

This is getting ridiculous. I’ve unidled, and quorum stays at 5. Passes 6-0, although technically this one doesn’t do anything either.—Rodney

Adminned at 23 May 2007 10:20:03 UTC

This is a motion to add the text of the recently passed Proposal: Patent Rights, Act 3, to be added to the rules set as 2.2.2 Patent Rights.

Proposal: Speeding Things Up

Self-killed.—Axeling

Adminned at 19 May 2007 14:09:11 UTC

In the rule “Position” replace

Job Requrements: If there are at least 3 Workers with this Position, any Worker that has this Position may occasionally make a Story Post “Building the Machine” with a list of Pieces from the Created Pieces wiki page. Each Worker with this position may vote on this Story Post, and if a Majority of Workers with this Position vote FOR the Parts in the post are added to the either the List of Parts or List of Variables for the Machine.

with

Job Requrements: A Workers with this Position may occasionally make a Story Post “Building the Machine” with a list of Pieces from the Created Pieces wiki page. Each Worker may vote on this Story Post, and if a Majority of Workers with this Position vote FOR the Parts in the post are added to the either the List of Parts or List of Variables for the Machine.

Replace

Job Requirements: Any Worker that has this Position may occasionally add a single entry to the Created Pieces Page. Upon doing so E must post a Story Post explaining eir action within 48 hours or the entry will be removed.

with

Job Requirements: If they have not done so within the last 48 hours. Workers with this position may add a single entry to the created pieces page. Upon doing so E must post a Story Post explaining eir action within 48 hours or the entry will be removed.

And replace

Each Worker has a value “Position” tracked in the GDNT. This Position is tracked by a 3 letter abreviation and is chosen from the list below. Each Position has the following attributes:

with

Each Worker has a value “Position” tracked in the GDNT. This Position is tracked by a 3 letter abreviation and is chosen from the list below. A worker may occasionally change eir position to any position other than the CEO. Each Position has the following attributes:

Monday, May 14, 2007

Story Post: Question:

Curious: Why does my post not change the rules set? It adds the rule under Wages and makes an entry 2.2.2. Perhaps I am not understanding something.

Friday, May 11, 2007

Proposal: Patent Rights, Act 3.

2-0. Timed out. Consider me unidle while admining this.

It does no changes to the gamestate or ruleset.—Chronos

Adminned at 13 May 2007 17:55:57 UTC

2.2.2 Patent Rights

When a Laboror creates a Machine Part, that Laboror then owns the Patent Rights to that part. When the Machine has moved from a Stand By state to a Running state and just before the machine goes back to a Stand By state, and if the Laboror’s part works correctly at least once, the Laboror who has the Patent Rights gains $5 to eir Net Worth once per running of the machine, regardless of how many times the part was used. Due to the Machine working properly, the company is becoming more profitable and the company will award a bonus of $1 to all management staff for every part that is patented that works correctly. A Laboror may gain the $5 for every part e has Patent Rights too.

Wages earned from Patent Rights are updated in the GDNT before the machine enters the Stand By state. This avoids a loop that would start the machine running again from the update of the GDNT.

Working Correctly means that the initiator requirements were met and the effect caused at lease one (1) other part to meet its initiator requirements.

 

Friday, May 11, 2007

BUSYWORK for BACPAT’s Draft

This proposal will allow management to create BUSYWORK (Beneficial Utilization of Senior Yeoman’s Work) for workers. These are goals for the machine, that will be voted on by management in a similar manner to restructuring. Completed Busywork will result in a BACPAT (BUSYWORK Accomplished Cash Payout for Achieving Triumph) for management. Basically a cash reward set when the BUSYWORK was created. This will be awarded to all managers. Because letting managers vote on ways for them to make money is only fair.

I’m also considering including a provision that will remove the clause in ChivalryBean’s proposal that gives Management money when the machine runs, since this accomplishes a similar goal in a different manner.

Other things I’ve considered is giving the reward to a specific individual but I’m not sure how that would be determined. Another idea was to make the BACPAT part a trophy (BUSYWORK Achievement through Creative Productivity Award Trophy) awarded to the worker responsible for achieving the goal instead. And maybe have a separate cash reward for management. Then the number of BACPAT’s a worker had could be used in evaluating people for management somehow. Maybe different positions could have minimum eligibility requirements.  But again this would require some method of assigning credit.

Its really a rough idea, so comments (and better acronym suggestions :) ) are welcome.

Proposal: Patent Rights. Take 2

2-2. Timed out. Consider me Idle again.—Chronos

Adminned at 13 May 2007 04:23:57 UTC

Rework of the Proposal of Patent Rights, which would be added to the Wages section as 2.2.2.

2.2.2 Patent Rights

When a Worker creates a Machine Part that works correctly the first time it is used in the Machine, the Worker may request Patent Rights. When Patent Rights are in force, when the Machine is run and the Worker’s part works correctly at least once, the Worker who has the Patent Rights gains $5 to eir Net Worth once per running of the machine, regardless of how many times the part was used. Due to the Machine working properly, the company is becoming more profitable and the company will award a bonus of $1 to all management staff for every part that is patented that works correctly. A Worker may gain the $5 for every part e has Patent Rights too.

Whomever is running the machine shall update the GDNT with gained Patent Rights (both worker and management) just before the Machine enters a Standby State. This is to avoid the Machine running because the GDNT was updated from the gaining of profit from the Parts that Worked Correctly.

Working Correctly means that the initiator requirements were met and the effect caused at lease one (1) other part to meet its initiator requirements.

Proposal: Patent Rights

S-K.—Chronos

Adminned at 13 May 2007 04:19:58 UTC

An addition to Wages, 2.2.2

2.2.2 Patent Rights

When a Worker creates a Machine Part that works correctly the first time it is used in the Machine, the Worker may request Patent Rights. When Patent Rights are in force, any time the said Part works correctly in the Machine, the worker gains $5 and may once (and only once per times the part worked correctly) add $5 to eir Net Worth in the GNDT.

Working Correctly means that the initiator requirements were met and the effect caused at lease one (1) other part to meet its iniator requirements.

First tinkering

The new guy grabs a set of tools and spare parts and creates a Radio Transmitter and sets it up in the Created Pieces to see what happens.

Wednesday, May 09, 2007

Story Post: Enter the Chivalrybean

Done.  Quorum rises to 6.  Your GNDT password has been PM’ed to you.  Welcome to the game.

Adminned at 09 May 2007 20:46:05 UTC

At the start of a shift today, there is a new guy sitting it the break room. E wear a hat with a robot on it. E proudly announces when asked about it that Is wife drew the robot. He looks ready to get to work.

Proposal: Action Fix (Take 2)

5-0. Timed out.—Chronos

Adminned at 13 May 2007 04:18:58 UTC

Modify the rule “Machine in Action” to read:

At any given time, the Machine is considered to be either “Running” or “Standing by”. At the moment this paragraph is added to the Ruleset, the Machine is Standing by.

When the Machine is Standing by, it becomes Running if any of the following occur:

* The order or contents of the list of Parts on the “Machine Parts” page change (including the addition or removal of a Part).
* The location of a Part on the Workbench changes
* A Worker is added to or removed from the list of Active Workers in the blog sidebar.
* A Proposal becomes Enacted. In this case, the specified effects of said Proposal occur before the Machine becomes Running.
* A value which the Ruleset requires to be tracked in the GNDT changes.

When the Machine becomes Running, the following steps take place, in order:

* Step 1 - If any Rule other than this Rule requires changes to be made to the Gamestate, those changes are made as usual, until no such changes are required. (If there is an infinite loop within the Ruleset itself, no out will be provided, of course. Don’t let that happen.)
* Step 2 - If the location of each Part on the workbench and the state of each part on the “Machine Parts” page is identical to any previous iteration of Step 2 since the machine was most recently Standing By then the Machine becomes Standing by, and any remaining steps are not performed.
* Step 3 - If no requirements for the Initiator of any Part are satisfied, then the Machine becomes Standing by, and any remaining steps are not performed.
* Step 4 - The parts on the Machine Parts page are examined in order from top to bottom. The first part whose Initiator conditions are met has its Effects carried out as indicated.
* Step 5 - Repeat Steps 1-5 in order, until a Step indicates that remaining steps are not to be performed.

This version is much simplified by only allowing one part to run at a time, rather than having all parts run from a snapshot

Proposal: Action Fix

S-K.—Chronos

Adminned at 13 May 2007 04:18:14 UTC

Modify the rule “Machine in Action” to read:

At any given time, the Machine is considered to be either “Running” or “Standing by”. At the moment this paragraph is added to the Ruleset, the Machine is Standing by.

When the Machine is Standing by, it becomes Running if any of the following occur:

  * The order or contents of the list of Parts on the “Machine Parts” page change (including the addition or removal of a Part or Variable).
  * A Worker is added to or removed from the list of Active Workers in the blog sidebar.
  * A Proposal becomes Enacted. In this case, the specified effects of said Proposal occur before the Machine becomes Running.
  * A value which the Ruleset requires to be tracked in the GNDT changes.

When the Machine becomes Running, the following steps take place, in order:

  * Step 1 - If any Rule other than this Rule requires changes to be made to the Gamestate, those changes are made as usual, until no such changes are required. (If there is an infinite loop within the Ruleset itself, no out will be provided, of course. Don’t let that happen.)
  * Step 2 - If the position of each Part on the workbench and the state of each part on the “Machine Parts” page is identical to any previous iteration of Step 2 since the machine was most recently Standing By then the Machine becomes Standing by, and any remaining steps are not performed.
  * Step 3 - If no requirements for the Initiator of any Part are satisfied, then the Machine becomes Standing by, and any remaining steps are not performed.
  * Step 4 - A ‘snapshot’ is taken of the current state of the Machine Parts and Workbench pages.
  * Step 5 - Each Part in the ‘snapshot’ is examined in order from top to bottom. If the conditions specified in the Initiator of that part are met based upon the information in the ‘snapshot’ then the Effect of that part is carried out by making changes to the Machine Parts page, Workbench page, or any other required changes.
  * Step 6 - Repeat Steps 1-6 in order, until a Step indicates that remaining steps are not to be performed.

Proposal: Change to Parts #2

4-1. Timed out.—Chronos

Adminned at 13 May 2007 04:17:03 UTC

Proposal to amend Rule 2.3.1 “Parts” as follows:

Replace the text that currently reads:

Effect: A description of changes to the States of other Parts.

with the text:

Effect: A description of changes to the Gamestate (other than the Ruleset and any statistics tracked in the GNDT) that will be given effect upon the Initiator requirement or requirements being satisfied.  Particular effects may be conditioned upon the existence of particular Gamestate circumstances (such as, for example, particular Parts having particular Locations or States).

 

Part added

The Rabid Monkey has been added to the Created Parts page.

problems_with_the_machine_in_action

The rule “The Machine in Action” in the ruleset is screwed up in the wiki and needs to be fixed.  At any rate, the rule is also now broken in a substantive sense because it refers to “Variables”, which no longer exist.

Story Post: Energy Relay Updated

The Energy Relay has been updated in accordance with the new rules.

Proposal: Change to Parts

S-K. Consider myself unidled (Quorum still 6) while I’m admining Proposals.—Chronos

Adminned at 13 May 2007 04:16:00 UTC

Proposal to amend Rule 2.3.1 “Parts” as follows:

Replace the text:

Effect: A description of changes to the “Machine Variables” wiki page.

with the text:

Effect: A description of changes to the Gamestate (other than the Ruleset and any statistics tracked in the GNDT) that will be given effect upon the Initiator requirement or requirements being satisfied.  Particular effects may be conditioned upon the existence of particular Gamestate circumstances (such as, for example, particular Parts having particular Locations or States).

 

power manifold and shark edited

power manifold and shark are edited per the enactment of the no more variables proposal

Story Post: Yay for Bananas

The Banana Tree has now been added to the created pieces page.

htory post: New Part “Power Manifold”

This is a story post.  The new part “Power Manifold” has been added to the Created Pieces page.

Tuesday, May 08, 2007

Proposal: No variables, again.

Passes. Either 7-0 or 8-0. There were a couple CoV’s to IMPs, but either way it only need 5 so still passes.

Clucky

Adminned at 09 May 2007 07:02:53 UTC

Delete the third sentence of Rule The Machine.

Rewrite the entry beginning with Effect in the list in Subrule Parts to read:

Effect: A description of changes to the States of other Parts.

Rewrite the entry beginning with Size in the list in Subrule Parts to read:

*Size: The number and orientation of Workbench Squares that this Part would occupy if placed on the Workbench. (Examples: 1x1, 3 wide by 2 high). The number of Squares must be a nonnegative integer. If the size is unspecified then the size is 1x1 (i.e., one Square).
*Possible States: A description of the possible states the Part may be in. If appropriate, a description of the order in which the Part advances States may be included.
*State: The current State of the Part (which must always be one of the possible States described in the previous bullet-point).
*Default State: A Constant which is the same as the State of the Part when it is first added to the Machine.

Delete Subrule Variables

Rewrite Subrule Workbench to read

The Workbench is a grid of Squares consisting of 6 rows labeled “A” through “F” (with A at the bottom) and 8 columns labeled “1” through “8” (with 1 on the left). Individual Squares in the Workbench are thus identified “1A” (at the lower left and so on through “6F” at the upper right).  There exists a wiki page Workbench which describes the location of all Pieces on the Workbench. The contents of this list are considered part of the Gamestate (and thus may not be modified except as permitted by the Ruleset).

Workbench Squares are considered “adjacent” if their positions on the Workbench grid are adjacent. For example, Square 1A is adjacent to Squares 2A and 1B, but not adjacent to any other Squares. The terms “above” and “beneath” may also be appropriately used to indicate Workbench Squares that occupy a position in the same column as a given Square.

In order for a Part with nonzero Size to become part of the Machine, in addition to any other criteria that a Part must meet, that Part must be placed in vacant Squares in the Workbench. If a Part has 0 Size, then this requirement does not apply.

Two or more Parts may not occupy the same Square. Placing a Part in the Workbench is accomplished by indicating which column (or adjacent columns, if the Part is more than 1 column wide) the Part is dropped into. The Part then drops down to the lowest vacant Squares in that column. For example, if the Workbench is empty and a 1x1 sized Part is dropped in column 3 then the Part falls down to Square 3A. If another 1x1 sized Part is then dropped in column 3 it falls down to Square 3B. If a 2-wide by 1-high Part is then dropped in columns 3 and 4 then it falls down to Squares 3C-4C.

Parts “fall down” to the lowest vacant Squares in the Workbench columns that it occupies, but without changing its shape. Thus, for example, if the Workbench is empty except for “PART-A” (a 1x1 sized Part located at Square 3A), “PART-B” (a 1x1 sized part located at Square 3B) and “PART-C” (a 2-wide by 1-high Part located at Squares 3C-4C), and PART-B is destroyed or removed from the Workbench, then PART-C will immediately “fall down” and change its location to Squares 3B-4B. “Falling down” happens whether the Machine is Running or Standing By, and notwithstanding anything to the contrary in the “The Machine in Action” rule, occurs immediately upon the condition for “Falling down” occurring, and before any further Machine running steps may occur.

The Square or Squares on the Workbench occupied by a Part may be referred to as that Part’s Location. A Part that is not on the Workbench does not have a Location.

Any Parts or Variables that are in the Created Pieces Page may be modified to fit the changes made in this Proposal within 72 hours of the passing of this Proposal by the creator of that Piece by making the requisite changes and making a post indicating that e has modified the part.  If any Piece exists that does not contain the necessary information, then it shall be deleted 72 hours this Proposal is Enacted.

Monday, May 07, 2007

No variables, yet again

Delete the third sentence of Rule The Machine.

Rewrite the entry beginning with Effect in the list in Subrule Parts to read:

Effect: A description of changes to the States of other Parts.

Rewrite the entry beginning with Size in the list in Subrule Parts to read:

*Size: The number and orientation of Workbench Squares that this Part would occupy if placed on the Workbench. (Examples: 1x1, 3 wide by 2 high). The number of Squares must be a nonnegative integer. If the size is unspecified then the size is 1x1 (i.e., one Square).
*Possible States: A description of the possible states the Part may be in. If appropriate, a description of the order in which the Part advances States may be included.
*State: The current State of the Part (which must always be one of the possible States described in the previous bullet-point).
*Default State: A Constant which is the same as the State of the Part when it is first added to the Machine.

Delete Subrule Variables

Rewrite Subrule Workbench to read

The Workbench is a grid of Squares consisting of 6 rows labeled “A” through “F” (with A at the bottom) and 8 columns labeled “1” through “8” (with 1 on the left). Individual Squares in the Workbench are thus identified “1A” (at the lower left and so on through “6F” at the upper right).  There exists a wiki page Workbench which describes the location of all Pieces on the Workbench. The contents of this list are considered part of the Gamestate (and thus may not be modified except as permitted by the Ruleset).

Workbench Squares are considered “adjacent” if their positions on the Workbench grid are adjacent. For example, Square 1A is adjacent to Squares 2A and 1B, but not adjacent to any other Squares. The terms “above” and “beneath” may also be appropriately used to indicate Workbench Squares that occupy a position in the same column as a given Square.

In order for a Part with nonzero Size to become part of the Machine, in addition to any other criteria that a Part must meet, that Part must be placed in vacant Squares in the Workbench. If a Part has 0 Size, then this requirement does not apply.

Two or more Parts may not occupy the same Square. Placing a Part in the Workbench is accomplished by indicating which column (or adjacent columns, if the Part is more than 1 column wide) the Part is dropped into. The Part then drops down to the lowest vacant Squares in that column. For example, if the Workbench is empty and a 1x1 sized Part is dropped in column 3 then the Part falls down to Square 3A. If another 1x1 sized Part is then dropped in column 3 it falls down to Square 3B. If a 2-wide by 1-high Part is then dropped in columns 3 and 4 then it falls down to Squares 3C-4C.

Parts “fall down” to the lowest vacant Squares in the Workbench columns that it occupies, but without changing its shape. Thus, for example, if the Workbench is empty except for “PART-A” (a 1x1 sized Part located at Square 3A), “PART-B” (a 1x1 sized part located at Square 3B) and “PART-C” (a 2-wide by 1-high Part located at Squares 3C-4C), and PART-B is destroyed or removed from the Workbench, then PART-C will immediately “fall down” and change its location to Squares 3B-4B. “Falling down” happens whether the Machine is Running or Standing By, and notwithstanding anything to the contrary in the “The Machine in Action” rule, occurs immediately upon the condition for “Falling down” occurring, and before any further Machine running steps may occur.

The Square or Squares on the Workbench occupied by a Part may be referred to as that Part’s Location. A Part that is not on the Workbench does not have a Location.

Any Parts or Variables that are in the Created Pieces Page may be modified to fit the changes made in this Proposal within 72 hours of the passing of this Proposal by the creator of that Piece by making the requisite changes and making a post indicating that e has modified the part.  If any Piece exists that does not contain the necessary information, then it shall be deleted 72 hours this Proposal is Enacted.

Sunday, May 06, 2007

Proposal: Variables are silly, another take

Self-kill. —Axeling

Adminned at 06 May 2007 22:57:22 UTC

Delete the third sentence of Rule The Machine.

Rewrite the entry Size in Subrule Parts to read:

*Size: The number and orientation of Workbench Squares that this Part would occupy if placed on the Workbench. (Examples: 1x1, 3 wide by 2 high). The number of Squares must be a nonnegative integer. If the size is unspecified then the size is 1x1 (i.e., one Square).
*Possible States: A description of the possible states the Part may be in. If appropriate, a description of the order in which the Part advances States may be included.
*State: The current State of the Part (which must always be one of the possible States described in the previous bullet-point).
*Default State: A Constant which is the same as the State of the Part when it is first added to the Machine.

Delete Subrule Variables

Rewrite Subrule Workbench to read

The Workbench is a grid of Squares consisting of 6 rows labeled “A” through “F” (with A at the bottom) and 8 columns labeled “1” through “8” (with 1 on the left). Individual Squares in the Workbench are thus identified “1A” (at the lower left and so on through “6F” at the upper right).  There exists a wiki page Workbench which describes the location of all Pieces on the Workbench. The contents of this list are considered part of the Gamestate (and thus may not be modified except as permitted by the Ruleset).

Workbench Squares are considered “adjacent” if their positions on the Workbench grid are adjacent. For example, Square 1A is adjacent to Squares 2A and 1B, but not adjacent to any other Squares. The terms “above” and “beneath” may also be appropriately used to indicate Workbench Squares that occupy a position in the same column as a given Square.

In order for a Part with nonzero Size to become part of the Machine, in addition to any other criteria that a Part must meet, that Part must be placed in vacant Squares in the Workbench. If a Part has 0 Size, then this requirement does not apply.

Two or more parts may not occupy the same Square. Placing a Part in the Workbench is accomplished by indicating which column (or adjacent columns, if the Part is more than 1 column wide) the Part is dropped into. The Part then drops down to the lowest vacant Squares in that column. For example, if the Workbench is empty and a 1x1 sized Part is dropped in column 3 then the Part falls down to Square 3A. If another 1x1 sized Part is then dropped in column 3 it falls down to Square 3B. If a 2-wide by 1-high Part is then dropped in columns 3 and 4 then it falls down to Squares 3C-4C.

Part “fall down” to the lowest vacant Squares in the Workbench columns that it occupies, but without changing its shape. Thus, for example, if the Workbench is empty except for “PART-A” (a 1x1 sized Part located at Square 3A), “PART-B” (a 1x1 sized part located at Square 3B) and “PART-C” (a 2-wide by 1-high Part located at Squares 3C-4C), and PART-B is destroyed or removed from the Workbench, then PART-C will immediately “fall down” and change its location to Squares 3B-4B. “Falling down” happens whether the Machine is Running or Standing By, and notwithstanding anything to the contrary in the “The Machine in Action” rule, occurs immediately upon the condition for “Falling down” occurring, and before any further Machine running steps may occur.

The Square or Squares on the Workbench occupied by a Part may be referred to as that Part’s Location. A Part that is not on the Workbench does not have a Location.

Any Parts or Variables that are in the Created Pieces Page may be modified to fit the changes made in this Proposal within 72 hours of the passing of this Proposal by the creator of that Piece by making the requisite changes and making a post indicating that e has modified the part.  If any Piece exists that does not contain the necessary information, then it shall be deleted 72 hours this Proposal is Enacted.

Friday, May 04, 2007

Workbench wiki template

Admins: look at User:Spikebrennan/Sandbox-4 in the wiki.

Proposal: Variables are silly

Time out (3-4).—Axeling

Adminned at 06 May 2007 22:56:28 UTC


If the proposal titled “Workbench Repair” passes, reverse all changes by the proposal except for the line “Amend Rule 2.3.1 “Parts” and 2.3.2 “Variables” to replace the word “Cells” wherever it appears with the word “Squares”.”


In the rule called “The Machine” enact the following changes:

-replace “The Machine consists of Pieces that are classified as either Parts or Variables.” with “The Machine consists of a number of pieces, also called parts.”


In the sub-rulle called “Parts” enact the following changes:

-replace “A description of changes to the “Machine Variables” wiki page.” with “A description of changes to the variables of the part or other parts in the machine.”

-add “Variables: The variables associated with each part. Each variable should include the following information:

# Name: The name by which the Variable is referred (and any abbreviations by which it may be referred).
# Possible States: A description of the possible states the variable may be in. If appropriate, a description of the order in which the variable advances may be included.
# State: The current State of the Variable (which must always be one of the possible states described in the previous bullet-point).
# Default State: A Constant which is the same as the State of the variable when the part is first added to the Machine.


Repel the sub-rule “Variables”


In the sub-rule “Workbench” enact the following changes

-replace “In order for a Part to become part of the Machine, that Part must be placed in vacant Squares in the Workbench. If a Variable’s description in the “Machine Variables” wiki page provides that the Variable may be placed in the Workbench, then the Variable may not become part of the Machine unless it is placed in vacant Squares in the Workbench. Otherwise, it is not required that the Variable be placed on the Workbench in order to become part of the Machine.”

with “When a Part is added to the Machine, that Part must be placed in vacant Squares in the Workbench. If it cannot legally be placed in the Workbench, the part is not added to the machine.”


In the sub-rule “The Machine in Action” enact the following changes

-if it exists, replace “The order or contents of the list of Parts on the “Machine Parts” page or of the list of Variables on the “Machine Variables” page change (including the addition or removal of a Part or Variable).”

with “The order or contents of the list of Parts on the “Machine Parts” page, including any variables, page changes (including the addition or removal of a Part or Variable).”

-replace “Step 2 - If the order and contents of the list of Variables on the “Machine Variables” page are identical to what they were during any previous iteration of Step 2 that was made since the Machine was most recently Standing by, then the Machine becomes Standing by, and any remaining steps are not performed.”

with “Step 2 - If the order and contents of all the variables on the “Machine Parts” page are identical to what they were during any previous iteration of Step 2 that was made since the Machine was most recently Standing by, then the Machine becomes Standing by, and any remaining steps are not performed.”

-replace “Changes to the “Machine Variables” page are made as described in the Effect of the first Part for which the Initiator requirements are satisfied (when the Parts are considered in the order in which they are listed on the “Machine Parts” page). No aspect of the Gamestate other than the contents of the “Machine Variables” page may be changed in this way.”

with “Changes to the each of the variables on the “Machine Parts” page are made as described in the Effect of the first Part for which the Initiator requirements are satisfied (when the Parts are considered in the order in which they are listed on the “Machine Parts” page). No aspect of the Gamestate other than the contents of these variables may be changed in this way.”


In the rule Position enact the following changes

-replace “There exist a wiki page Created Pieces which contains a list of pieces that have not been added to the machine. Any Entry to this page must either be a Variable or a Part and contain all the information that they have, as well as the date which the part was added to the Created Parts page.”

with “There exist a wiki page Created Pieces which contains a list of pieces that have not been added to the machine. Any Entry to this page must part and contain all the information that they have, as well as the date which the part was added to the Created Parts page.”



Remove all entries from the created pieces page. Any worker who made an entry to the created pieces page which was removed by this rule may, once within 72 hours after this proposal passes, add new entry to the created pieces page. This action is not considered the same action done by the GWF and thus does not count against eir “often”


Like this proposal says, variables are silly. They basically just make it take longer to get a part in action. It is not like two parts are gonna share the same variable. If they are sharing the same variable, I betcha that isn’t a variable but another part. Like, the watering can is a part. The status shark is a part. Variable would be like “status of watering can”. But forcing one to add even the most trivial variables is silly

Proposal: Workbench Repair

Times out, 1-2—Axeling

Adminned at 06 May 2007 22:53:32 UTC

Amend rules as follows:

Amend Rule 2.3.1 “Parts” and 2.3.2 “Variables” to replace the word “Cells” wherever it appears with the word “Squares”.

Amend the Created Pieces wiki page such that any Variables on that page as of the moment that this Proposal is adminned that do not state whether that Variable may be placed on the Workbench (such Variables being referred to as “Defective Variables”) have text “X” added to the end of that Workbench.

The content of text “X” will be determined as follows:
- If the Creator of a particular Defective Variables posts a reply to this proposal before this proposal is adminned that contains a proposed form of text “X” for that Defective Variable that, if added to the description of that Defective Variable on the Created Pieces page, would cause the Defective Variable to be in conformity with the requirements of the “Locatability and Size” clause of Rule 2.3.2, then that proposed form of text “X” will be the text “X” that is added to the description of that Defective Variable.  Otherwise, text “x” will be “This Variable may not be placed on the Workbench.”
If

Story Post: This time, fo real.

A watering can has been added to the parts list.

Story Post: This time, fo real.

A watering can has been added to the parts list.

Thursday, May 03, 2007

Story Post: Pay Day

Due to the amazing response from the starting up of the company, the CEO has deemed that all those that work for GT deserve a little something for all their hard work.  Keep up the pace everyone!

Proposal: Machine Fix

Self-kill.
Adminned by Alethiophile.

Adminned at 05 May 2007 09:57:14 UTC

Add the following Position to the list:

OPR

  • Name: Operator
  • Job Type: Laborer
  • Job Requirements: Occasionally, any Worker at this Position may make the Machine Running.

Change this in rule “The Machine in Action”

When the Machine is Standing by, it becomes Running if any of the following occur:

    The order or contents of the list of Parts on the “Machine Parts” page or of the list of Variables on the “Machine Variables” page change (including the addition or removal of a Part or Variable).
  • A Worker is added to or removed from the list of Active Workers in the blog sidebar.
  • A Proposal becomes Enacted. In this case, the specified effects of said Proposal occur before the Machine becomes Running.
  • A value which the Ruleset requires to be tracked in the GNDT changes.

to

The Machine is made Running by an Operator.

Proposal: Death and Destruction

Vetoed.—Axeling

Adminned at 04 May 2007 16:12:23 UTC

Add the following to the Machine rule:

Every Variable and Part has the state “Blown Up”. If a Part is in this state, it cannot be Activated. If a Variable is in this state, it cannot affect any Parts or Variables.

Story Post: Prepare to Power Up!

The Energy Relay has been added to the Created Parts page.

Is anyone else having trouble with this page displaying correctly? Or is it a browser caching issue on my end?

Confused Kamikaze Pilot

New Created Pieces entry: Confused WWII era Kamikaze Pilot

Story Post: This time, it’s for real.

I have added a single entry to the Created Pieces Page.  This Story Post explains my action.

Created Pieces Reminder

Remember to include the Date Added when you put na entry into the Created Pieces wiki as required by the rules.

Story Post: Banana Tree

The Banana Tree has been added. Now we just need watering cans and banana piles.

Story Post: New Variable “Shark Status”

This is a story post explaining that I have added a new variable “Shark Status” to the Created Pieces wiki page.

Story Post: Story Post?

I have added a single entry to the Created Pieces Page.  I hope this Story Post helps to explain my action.

Proposal: YESMEN are WEAK

Quorumed (7-0)—Axeling

Adminned at 04 May 2007 16:05:06 UTC

In the rule titled “Your Extra Salary Margin for Avoiding Nay-saying”

add the following subrule called “Thinking for ones-self”

If, from 00:00 AM Monday to 23:59 PM the following Sunday, every vote that a worker casts is either FOR or AGAINST(i.e., no IMP) and does not change any of eir votes, e may once and only once increase eir wages by 1.00, provided e voted on at least five proposals.


Kissing up to the boss might give some short term rewards, but showing you have a sound mind leads to long-term success.

Besides, life its still flawed. If we assume five proposals aweek, Thinkers for eim-self will gain 1 salary vs 5 net worth. It will take awhile for the forces to cancel eachother out.

Thursday, May 03, 2007

Proposal: Let me show you how it’s done

Quorumed (5-1)—Axeling

Adminned at 04 May 2007 15:56:55 UTC

Change the following text from

Occasionally the CEO or any Worker with a Management Position make a Story Post to the main page title “Restructuring” which contains changes to the Current Available Positions (below) and is voted on by all Workers with a Management position (per Proposal Rules), in the event of a Majority vote FOR those changes are made to the Current Available Position. Any Worker that becomes inactive has eir Position reset to GWF.

to

Any worker with a Management Position may Occasionally make a Story Post to the main page with the title “Restructuring” which contains proposed changes to the list of Current Available Positions.  All workers with a Management position may vote FOR or AGAINST the Restructuring by making a comment with the appropriate icon (with their latest vote overriding any previous votes).  If a majority of workers with a Management position vote FOR the Restructuring, it is enacted and its proposed changes to the list of Current Available Positions are made.  If this is not true after 48 hours, or if a majority of workers with a Management position vote AGAINST the Restructuring, or if a Worker with the CEO position has VETOed the Restructuring, then the Restructuring fails.

Add the following to the list of Current Available Positions in rule Position:

CEO
Name:Chief Executive Officer
Job Type: Management
Job Requirements: Only the ‘’‘CEO’‘’ can hold this position, and may at any time switch from this position to any other position, or vice versa.  A Worker with this position may take actions as though e holds any other position, and may cast a VETO on any Restructuring post.

A Layoff

In any merger there are some bound to be lost in the shuffle.  Gobleteer is one such poor soul.  Quorum is now 5.

Proposal: Resting the Machine, take 2 (as a proposal!)

6-1. Reached quorum.

Adminned at 04 May 2007 14:26:51 UTC

in rule 2.3.2 “Variables” change the following:

*Name: The name by which the Variable is refered (and any abbreviations by which it may be refered).
*Creator: The name of the Worker(s) considered responsible for adding the Variable to the Machine.
*Possible States: A description of the possible states the variable may be in.  If appropriate, a description of the order in which the variable advances may be included.
*State: The current State of the Variable (which must always be one of the possible states described in the previous bullet-point).

to:

*Name: The name by which the Variable is refered (and any abbreviations by which it may be refered).
*Creator: The name of the Worker(s) considered responsible for adding the Variable to the Machine.
*Possible States: A description of the possible states the variable may be in.  If appropriate, a description of the order in which the variable advances may be included.
*State: The current State of the Variable (which must always be one of the possible states described in the previous bullet-point).
*Default State: A Constant which is the same as the State of the Variable when it is first added to the Machine.

This gives us the option of reseting the entire machine, or pieces of the machine by using their Default States.

Proposal: Workbench #2

Quorumed (7-1)—Axeling

Adminned at 03 May 2007 16:16:36 UTC

Part 1

If there is a sub-rule entitled “Parts”, then insert the following bullet point at the end of the list of the bullet points in that sub-rule

* Size: The number and orientation of Workbench Squares that this Part would occupy if placed on the Workbench. (Examples: 1x1, 3 wide by 2 high).  The number of Cells must be a positive integer.  If the size is unspecified then the size is 1x1 (i.e., one Square).

If there is a sub-rule entitled “Variables”, then insert the following bullet point at the end of the list of the bullet points in that sub-rule

* Locatability and Size: An indication of whether or not this Variable may be placed on the Workbench.  If this Variable may be placed on the Workbench, then there must also be a statement of the number and orientation of Workbench Squares that this Variable would occupy if placed on the Workbench. (Examples: 1x1, 3 wide by 2 high).  The number of Cells must be a positive integer.  If the size is unspecified then the size is 1x1 (i.e., one Square).

Part 2

Insert a new sub-rule to the “Machine” rule, entitled “Workbench”, reading as follows:

The Workbench is a grid of Squares consisting of 6 rows labeled “A” through “F” (with A at the bottom) and 8 columns labeled “1” through “8” (with 1 on the left).  Individual Squares in the Worbench are thus identified “1A” (at the lower left” and so on through “6F” at the upper right.

Workbench Squares are considered “adjacent” if their positions on the Workbench grid are adjacent.  For example, Square 1A is adjacent to Squares 2A and 1B, but not adjacent to any other Squares.  The terms “above” and “beneath” may also be appropriately used to indicate Workbench Squares that occupy a position in the same column as a given Square.

In order for a Part to become part of the Machine, that Part must be placed in vacant Squares in the Workbench.  If a Variable’s description in the “Machine Variables” wiki page provides that the Variable may be placed in the Workbench, then the Variable may not become part of the Machine unless it is placed in vacant Squares in the Workbench.  Otherwise, it is not required that the Variable be placed on the Workbench in order to become part of the Machine.

Any given Square may not hold more than one Piece.  Placing a Piece in the Workbench is accomplished by indicating which column (or adjacent columns, if the Piece is more than 1 column wide) the Piece is dropped into.  The Piece then drops down to the lowest vacant Squares in that column.  For example, if the Workbench is empty and a 1x1 sized Piece is dropped in column 3 then the Piece falls down to Square 3A.  If another 1x1 sized Piece is then dropped in column 3 it falls down to Square 3B.  If a 2-wide by 1-high Piece is then dropped in columns 3 and 4 then it falls down to Squares 3C-4C.

Pieces “fall down” to the lowest vacant Squares in the Workbench columns that it occupies, but without changing its shape.  Thus, for example, if the Workbench is empty except for “PART-A” (a 1x1 sized Part located at Square 3A), “PART-B” (a 1x1 sized part located at Square 3B) and “PART-C” (a 2-wide by 1-high Part located at Squares 3C-4C), and PART-B is destroyed or removed from the Workbench, then PART-C will immediately “fall down” and change its location to Squares 3B-4B.  “Falling down” happens whether the Machine is Running or Standing By, and notwithstanding anything to the contrary in the “The Machine in Action” rule, occurs immediately upon the condition for “Falling down” occurring, and before any further Machine running steps may occur.

The Square or Squares on the Workbench occupied by a Piece may be referred to as that Piece’s Location.  A Piece that is not on the Workbench does not have a Location.

There exists a wiki page Workbench which describes the location of all Pieces on the Workbench.  The contents of this list are considered part of the Gamestate (and thus may not be modified except as permitted by the Ruleset).

 

Resting the Machine, take 2

in rule 2.3.2 “Variables” change the following:

*Name: The name by which the Variable is refered (and any abbreviations by which it may be refered).
*Creator: The name of the Worker(s) considered responsible for adding the Variable to the Machine.
*Possible States: A description of the possible states the variable may be in.  If appropriate, a description of the order in which the variable advances may be included.
*State: The current State of the Variable (which must always be one of the possible states described in the previous bullet-point).

to:

*Name: The name by which the Variable is refered (and any abbreviations by which it may be refered).
*Creator: The name of the Worker(s) considered responsible for adding the Variable to the Machine.
*Possible States: A description of the possible states the variable may be in.  If appropriate, a description of the order in which the variable advances may be included.
*State: The current State of the Variable (which must always be one of the possible states described in the previous bullet-point).
*Default State: A Constant which is the same as the State of the Variable when it is first added to the Machine.

This gives us the option of reseting the entire machine, or pieces of the machine by using their Default States.

Proposal: Resting the Machine

Self-kill. —Axeling

Adminned at 02 May 2007 21:25:54 UTC

in rule 2.3.2 “Variables” change the following:

*Name: The name by which the Variable is refered (and any abbreviations by which it may be refered).
*Creator: The name of the Worker(s) considered responsible for adding the Variable to the Machine.
*Possible States: A description of the possible states the variable may be in.  If appropriate, a description of the order in which the variable advances may be included.
*State: The current State of the Variable (which must always be one of the possible states described in the previous bullet-point).

to:

*Name: The name by which the Variable is refered (and any abbreviations by which it may be refered).
*Creator: The name of the Worker(s) considered responsible for adding the Variable to the Machine.
*Possible States: A description of the possible states the variable may be in.  If appropriate, a description of the order in which the variable advances may be included.
*State: The current State of the Variable (which must always be one of the possible states described in the previous bullet-point).
*Default State: The Base State which, when the Machine is Standing By, the Current State of the Variable is returned to (Note that setting Variables to their Default State does not Cause the Machine to become Runnig).

Because Ideally the machine will be reset each time, not started up again and again.

Proposal: I’m slightly worried about Time Freeze abuse.

Quorumed (7-0)—Axeling

Adminned at 02 May 2007 21:01:08 UTC

In the “Call for Judgment” rule, replace the word “Lifeforms” with “Workers”.

Add a paragraph to the “Call for Judgment” rule, just before the current last paragraph of that rule, reading:

If the CEO or any 3 other Workers make comments to a Time Freeze that include the VETO icon, then that Time Freeze is no longer considered a Time Freeze (but it is still a Call for Judgement), and provided there no other DoVs or Time Freezes pending, the Hiatus ends.

Proposal: Edits to Parts/Variables; Workbench

S.K.
-Amnistar

Adminned at 02 May 2007 17:05:27 UTC

Part 1: Changes to “Parts”

If there is a Rule 2.3.1 “Parts”, then rewrite the text that currently reads:

* Name: The name by which the Part is refered (any any abbreviations by which it may be refered).
...
* Initiator: The requirements that must be met for this Part to take effect.
* Effect: A description of changes to the “Machine Variables” wiki page”

so that it reads:

* Name: The name by which the Part shall be referred to (and the four-character abbreviation by which the Part shall be referred to).
...
* Size: The number and orientation of Workbench Squares that this Part would occupy if placed on the Workbench. (Examples: 1x1, 3 wide by 2 high).  The number of Cells must be a positive integer.  If the size is unspecified then the size is 1x1 (i.e., one Square).
* Attributes: (This element is optional) A list of any attributes that this Part has (e.g., edible, flammable, magnetic, and so on).  If a Part’s description does not specify that it has a particular Attribute then the Part does not have that Attribute.
* Activation Condition: (This element is optional) A description of a condition which, if true, activates this Part.  (In addition to the Activation Condition, if any, specified in the description of the Part on the wiki page, please note that the the description of another Part may expressly provide that the Activation of that Part will Activate this Part.
* Effect: A description of the effect or effects of Activating this Part.  This description may include checking the State of any number of Variables and setting forth the Effect of particular States of particular Variables.  Valid effects include: activating or deactivating any number of specified Parts (which may be specified by identifying the Part or the Location of the Part (e.g., “Activate any Part immediately adjacent to this Part on the right”), or, changing the State of any number of Variables,  changing the Location of any number of Parts, or destroying any number of Parts.  Only Parts that are part of the Machine may be affected. (example: effect of a Part entitled “Piranha”.  If the Variable “Piranha hunger status” has the state “Hungry” and the Variable “Piranha life status” has the state “Alive”, and the Square immediately to the right of this Part is vacant, and the Square that is immediately to the right of that vacant Square contains a Part that is Edible, then change the location of the Piranha by one Square to the right and destroy that edible Part.)

If there is a rule or sub-rule called “The Machine in action” then also add the following text to the end of the “Parts” rule:

“Whenever the Machine becomes Standing By, all Parts become deactivated.”

Part 2: Changes to “Variables”
If there is a Rule 2.3.2 “Variables”, then rewrite the text that currently reads:

* Name: The name by which the Variable is refered (any any abbreviations by which it may be refered).
...

so that it reads:

* Name: The name by which the Variable shall be referred to (and the four-character abbreviation by which the Variable shall be referred to.)

and add the following bullet point to the end of the “Variables” rule:

” Association with Part: If this Variable is associated with a particular Part, the name and/or abbrevation of that Part.  If that Part is destroyed or otherwise removed from the gamestate, then this Variable will also be deleted.”


Part 3: Workbench

If there is a rule “The Machine”, create a subrule entitled “Workbench” as follows:

The Workbench is a grid of Squares consisting of 6 rows labeled “A” through “F” (with A at the bottom) and 8 columns labeled “1” through “8” (with 1 on the left).  Individual Squares in the Worbench are thus identified “1A” (at the lower left” and so on through “6F” at the upper right.

Workbench Squares are considered “adjacent” if their positions on the Workbench grid are adjacent.  For example, Square 1A is adjacent to Squares 2A and 1B, but not adjacent to any other Squares.  The terms “above” and “beneath” may also be appropriately used to indicate Workbench Squares that occupy a position in the same column as a given Square.

In order for a Part to become part of the Machine, that Part must be placed in vacant Squares in the Workbench.  Variables may not be placed in the Workbench.

Any given Square may not hold more than one Part.  Placing a Part in the Workbench is accomplished by indicating which column (or adjacent columns, if the Part is more than 1 column wide) the Part is dropped into.  The Part then drops down to the lowest vacant Squares in that column.  For example, if the Workbench is empty and a 1x1 sized Part is dropped in column 3 then the Part falls down to Square 3A.  If another 1x1 sized Part is then dropped in column 3 it falls down to Square 3B.  If a 2-wide by 1-high Part is then dropped in columns 3 and 4 then it falls down to Squares 3C-4C.

Parts “fall down” to the lowest vacant Squares in the Workbench columns that it occupies, but without changing its shape.  Thus, for example, if the Workbench is empty except for “PART-A” (a 1x1 sized Part located at Square 3A), “PART-B” (a 1x1 sized part located at Square 3B) and “PART-C” (a 2-wide by 1-high Part located at Squares 3C-4C), and PART-B is destroyed or removed from the Workbench, then PART-C will immediately “fall down” and change its location to Squares 3B-4B.  “Falling down” happens whether the Machine is Running or Standing By, and notwithstanding anything to the contrary in the “The Machine in Action” rule, occurs immediately upon the condition for “Falling down” occurring, and before any further Machine running steps may occur.

The Square or Squares on the Workbench occupied by a Part may be referred to as that Part’s Location.

There exists a wiki page Workbench which describes the location of all Parts on the Workbench.  The contents of this list are considered part of the Gamestate (and thus may not be modified except as permitted by the Ruleset).

Wednesday, May 02, 2007

Proposal: People who work need jobs, take 2

Qourumed: 6-0
-Amnistar

Adminned at 02 May 2007 17:03:03 UTC

Create a new Rule “Position” with the text:

Each Worker has a value “Position” tracked in the GDNT. This Position is tracked by a 3 letter abreviation and is chosen from the list below.  Each Position has the following attributes:
=Position Acronym=
*Name: The full name of the Position
*Job Type: Either Labor or Managment
*Job Requirements: What activities the person with this Position may perform

The CEO may occasionally post a Story Post to the main page titled “Promotions/Demotions” which contains any changes in Positions for all Active Workers.  Occasionally the CEO or any Worker with a Management Position make a Story Post to the main page title “Restructuring” which contains changes to the Current Available Positions (below) and is voted on by all Workers with a Management position (per Proposal Rules), in the event of a Majority vote FOR those changes are made to the Current Available Position.  Any Worker that becomes inactive has eir Position reset to GWF.

There exist a wiki page “Created Pieces” which contains a list of pieces that have not been added to the machine.  Any Entry to this page must either be a Variable or a Part and contain all the information that they have, as well as the date which the part was added to the Created Parts page.

Current Available Positions:
=GWF=
*Name: General Workforce
*Job Type: Laborer
*Job Requirements: Any Worker that has this Position may occasionally add a single entry to the Created Pieces Page.  Upon doing so E must post a Story Post explaining eir action within 48 hours or the entry will be removed.

=EGM=
*Name: Engineering Group Member
*Job Type: Laborer
*Job Requrements: If there are at least 3 Workers with this Position, any Worker that has this Position may occasionally make a Story Post “Building the Machine” with a list of Pieces from the Created Pieces wiki page.  Each Worker with this position may vote on this Story Post, and if a Majority of Workers with this Position vote FOR the Parts in the post are added to the either the List of Parts or List of Variables for the Machine.

=QCC=
*Name: Quality Control Clerk
*Job Type: Laborer
*Job Requirements: Any Worker that has this Position may occasionally remove a single entry from the Parts section of the Machine. Upon doing so E must post a Story Post explaining eir action with 48 hours or the Part removed from the Machine will be added again.

=MDM=
Name: Moral Department Management
*Job Type: Management
*Job Requirements: Any Worker that has this Position must make all posts and proposals using one of the following poetic forms: Haiku, Lymeric, or Sonnet.

=HRM=
*Name: Human Resources Manager
*Job Type: Management
*Job Requirements: Any Worker that has this Position may Occasionally make a Story Post to the main page titled “Pay Day” or “Raise”.  If the Worker makes a Pay Day Post, every acvtive Worker may increase their Net Worth by their current Wage within 72 hours of the Story Post.  If the Worker makes a Raise Post, the text of the Post must include the name of every worker and a number between -10 and 10 if the worker has a Laborer Position, or between -30 and 30 if the Worker has a Management Position, ex. John: -1 (It is recommended that these raises reflect how well that Worker has performed the Job Requirements of eir current Position).  The CEO may then vote FOR or AGAINST the “Raise” post.  If the CEO votes AGAINST, the CEO may lower the Wage of the Worker that posted the “Raise” by up to 10.  IF the CEO votes FOR, then the CEO shall adjust the wages of each worker by the number listed next to eir name.

Set Every Worker’s Position to GWF and set the CEO’s Position to HRM.

Workbench and other stuff, take 2

This is still a draft, not a proposal.

WORKBENCH.  A grid of 6 rows labeled “A” through “F” (with A at the bottom) and 8 columns labeled “1” through “8” (with 1 on the left).  Individual grid-squares are thus identified “1A” (at the lower left” and so on through “6F” at the upper right.

In order for a Part to become part of the Machine, it must be placed in the Workbench.  This is accomplished by indicating which column (or adjacent columns, if the Part is more than 1 column wide) the Part is dropped into.  The Part then drops down to the lowest vacant grid squares in that column.  For example, if the grid is empty and a 1x1 sized Part is dropped in column 3 then the Part falls down to location 3A.  If another 1x1 sized Part is then dropped in column 3 it falls down to location 3B.  If a 2-wide by 1-high Part is then dropped in columns 3 and 4 then it falls down to locations 3C-4C.

Changes to the concepts of Parts and Variables:
Parts are physical, tangible objects such as a lever, a bell, a shotgun, an aircraft carrier, or a shark.  Variables are factual states such as: Position of Lever (permitted states: up, down).  Time of day (permitted states: Morning, Afternoon, Night).  Status of Mouse (permitted states: Awake, Asleep, Dead). 

Some Variables refer to conditions applicable to a particular Part- these can be referred to as “Part Variables”.  (examples: Position of Lever, Status of Mouse).  Other Variables do not refer directly to conditions applicable to a particular Part, but simply refer to a condition of the universe (example: Time of Day).  The definitions of “Part” and “Variable” in the rules are amended to conform with this.

A Part may become part of the Machine by being placed at a location in the Workbench.  Variables, being concepts rather than tangible things, do not have locations.

When a Part is activated, the Part may (but is not required to) check the status of any number of Variables, and the status of those Variables may affect the result of activating that Part.  For example, if a Part is a Lever, and there exists a variable entitled “Status of Lever (permitted states: Up, Down)”, and the description of the Lever is “If Lever is activated, check the status of Lever.  If Status of Lever is Down then do nothing.  If Status of Lever is up, then change the Status of Lever to Down activate the Part that is located immediately above the Lever, and increase the value of the Variable entitled “Number of Lever Clicks” by one.  Valid results of activating a Part may include, for example: changing the state of one or more Variables in specified ways, activating or deactivating one or more specifically named Parts or one or more Parts having a specified spatial relationship to the Part in question, or changing the location of one or more Parts.  Only Parts that are part of the Machine (i.e., that have locations) can be affected.

Draft: The Workbench

This is a draft, not a proposal.  I solicit comments.

The Workbench is a 10x10 grid of 100 positions, numbered consecutively from 1 to 100.  Position #1 is in the lower left hand corner and the positions are numbered in increasing order from left to right and from the lowest row of the grid to the highest row, with the upper right hand corner of the grid being Position # 100.

Positions are considered “adjacent” if their positions in the Workbench grid are adjacent.  For example, position #12 is adjacent to positions #2, 11, 13 and 22, but not adjacent to any other positions.  By way of further example, position 10 (being in the lower right hand corner of the grid) is not adjacent to position #1 or #11, but is adjacent to #9 and #20.

Each Part on the Machine is assigned to exactly one position on the Workbench.  Unless a rule provides otherwise, a new Part on the Machine is assigned to the position with a number one more than the highest numbered position that then contains a Part (even if a lowered number position is then vacant).  For example, if there are Parts at positions 1, 2, 3 and 5, then the next Part will be placed at position 6.

If a position becomes vacant and there is a Part in the position above it, then that Part moves to the vacant position.  For example, if there are Parts at all positions 1 through 30, but position 4 becomes vacant, then the Part at position 14 slides down to position 4, then the Part at position 24 slides down to position 14, then the Part at position 24 slides down to position 14.

Draft #1: Workers of the world, unite!

[This is a draft, not a proposal.  I solicit your comments.]

If there is no rule entitled “Position” then this proposal does nothing.

Add a new dynastic rule entitled “Labor Union” with the following text:

There is a set of Workers called the “Labor Union”.  The membership of the Labor Union consists of all Workers who are Laborers, but notwithstanding the foregoing, excludes all Workers who: (1) are Management, or (2) have been expelled from the Labor Union and have not been re-admitted.  The CEO is never a member of the Labor Union.  Each Worker who is included in the Labor Union may be referred to as a “Union Member”. 

Each Union Member has one vote with respect to any matters on which the Labor Union may vote.

There is a position of “President” of the Labor Union.  Only a Union Member may be the President of the Labor Union; if a Worker who holds the position of President of the Labor Union ceases to be a Union Member then the position of President of the Labor Union becomes vacant.

If at any time the position of President of the Labor Union becomes vacant, then the Labor Union may not take any action other than the election of a President of the Labor Union.  Such an election may be called by any Union Member if the position of President of the Labor Union is vacant.  To call such an election, a Union Member makes a story post to the blog declaring that the election has commenced, and the election ends three (3) days after the time of that post, whereupon Union Members may vote by posting responses to that story post.  The winner of the election is the Union Member who is selected by a plurality of the voters (only Union Members may vote, and a Union Member’s latest post containing a vote is the only post by that Union Member that counts for the purpose of the election).

[the main action that the Labor Union should be able to take is to declare a strike.  President proposes it, membership votes on whether to strike.  No Machine components can be added so long as a strike exists.  The point of a strike is to extract higher wages or other benefits that inure to all Union Members.]