Sunday, February 06, 2022

Proposal: Al In This Together

Reached quorum, 7-1. Enacted by TyGuy6.

Adminned at 08 Feb 2022 18:38:44 UTC

Create a new rule called “Alan” as follows:

Alan is an NPC whose actions are controlled by the CEO. For the purposes of Dynastic Rules, Alan is considered an Employee.

Alan is the only member of a team called Logistics (which is distinct from all other teams) and may not transfer to another team. Any time Alan would receive an increase in Vested Value, that increase is instead applied to the Company Budget.

When Alan moves between departments, a faint buzzing and whirring sound can be heard. This has no effect on the ruleset or gamestate, but it is creepy.

In the rule “Teams”, replace:

The CEO has the sole power to set and/or change an Employee’s Team, with the exception that they are unable to change an Employee’s Team to or from On Strike, except as described in the rule On Strike. An Employee’s Team is publicly tracked.

An Employee who is unhappy in their current Team is encouraged to submit a transfer request to the CEO. Any Employee that does not belong to a Team must be assigned one at the CEO’s earliest convenience.


As a Weekday Action, an Employee may Transfer to another Team by changing their Team to one whose members have a total combined Production equal to or lower than their current team.


Brendan: he/him

07-02-2022 01:51:36 UTC

We’ve really got to get around to defining “NPC” someday.

Brendan: he/him

07-02-2022 01:52:58 UTC

(Also, a little worried about the potential of reading “When Alan moves between departments… This has no effect on the ruleset or gamestate”)

Zack: he/him

07-02-2022 06:35:18 UTC

That’s what I get for trying to be creative… just kidding, I think the rule is pretty unambiguous about Alan’s ability to move between departments; the only thing that has no effect is the clause about that cute and not-at-all suspicious noise they make.


07-02-2022 06:57:02 UTC

for This is a much cuter version of what I wrote up for Zack. Also, I read the proposal’s name as AI, at first.

Clucky: he/him

07-02-2022 08:06:17 UTC


I have two concerns with this:

One concern is mechanical: the “Any time Alan would receive an increase in Vested Value, that increase is instead applied to the Company Budget.” is exponential, which could result in the company budget getting way out of hand. Zack can freely pass a couple of promotional proposals for Alan. So say you get him up to rank 4. Then every day, you’re basically multiplying the company budget by 5 (as Alan gets their options increase in, then cashes out). Pretty soon budget would lose its meaning

The second is that we’re in the endgame, and so want to avoid big mechanical changes like this even if they work. Feels like things could easily come down to “hey Zack can you do some Alan actions so that my options will be worth enough to buy the last BCC shares?”

Josh: he/they

07-02-2022 09:59:30 UTC

for What happens if Alan achieves victory?

Brendan: he/him

07-02-2022 13:48:20 UTC

imperial Robot emperor! Robot emperor!

ATMunn: he/him

07-02-2022 15:46:16 UTC


Zack: he/him

07-02-2022 18:15:25 UTC

@Josh Nothing happens, Alan can’t make aDoV.


08-02-2022 05:11:42 UTC


Snisbo: she/they

08-02-2022 16:43:00 UTC


Snisbo: she/they

08-02-2022 16:58:27 UTC

On second thought, which team would get options under the change to transferring?