Friday, January 29, 2021

Proposal: Subversion Escalation, Take Three

Timed Out. Fails 1-3—Clucky

Adminned at 31 Jan 2021 18:52:40 UTC

Create a new rule entitled “Imperial Devolution [Universal]” with the following text:

The Player may not veto any Proposals do not include at least one of the following tags: [Core], [Special Case], [Appendix], [Victory]. If a Proposal would cause the game to become unplayable; would effectively amend or allow arbitrary amendment of a Core, Special Case, or Appendix rule; or would grant immediate victory to the enacting Admin; then, instead, the Player may and should veto that Proposal.

Delete the text in the rule “Treaties [Universal]” that reads “The Player should veto any proposal that would make an Emperor a Signatory to a Treaty against his will, or that would convert a Treaty into a Universal rule without the assent of all non-Signatory Emperors. Moreover,”

Add a new subrule to the rule “Treaties [Universal]” called “Treaty Limits [Universal]” that reads as follows:

A Proposal that creates or amends a Treaty is considered Unpopular, and is not considered Popular, so long as any of the following would be true of its effects upon enactment:

  • They would make an Emperor a Signatory to a Treaty without that Emperor’s consent.
  • They would convert a Treaty into a Universal rule.
  • They would add or remove Signatories from another Treaty, except as mediated by Universal rules.
  • They would restrict the actions of non-Signatories, beyond not being able to act as Signatories.
  • They would avoid the requirement that the Player always be a Signatory.
  • They would make substantial modifications to another Treaty, such that it effectively becomes a different Treaty.
  • They would enable arbitrary rules modifications.

However, the foregoing list of conditions excepts the following cases:

  • A Treaty may affect its own subrules. Subrules of a Treaty may affect the parent Treaty or other subrules of that Treaty.
  • Treaties may have terms specific to mutual Signatories with other Treaties—for example, by modifying variables defined in the other Treaty.
  • Treaties may declare the Player and other Signatories as second-class Signatories who may not take certain actions.

Enact the rule modifications set forth in Bucky’s proposal entitled “Universality Incorporated” from January 27th of 2021.

If Bucky’s proposal entitled “Idle Signatures” from January 27th of 2021 did not enact, then enact its rule modifications as well.

Modified to account for requests to keep all of this as dynastic material.

Comments

Bucky:

29-01-2021 18:27:41 UTC

Hmm, so you’re giving up the opportunity to try to slip one by me, and instead making failure platonic? That seems brittle, as we might notice a forced Signature method or other violation only after the fact.

You also appear to have inverted the relationship where parents can modify subrules.

Brendan: he/him

29-01-2021 18:46:11 UTC

Is your position that relying entirely on you to veto things at your own discretion is somehow less brittle? Updated to allow all relationships between Treaty parent rules and subrules.

Clucky: he/him

29-01-2021 19:43:17 UTC

I see a number of issues with this. Will be voting against unless they are resolved

> They would restrict the actions of non-Signatories, beyond not being able to act as Signatories.

This would prevent a treaty from locking itself from future signatories. Do we want that?

> They would make substantial modifications to another Treaty

I feel like this is far too subjective for an admin to have to try and adjudicate. I think its fine if its just one person making the call but I’m not a fan of having proposals that one admin will pass and a different admin will fail, and this creates that exact scenario.

> They would enable arbitrary rules modifications.

I feel like there are some halting problem type issues with this. An admin can not necessarily be sure if a rule actually enables arbitrary rules modifications.

> Subrules of a Treaty may affect the parent Treaty or other subrules of that Treaty.

Right now, subrules are their own treaty. This would enable people to effect rules which they are not a signatory to, which is part of the problem we want to avoid.

Brendan: he/him

29-01-2021 21:00:59 UTC

Thank you for the fifteen-minute warning, Clucky, but I’m afraid it wasn’t enough; I can’t modify this post anymore. All of the points I put in this list are direct copies of the ones you and Bucky collaborated on for the “Veto Conditions” protosal, so I’m not sure why you haven’t raised objections there in the last two days.

I’m not against modifying the list—I LIKE more wiggle room on proposals—but this was written to thread the needle of Bucky’s and Kevan’s against-votes. Would you consider proposing to amend this if it passes, rather than vetoing before any of those issues actually come up?

Clucky: he/him

29-01-2021 22:00:24 UTC

I responded to the proposal when I noticed it was up

Also outside of a comment where I pointed out that someone could significantly change a treaty and you’d still be bound to it, which is one of the items Bucky tried to fix in his list, I haven’t actually had any input with Bucky on his list. I didn’t even really pay much attention to the post he made, because it wasn’t a proposal. But taking a look at his list now

- The first issue I raised is still there. I would point out the problem, but its not a big enough deal that I would kill the proposal over it.

- The second issue boils down to a problem with subjectivity. As long as the rule was “The Player *should* veto a proposal if these are true” then you no longer have the subjectivity problem. If Bucky feels the proposal makes substantial modifications to another Treaty, its all fine.

But if you either say “Bucky must do this” or “Any Admin may do this” then you run into subjectivity problems which are a mess I don’t think we really want to get into

- the third issue is much the same. I don’t think its possible to ban proposals that enable arbitrary rules modifications. But if you make it a “should” then the subjectivity of whether a proposal actually enables arbitrary rules modifications is moot, and if a proposal that does in fact arbitrary rules modifications sneaks through the rules then its still all legal

- the final issue was introduced by you, as Bucky’s list only allows parent rules to mess with its subrules, and every signatory of a subrule is a signatory of the parent rule. It is only if you allow subrules to mess with other subrules where the “a rule which I’m not a signatory to is messing with a rule which I am a signatory to” becomes a problem.

I do not believe that its safe to make it so that the admining of rules arbitrarily depends on the interpretations that the person doing the admining makes. Especially when the rules provide a way for other players to veto any changes we want to later make, even if the rest of the blog is onboard with making those changes.

I also don’t really understand the problem we’re trying to fix with this proposal in the first place.

Kevan: he/him

30-01-2021 09:29:39 UTC

against Still seems a fool’s errand to try to define “game-breaking proposals” as a short, exhaustive list, and yes, the platonic failure is a problem, particularly when some of the things on that list could be done subtly or accidentally (allowing a scam of “surprise, that proposal didn’t actually enact two weeks ago”).

Darknight: he/him

30-01-2021 13:46:37 UTC

against

Bucky:

30-01-2021 19:50:53 UTC

against  per Kevan

Raven1207: he/they

31-01-2021 18:16:17 UTC

against