Remove the items “Can”, “May”, “May not”, “Shall” and “Should” from the Glossary.

Remove the items “Daily Action”, “Daily Communal Action”, “Weekly Action” and “Weekly Communal Action” from the Glossary.

Add a new rule to the glossary, entitled Imperatives and Frequencies:

An Action is any activity that the ruleset specifically permits Readers to carry out, and regulates the usage of.

The ruleset regulates the usage of Actions through Imperatives and Frequencies. A Frequency defines how frequently an Action may be undertaken by each Reader. An Imperative defines the circumstances within which Readers can undertake an Action. The keywords used below to describe Imperatives and Frequencies are only keywords in that context when they apply to Actions, as defined in this rule. In all other situations, they take their regular English meaning.

Add a sub-rule to that rule, entitled Imperatives:

Imperatives in use within BlogNomic are as follows:

• Can or May: A Reader can carry out this Action at any time, with no restrictions beyond those otherwise explicitly defined by the Ruleset.
• Should: A Reader should carry out this Action at their first opportunity. The “should” imperative confers flexibility upon the gamestate but not the Reader; a Reader must treat the “should” imperative upon an Action that applies to themselves as if it were a “must”, but their failure to do so does not put the gamestate into an illegal state. The failure of a Reader to carry out an Action with a “should” imperative may be the subject of a CfJ, if it cannot otherwise be trivially resolved, but such a CfJ may not present a retroactive remedy.
• Must or Shall: A Reader must carry out this Action before any further Actions are taken, and their failure to do so would put the gamestate into an illegal position. It is suggested that this Imperative is primarily used for subordinate Actions or steps undertaken in the carrying out of other Actions.

If the gamestate has been in an illegal state for seven days due to an Reader’s failure to carry out an action with a “Must” imperative, and no CfJ has been raised that identifies and seeks to remedy that failure; or if the gamestate has been in an illegal state for fourteen days, and no CfJ that identifies and seeks to remedy that failure has passed, or if the the gamestate is in an illegal state due to an Reader’s failure to carry out an action and that Reader has since become idle due to inactivity without carrying out any subsequent Actions, then the gamestate ceases to be in an illegal state and the failure to carry out that action is considered legal.

In that event that any Imperative is immediately followed by the word “not”, it instead means that the described Action is strictly forbidden under the stated circumstances, or under all circumstances if not further qualified.

Add another new subrule to the rule “Imperatives and Frequencies”, entitled Frequencies:

Frequencies in use in BlogNomic are as follows:

• Daily: A Reader may carry out this Action once per Day, but not more than once in any four-hour period.
• Bi-daily: A Reader may carry out this Action once every two Days, but not more than once in any twelve-hour period.
• Weekly: A Reader may carry out this Action once every Week, but not more than once in any twenty-four-hour period.

Action frequencies may be modified as follows:

• Communal: Any Action that is marked as Communal may only be carried out by a single Reader in the stated Frequency period.
• X-Usage: Any Action that is marked as X-Usage, where X is any integer, may be carried out X times in its Frequency period.

In “Ruleset and Gamestate”, change “The Ruleset and Gamestate can only be altered in manners specified by the Ruleset” to “The Ruleset and Gamestate must only be altered in manners specified by the Ruleset”.

In “Resolution of Proposals”, change “If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and can be failed by any Admin” to “If a proposal somehow ends up being pending for more than 7 days, it is ignored for the purpose of calculating the oldest pending proposal, and should be failed by any Admin”.

In “Seasonal Downtime”, change “During this time no game actions may be taken” to “During this time game actions may not be taken”.

In “Drawing”, remove “choose to” and “at any time” in items 5, 6 and 7 in the numbered list.

In “Discards”, change “then any Reader may remove all the Cards from each Reader’s Discard pile” to ” then any Reader should remove all the Cards from each Reader’s Discard pile”.

In “Fair Play”, change all instances of “should” in the 2nd, 3rd, 4th and 6th bullets to “must”.