Proposal: Make CfJs more reliable [Core]
Change the core rule “Calls for Judgement” to read as follows:
Any Snail or Idle Snail can raise a Call for Judgement (abbreviated “CfJ”) by posting an entry in the “Call for Judgement” category. Snails are encouraged to do this only when two or more Snails actively disagree as to the interpretation of the Ruleset, or when a Snail feels that an aspect of the game needs urgent attention.
A Pending CfJ may be Enacted by any Admin or Idle Admin if either of the following is true:
- It is Popular.
- It was posted between 48 and 120 hours ago, and has been open for comments and in the “Call for Judgement” category ever since it was posted, with no comments containing an AGAINST voting icon having been made to it.
A Pending CfJ may be Failed by any Admin or Idle Admin if either of the following is true:
- It is Unpopular.
- It specifies neither changes to the gamestate or ruleset nor corrections to any gamestate- or ruleset-tracking entities.
When a CfJ is Enacted, the gamestate and ruleset are updated as specified in the CFJ, and the Admin or Idle Admin Enacting it shall update the ruleset-tracking page and gamestate-tracking entities accordingly.
Dynastic rules cannot prevent or limit the creation of CfJs and cannot prevent or limit changes being made via CfJ enactment. This rule cannot be overruled by a dynastic rule.
In the core rule “Votes”, change:
Additionally, if the author of a Votable Matter has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR.
to
Additionally, if the author of a Votable Matter is not idle and has not used a valid voting icon in a comment to the post, then the author’s Vote is FOR.
It seems useful for idle Snails to be able to create CfJs; I’ve created two CfJs on behalf of idle Snails already this dynasty, and it could also help us recover if (for whatever reason) we become uncertain about who is and isn’t idle. Some other miscellaneous bugfixes and improvements to the CfJ rule while I’m there: a) allow CfJs to be enacted unanimously, even if voting is broken for some reason (with anti-scam precautions just in case); b) CfJs don’t become secretly/silently illegal based on the mental state of the person posting them (although using CfJs as proposal-equivalents is discouraged, it shouldn’t make the CfJ illegal and thus unenactable, and yet it does under the current rules); c) make it explicit that dynastic rules can’t prevent the gamestate being changed via CfJ, nor prevent the creation of CfJs; d) an enacted CfJ still updates the gamestate and ruleset even if the enacting admin fails to complete the action correctly.
Josh: he/they
I guess I have a bit of a problem with this. Maybe it’s just a hangover from the end of Lulu 3 but I tend to view idle meddling in an ongoing dynasty to be more often malign than not; the use cases in this dynasty are a good example for the proposal but it could equally be the case that, say, a slow dynasty keeps getting peppered by “wrap it up” CfJs from idle players, and that could become extremely annoying. It also seems likely that idle players will start using CfJs as proposals that they can actually carry out, especially for core and appendix changes; that might not be bad in effect but should be explicit.
On a practical note, it is possible for a CfJ under this proposal to be both enactable and failable (if it has zero votes cast on it it will be unpopular, meeting this ‘has been open for voting for at least 48 hours and it is not Popular’ criterion, as well as meeting the new criterion for enactability).