BlogNomic: The First Dynasty of Desertfrog

Add a new dynastic rule called “Old Sarum”, as follows:

A proposal is subject to Team Voting if any of the following is true with respect to that proposal:
- the text of the proposal unambiguously states that the proposal shall be subject to Team Voting; or
- the proposal would not directly change the ruleset.
(Note that Declarations of Victory and Calls for Judgment are not proposals and, as such, are never subject to Team Voting).
A “Team Vote” of a given team with respect to a proposal that is subject to Team Voting is: (A)  “FOR” if a majority of the members of that team who cast votes on that proposal included “FOR” votes in their EVC for that proposal; and (B) “AGAINST” if a majority of the members of that team who cast votes on that proposal included “AGAINST” votes in their EVC for that proposal; and (C) an abstention, if the number of “FOR” votes and “AGAINST” votes cast by team members in their respective EVCs are evenly divided, or if no members of that team cast votes on that proposal.

If a proposal is subject to Team Voting, then notwithstanding the normal voting rules that relate the enactment or failing of proposals, the proposal shall be enacted if there are more Team Votes “FOR” the proposal than Team Votes “AGAINST” the proposal; and failed otherwise.

The enactment or failure of proposals (as opposed to the operation of the proposal itself in accordance with the proposal’s terms) that are subject to Team Voting shall not, in and of itself, result in points being awarded or taken away, anything to the contrary in the Ruleset notwithstanding.