Experiment

From BlogNomic Wiki
Jump to navigation Jump to search

Core Rules

Ruleset and Gamestate

This is the Ruleset for BlogNomic; all Musicians must obey it. Section One consists of the "core rules" of blognomic, covering basic proposal mechanics; Section Two contains the rules of the current dynasty; and Section Three contains the glossary, which exists solely to clarify the remainder of the ruleset. Rules may be referred to by their type and entire number or type and name. (e.g. This Rule may be referred to as Rule 1.1 or the Rule entitled "Ruleset and Gamestate").

The Ruleset and Gamestate can only be altered in manners specified by the Ruleset.

No Rule may contain a provision that bars itself from being altered and/or repealed. If at any moment a Rule exists or is altered in a manner that renders it to contain such a provision, the entirety of that Rule shall be considered void and with no effects on the Gamestate. The provisions on this paragraph supersede any text in a Rule.

Spivak pronouns, as defined in the Glossary, shall be used whenever a Musician is referred to.

Admins may correct obvious spelling and typographical mistakes in the Ruleset at any time.

Musicians

Anybody may apply to join BlogNomic (if e is not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post announcing eir arrival. An Admin will add em to the roster in the sidebar, at which moment e becomes a Musician.

A Musician may leave the game at any time by posting an entry to the BlogNomic weblog requesting such an action. A Musician may only change eir name as a result of a proposal approving the change.

Some Musicians are Admins, responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Musicians who wish to become Admins shall sign up with a username for the Ruleset Wiki, and submit a Proposal to make themselves Admins. Existing Admins may be removed from their posts by Proposal, CfJ, or voluntary resignation.

Some Musician are idle, and shall be marked as such in the sidebar. For the purposes of the Ruleset, excluding Rules 1.1 and 1.2, idle Musicians are not counted as Musicians. Admins may render a Musician idle if that Musician has failed to vote for more than a week or has asked to become idle. Admins may un-idle a Musician at eir request - the Musician's personal gamestate retains the values it had immediately prior to eir idling.

A single person may not control more than one Musician within BlogNomic. If anybody is suspected of controlling more than one Musician, then a Proposal may be made to remove any number of such Musicians from the game, and to bar the perpetrator from rejoining.

Proposals

Any Musician may submit a Proposal to change the Ruleset or Gamestate, by posting an entry in the "Proposal" category that describes those changes (unless the Musician already has 2 Proposals pending, or has already made 3 Proposals that day).

Proposals can either be Pending, Enacted, or Failed. When a Proposal is first put forward, it is considered Pending.

Voting

Any Musician may cast eir Vote on a Pending Proposal by making a comment on that entry using a voting icon of FOR, AGAINST or DEFERENTIAL.

If the Musician who made a Proposal has not cast a Vote on it, eir Vote is counted as FOR. If a Musician casts more than one Vote on a Proposal, only the most recent of those Votes is counted. If a Musician leaves the game or goes idle, eir Vote no longer counts. If a Musician votes against eir own proposal, that vote may not be changed.

A vote of DEFERENTIAL is a vote of no opinion, or of faith in the decision of the Conductor. The vote will count as the same as Conductor's vote. The Conductor cannot cast a vote of DEFERENTIAL. If there is no Conductor, a vote of DEFERENTIAL counts as an explicit vote of abstention.

Enactment

The oldest pending Proposal may be enacted by any Admin (and the Ruleset and/or Gamestate updated to include the specified effects of that Proposal) if either of the following is true:-

  • It has a number of FOR votes that exceed or equal Quorum, has been open for voting for at least 12 hours, and has not been vetoed or self-killed.
  • It has been open for voting for at least 48 hours, it has more than 1 valid vote, more than half of its votes are FOR, and it has not been vetoed or self-killed.

The oldest pending Proposal may be failed by any Admin, if any of the following are true:-

  • It has enough AGAINST votes that it could not be Enacted without one of those votes being changed.
  • It has been open for voting for at least 48 hours and half or fewer of its votes are FOR.
  • It has been open for voting for at least 48 hours and has fewer than 2 valid votes.
  • The Musician who proposed it has voted AGAINST it.
  • The Conductor has voted to VETO it.

Whenever an Admin marks a proposal as enacted or failed, e must also mark eir name, and report the final tally of votes (or the fact that the proposal was self-killed or vetoed).

Calls for Judgment

If two or more Musicians actively disagree as to the interpretation of the Ruleset, or if a Musician feels that an aspect of the game needs urgent attention, then any Musician may raise a Call for Judgment by posting an entry in the "Call for Judgment" category. If the Musician wishes, e may post anonymously by choosing "Call for Judgment" from the Author drop-down menu on the OPTIONS tab. The post shall go on to describe the issue, and measures that shall be taken to resolve it.

All Musicians may add votes of agreement or disagreement in comments to this entry, using appropriate voting icons (a Musician's later votes overriding eir earlier ones). Unfailed CfJs continue until they reach a quorum of FOR votes, a quorum of AGAINST votes, or if there is no hiatus going on, until four days have passed, and if there is a hiatus going on until two days have passed. After this time, if more than half of the cast votes are in favour, the Gamestate and Ruleset shall be amended as was specified. Otherwise, the CfJ fails. A Failed CfJ has no further effect.

Gamestate Tracking

Proposals, Calls for Judgment, and other official posts, as well as specific gamestate information, shall be tracked by the BlogNomic blog at http://blognomic.com. Any Musician may post to the blog at any time, but may only make official posts to the blog when the Ruleset allows it. Posts following the format specified by a rule are considered official posts.

If no Musician has commented on it, an official post may be altered or removed by its author; otherwise this can only be done as allowed by the Ruleset. The Admin processing an official post is allowed to append to the post to reflect its new status. Anything appended to a post in this way must be placed in the Admin field of the post, and the post's Status must changed to reflect its status.

A non-official post may not, through editing of the blog or otherwise, be changed into an official post, with the following exception. Whilst a non-official post has been posted for less than five minutes and has no comments, the author may change the categories as e wishes.

Voting and comments are accessible through the link at the bottom of every post.

Specific parts of the Gamestate data shall be tracked by the Generic Nomic Data Tracker at http://blognomic.com/gndt/generic.cgi?nomic=blog. Any Musician may update any Musician's data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged - if a Musician feels that an alteration goes against the Rules (as they were at the time of the alteration), e may simply undo the effects of that alteration. If such an undoing is disputed, a Call for Judgment shall be raised.

Musicians shall be assigned a password for the GNDT when they join the Nomic.

Dynasties

BlogNomic is divided into a number of Dynasties. Each Dynasty is headed by a single Conductor, and is named according to the number of Dynasties they have headed (eg. "The First Dynasty of Myke").

The Conductor may vote to VETO any Proposal.

Victory and Ascension

If a Musician (other than the Conductor) believes that e has achieved victory in the current Dynasty, e may make a post to the Blognomic weblog in the Declaration of Victory category, detailing this.

Upon doing so, the game immediately game goes into Hiatus, if it hasn't already. During this time, the only game actions that may be taken are those covered by Rules 1.2, 1.6, 1.7 and 1.9.

Every Musician may respond to an active DoV saying whether or not e believes the poster has achieved victory in the current Dynasty (using the FOR and AGAINST icons).

The Declaration of Victory may be resolved after 24 hours, or after 12 hours if the Conductor has voted on it. Upon resolution, if a Quorum of Musician's have voted on the DoV and more than half of those votes were in favour, then the DoV passes - otherwise the DoV fails, and if no other DoVs are still pending, the Hiatus ends.

When a DoV passes, all other active DoVs are failed, and a new Dynasty begins with the Musician who made the DoV as its Conductor. (That Musician may pass this role to another Musician at this point, if they wish.) The Hiatus continues until the new Conductor posts an Ascension Address to the BlogNomic weblog - this shall specify Conductor's chosen theme for the new Dynasty, and may optionally include a proclamation that any number of Dynastic Rules will be repealed, and that any keywords will be replaced with new theme-appropriate terms.