Fewer than a quorum not voting AGAINST. Failed 1 vote to 7 by Kevan.
Adminned at 25 Jul 2025 16:15:41 UTC
Reword the Building Block that is called “Bounties” in the Building Blocks wiki page into “Request for Mechanic”, and rewrite it as follows:
A Request for Mechanic is a post in the Story Posts - Votable Matter category which broadly requests a single mechanical or ruleset change. Despite its category, it is not a votable matter and any votes on it are ignored. A Request for Mechanic may be Open or Closed being Open by default and being Closed when set to the ‘Enacted’ or ‘Failed’ status in the post backend. The Enacted Status should be used for successfully completed Request for Mechanic, while Failed should be used for ones that were closed for any other reason.
The Yard may post a Request for Mechanic, or close an open Request for Mechanic, at any time.
The Yard should vote For on any Votable Matter that satisfy the demands of a Request for Mechanic, or clarify which parts of the Votable Matter that the Yard feels said Votable Matter does not meet the goals of the Request for Mechanic.
If the Yard believes that one or more enacted votable matters satisfy the demand of an open Request for Mechanic, then they may set the Request for Mechanic to Enacted and apply any action that appear after “Rewards:” in the Request for Mechanic (if there is any) to each Truck (excluding the Yard) that authored those enacted votable matters.
Second draft; open for revision.
I feel that the current Bounty rule is underused because it does not match what is expected - Bounties is expected to be (if you do a predefined x; get y) as seen in the use of Bounties in The Coregency of ais523 and Josh; but mechanically it fits more of a “the emperor wants your input” role.
Kevan: Yard he/him
From a diff against the ruleset, your changes here are:
1. Renaming Bounties to “Requests for Mechanic”
2. Recommending that the Emperor vote for proposals that address the Request
3. Replacing the dynastically defined Payout with one that the Emperor defines in the Request
1 seems too specific, as it’s not always going to be a request for a mechanic. It might be a fix, or some flavour, or adding more items to a list.
2 seems redundant and mildly risky: if the Emperor asks for a way to slow down the tree-growing mechanic and someone proposes “start a metadynasty” or “repeal all core rules”, the Emperor is encouraged to support that.
3 I’m not sure about. It can’t realistically be abused (it’s nothing an Emperor can’t propose to do anyway), but there’s some risk of Emperor blindness in having them pick the reward each time, rather than the group agreeing on one.