Ruleset 79

From BlogNomic Wiki
Revision as of 05:32, 3 November 2014 by 75th Trombone (talk | contribs) (1 revision)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Contents

Core Rules

Ruleset and Gamestate

This is the Ruleset for BlogNomic; all Citizens shall 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.

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

Admins may correct obvious spelling and typographical mistakes in the Ruleset at any time, including replacing Spivak and gender-specific pronouns with the singular "they".

Citizens

Anybody may apply to join BlogNomic (if they are not already playing) by registering at http://blognomic.com via the Register link in the sidebar, and then making a post announcing their arrival. An Admin shall add them to the roster in the sidebar and the GNDT, at which moment they become a Citizen.

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

Some Citizens are Admins, responsible for updating the site and the Ruleset, and are signified as such in the sidebar. Citizens who wish to become Admins may 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. New admins shall be given the GNDT configuration password when they become admins.

Some Citizens are Idle, and shall be marked as such in the sidebar. For the purposes of the Ruleset, excluding Rules 1.1, 1.2, 1.8 and 1.10, Idle Citizens are not counted as Citizens. Admins may render a Citizen Idle if that Citizen has asked to become Idle or if that Citizen has not posted an entry or comment in the last seven days. In the latter case, the Admin must announce the idling in a blog post. Admins may render themselves Idle at any time by announcing that they have done so in a blog post. Admins may de-Idle an Citizen at his request, and Idle Admins may de-idle themselves at any time, unless the idle Citizen in question asked to become (or rendered themselves) Idle within the previous 4 days, and within the current dynasty. The Citizen’s personal gamestate retains the values it had immediately prior to his going Idle. If one or more values would be undefined, it is set to the value new Citizens receive, if such a value exists.

Proposals

Any Citizen may submit a Proposal to change the Ruleset or Gamestate, by posting an entry in the "Proposal" category that describes those changes, except that:

  • A Citizen cannot submit a non-Core Proposal if that Citizen already has two or more non-Core Proposals pending.
  • A Citizen cannot submit a Proposal if that Citizen already has three or more Proposals pending.
  • A Citizen cannot submit a Proposal if that Citizen has already submitted three or more Proposals that day.

Proposals can either be Pending, Enacted, or Failed. When a Proposal is first put forward, it is considered Pending. A Proposal may not also be a Call for Judgment.

Voting

Any Citizen may cast their Vote on a Votable Matter by making a comment to the official post that comprises that Votable Matter using a voting icon of FOR, AGAINST, DEFERENTIAL (only if the Votable Matter is a Proposal), or VETO (only if the Votable Matter is a Proposal and the Citizen is the High-Programmer).

If the Citizen who authored a Votable Matter has not cast a Vote on it, their Vote is counted as FOR. If a Citizen uses more than one Voting Icon in comments on a Votable Matter, their Vote is the last voting icon they use. If a Citizen leaves the game or goes Idle, their Vote is no longer valid. If a Citizen Votes against their own Proposal, this renders the Proposal self-killed and that Vote may not be changed.

A Vote of DEFERENTIAL is a Vote of no opinion, or of faith in the decision of the High-Programmer. The Vote will count as the same as the High-Programmer’s Vote. If the High-Programmer casts a Vote of DEFERENTIAL on a Proposal, it serves the purpose of cancelling any previous Vote on that Proposal that was cast by the High-Programmer and counts as an explicit Vote of abstention. If there is no High-Programmer, or the Vote is made by the proposal’s author on their own proposal and the High-Programmer does not Vote on it, a Vote of DEFERENTIAL counts as an explicit Vote of abstention, and has no effect except possibly to void earlier voting icons by that voter on that proposal.

If no High-Programmer has Voted on a Proposal, a Vote of DEFERENTIAL on that proposal does not count as a Vote for the purposes of rule 1.5.

Resolution of Proposals

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 continuously been a proposal for that time, 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 Citizen who proposed it has Voted AGAINST it.
  • The High-Programmer has Voted to VETO it

If the High-Programmerhas voted to VETO a proposal and that Vote’s comment includes the word “Procedural”, the vetoed proposal can be failed immediately by any admin, even if it is not the oldest pending proposal.

Whenever an Admin marks a proposal, CfJ, or DoV as enacted or failed, they must also mark their name, and report the final tally of Votes (or the fact that it was self-killed or vetoed).

Proposals the High-Programmer has Voted to VETO are considered vetoed, and such a Vote cannot be changed. Proposals the author has Voted against are considered self-killed unless the High-Programmer has Voted VETO on them, or they have fulfilled one of the other requirements to fail a proposal before the author’s self-kill Vote is placed. Immediately after enacting a proposal that causes a rule with no name to be added to the ruleset, unless the proposal specifically states that the rule should have no name, the enacting admin can change the rule’s title to give it a name, so long as doing so does not change the meaning of any part of the ruleset, nor change any properties of the rule (such as specific words in the title) that the ruleset specifically cares about.

Calls for Judgment

If two or more Citizens actively disagree as to the interpretation of the Ruleset, or if a Citizen feels that an aspect of the game needs urgent attention, then any Citizen may raise a Call for Judgment (abbreviated CfJ) by posting an entry in the “Call for Judgment” category. The post shall go on to describe the issue, and measures that shall be taken to resolve it.

All Citizens may cast Votes on that CfJ to indicate agreement or disagreement with the position taken in that CfJ. 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 the cast Votes are FOR Votes, the CfJ may be enacted by any Admin by updating or correcting the Gamestate and Ruleset as specified. Otherwise, the CfJ fails. A Failed CfJ has no further effect.

Any CfJ that has no effect on the ruleset or gamestate may be automatically failed by any admin.

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 Citizen 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 Citizen 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. However, despite this, official posts can never be changed from one category to another, or changed to be a different sort of official post, if they have been posted for more than fifteen minutes. 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 be 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 fifteen minutes and has no comments, the author may change the categories as they wish.

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 Citizen may update any Citizens data via the GNDT, whenever the Ruleset permits it.

All updates to the GNDT are logged. Actions that change gamestate directly (defined in other rules) can normally be performed simply by applying their effects to the GNDT, which updates the gamestate accordingly, unless another rule specifies some other method of performing them; one GNDT update may contain one or more actions, or one action may be split over multiple GNDT updates, as long as it’s clear what is happening and the actions are otherwise legal. The GNDT merely represents the Gamestate, and is not the same thing. In the event that the Gamestate and the GNDT are different, any Citizen may correct the GNDT to comply with the Gamestate.

If a Citizen feels that the GNDT was altered such that it no longer matches the gamestate (such as by performing an action which was against the Rules (as they were at the time of the alteration), or by any other means), they may simply undo the effects of that alteration. Instead of repeatedly reverting and re-reverting a disputed GNDT update, Citizens are encouraged to raise a Call for Judgment instead. Citizens 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 Citizen, known as the High-Programmer, and is named according to the number of Dynasties they have headed (eg. "The First Dynasty of Myke").

The High-Programmer may Vote to VETO any Proposal.

Victory and Ascension

If a Citizen (other than the High-Programmer) believes that they have achieved victory in the current Dynasty, they may make a post to the Blognomic weblog in the Declaration of Victory category, detailing this.

Upon doing so, the game immediately goes into Hiatus, if it hasn’t already. During this time, the only game actions that may be taken are those covered by Rules “Citizens”, “Voting”, “Calls for Judgment”, “Gamestate Tracking” and “Victory and Ascension”.

Every Citizen may cast Votes on that DoV to indicate agreement or disagreement with the proposition that the poster has achieved victory in the current Dynasty.

A DoV may be enacted if any of the following is true:

  • It has been open for voting for 12 hours, has a number of FOR Votes that exceed or equal Quorum, and either the High-Programmer has Voted FOR it or it has no AGAINST Votes.
  • It has been open for voting for at least 24 hours, has a number of FOR Votes that exceed or equal Quorum, and has a number of against Votes fewer than half of Quorum, rounded down.
  • It has been open for voting for at least 48 hours, at least Quorum Citizens have Voted on it, and more than half of its Votes are FOR.

A DoV may be failed if any of the following are true:

  • It has been open for voting for 12 hours and 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 cannot be legally enacted.

When a DoV fails and there are no pending DoVs, Hiatus ends.

When a DoV is enacted, all other active DoVs are failed, and a new Dynasty begins with the Citizen who made the DoV as its High-Programmer. (That Citizen may pass this role to another Citizen at this point, if they wish.) The Hiatus continues until the new High-Programmer posts an Ascension Address to the BlogNomic weblog - this shall specify the High-Programmer’s chosen theme for the new Dynasty, and may optionally include a proclamation that any number of Dynastic Rules will be repealed, and/or that the words Citizen and High-Programmer will be replaced with theme-specific terms throughout the entire ruleset.

A DoV may not be started in the period between an enacted DoV and that DoV’s Ascension Address. When a DoV is failed, if it has a number of AGAINST Votes that exceed Quorum, the Citizen who posted it cannot make another DoV until after 120 hours (5 days) have passed since the time their DoV was failed.

A Declaration of Victory may not also be any other type of Official Post unless the rules concerning that type of Official Post explicitly state otherwise.

Fair Play

The following are BlogNomic’s rules of fair play. If any of the rules are found to have been broken, a proposal or CfJ may be made to remove the perpetrator from the game, and bar them from rejoining.

  • A single person should not control more than one Citizen within BlogNomic.
  • A Citizen should not “spam” the BlogNomic blog. What counts as spamming is subjective, but would typically include posting more than ten blog entries in a day, more than ten blog comments in a row, or posting a blog entry of more than 1000 words.
  • A Citizen should not deliberately exploit bugs or unexpected behaviours in the software running the game (ExpressionEngine, MediaWiki or the GNDT).
  • A Citizen should not edit their own blog comments once posted, nor those of any other Citizen.
  • A Citizen should not edit the "Entry Date" field of a blog post.
  • A Citizen should not make a DoV primarily to delay the game by putting it into Hiatus.
  • A Citizen should not do any action meant to make the game unplayable (for example, changing multiple keywords to the same word in an ascension address).

Dynastic Rules

ULTRAVIOLET

Clearance Levels

A Clearance Level is one of (from highest to lowest)

  • ULTRAVIOLET
  • VIOLET
  • INDIGO
  • BLUE
  • GREEN
  • YELLOW
  • ORANGE
  • RED
  • INFRARED

Each Clearance Level above INFRARED has a single-letter abbreviation, which is its first letter.

Each Citizen has a Clearance Level, which defaults to INFRARED.

All dynastic rules have a Clearance Level. The Clearance Level of a dynastic rule is the section of the Dynastic rules which it is in. If a Dynastic Rule is ever without a Clearance Level, its Clearance Level becomes INFRARED.

Information Clearance

For the purposes of any given dynastic Rule, any Citizen with a Clearance Level higher than the Clearance Level of that Rule is an Officer but not a Citizen.

If there is a way in which a pending Proposal could - if enacted - create, modify or repeal a Dynastic Rule whose Clearance Level is higher than the Clearance Level of the Citizen who submitted the Proposal, or Promote to or Demote from a Clearance Level that is higher than the Clearance Level of the Citizen who submitted the Proposal, then that Proposal is Treasonous.

For the purposes of any ULTRAVIOLET dynastic rule, ULTRAVIOLET Citizens are both Citizens and Officers.

ProDemote

To Promote is to raise the clearance level of a Citizen or a Rule, and to Demote is to lower the Clearance Level of a Citizen or a Rule.

  • Citizens of ULTRAVIOLET Clearance may Promote to any Clearance and may Demote from VIOLET or lower Clearance.
  • Citizens of VIOLET Clearance may Promote to INDIGO or lower Clearance and may Demote from INDIGO or lower Clearance.
  • Citizens of INDIGO Clearance may Promote to GREEN or lower Clearance and may Demote from BLUE or lower Clearance.
  • Citizens of BLUE Clearance may Promote to ORANGE or lower Clearance and may Demote from GREEN or lower Clearance.
  • Citizens of GREEN Clearance may Demote from RED Clearance.

In order to Promote or Demote, a Citizen must make a Story Post describing the Promotion or Demotion. If they are below INDIGO clearance, they must include a reason for the Promotion(s) and/or Demotion(s) in the Story Post. More than one Promotion and/or more than one Demotion may be described in a single Story Post.

The High-Programmer may Promote to any Clearance and may Demote from any Clearance.

UV Citizens

The High-Programmer may replace any references to ‘the High-Programmer’ in the dynastic rules, not including this rule, with, ‘any ULTRAVIOLET Officer’.

The High-Programmer may replace any references to ‘Citizens or Officers’ or references to ‘Officers or Citizens’ in the dynastic rules, not including this rule, with, ‘Citizens’, or with ‘Officers’.

The High-Programmer may replace any references to ‘ULTRAVIOLET Citizen’ with ‘ULTRAVIOLET Officer’.

Naming Scheme

Each Citizen has a Designation, which is tracked in the GNDT. Their Designation is their prime-name (a string of letters, the first capitalized, the rest lower-case) followed by a dash, their single-letter Clearance Level abbreviation followed by a dash (if their Clearance Level has no abbreviation, this is omitted), their home-sector (three capitalized letters) followed by a dash, and their Clone-Number. A Citizen’s prime-name defaults to their name, with the first letter capitalized, the rest lowercased, and all non-letters removed. A Citizen’s home-sector defaults to “BGN”. Any ULTRAVIOLET Officer may change a Citizen’s prime-name or home-sector at that Citizens request.

Only the Computer Knows All

If a GNDT value is to be changed secretly, then only the High-Programmer can make that change, and should attempt to do so without revealing why it is being done.

Clones

Each Citizen has a Clone-Number which defaults to 1. Whenever a rule or a game action causes a Citizen to die, that Citizen’s Clone-Number is incremented by 1.

For purposes of the ruleset, the verbs “to die”, “to be executed” and “to be terminated” are synonyms. The valid Clone-Numbers are hexadecimal numbers from 1 to F (i.e., fifteen values), plus zero and -1. Due to an undocumented feature that must have been introduced by a dangerous subversive, if a Citizen’s Clone-Number is F and there occurs any action or event that would cause the Citizen’s Clone-Number to be incremented by 1, that Citizen’s Clone-Number instead becomes -1.

Termination is performed in an efficient and hygienic manner. When a Citizen is terminated, if that Citizen has not previously been terminated during the current day, the terminator Citizen(s) (if any) gain two perversity points each. No Citizen can terminate himself except where a rule explicitly permits him to.

Hero of our Complex

Behind Every Great Citizen…

If there is an ULTRAVIOLET Officer who is not the High-Programmer, then the Citizen with the highest non-ULTRAVIOLET Clearance (if there is one) has Achieved Victory.

A Shining Example

If any Citizen has a negative Treason score, and that score is at least five less than all other Citizens Treason score, then that Citzen has Achieved Victory.

Proposal Perversity

When a proposal is enacted, its author gains 1 perversity point.

VIOLET

Treason

Each Citizen has a Treason score, tracked in the GNDT and starting at zero. A Citizen’s Treason may go negative, indicating that the Computer may have some temporary reason to foster the appearance of trust in that Citizen. Whenever a Citizen’s Clearance Level or Clone-Number changes, that Citizen’s Treason score is reset to zero.

If a blog post is Treasonous and no Citizen has made an Accusation in its comments, any Citizen may make an Accusation by posting a comment to that post with the word “TREASON” in capital letters, and increasing the Treason score of the blog post’s author by one.

If a Citizen’s Treason score is -6 or lower, they may increase their Clearance Level by one level. If a Citizen’s Treason score is 6 or more, any Citizen or Officer with a higher Clearance Level may Terminate them by posting a blog post announcing such an action.

Perversity

Each Citizen possesses zero or more Perversity Points (PP). The number of PP they have is tracked in the GNDT and defaults to 0.

Entertain or Die

When voting on a Proposal, a Citizen may include the ARROW (http://blognomic.com/images/vote/arrow.gif) icon in their EVC and before their Vote to indicate that they believe the flavor of that Proposal (either within the Flavor Text or in the wording of the Proposal) is entertaining and/or well-suited to the theme of the dynasty.

When a Proposal is Enacted or Failed, the author of that Proposal gains one Perversity Point if five of EVC’s (including the EVC of the High Programmer) include the ARROW icon before the Vote.

When commenting on a Story Post, a Citizen may include the ARROW (http://blognomic.com/images/vote/arrow.gif) icon in their post to indicate that they believe the flavor of that Story Post is entertaining and/or well-suited to the theme of the dynasty.

If a Story Post ever has at least five comments authored by different Citizens (including the High Programmer) that each contain the ARROW (arrow.gif) icon, then the author of that Story Post may add one perversity point to their total in the GNDT. They may only do this within one week of making the Story Post, and may only gain one Perversity Point per Story Post.

Location

The sector each citizen is in currently is tracked in the GNDT and defaults to their home sector. Whenever a citizen is terminated, set their sector to their home sector.

INDIGO

Reactor Leak

A Citizen may have a mutation. A Citizen has the type of mutation that the High-Programmer tells them they have. If the High-Programmer does not a tell a Citizen that they have a mutation, then that Citizen does not have a mutation. All mutations must be a type of mutation that has the same name as a subrule of this rule. A subrule of this rule only applies to a Citizen if that Citizen’s type of mutation has the same name as the subrule in question, unless stated otherwise in that subrule.

Acute Moral Compass

Whenever a ULTRAVIOLET Officer processes an instance of an action in the Code of Conduct, and in doing so changes a Citizen’s GNDT stats, he shall send that Citizen a PM that provides one word from the action they triggered, and the number of words preceding that word in the text of that action. The High-Programmer should not provide any Citizen with the same Word more than once in this manner.

We Are Not Alone

When a new Citizen joins the game, or when an idle Citizen who has not previously participated in this Dynasty reactivates, the High-Programmer may (within 48 hours) determine whether this Citizen is a member of one or more groups, enumerated in subrules to this rule, in a manner of his choosing. Whenever the High-Programmer determines that a Citizen is a member of a group, the High-Programmer shall notify that Citizen via PM but shall not alert that Citizen of the identity of any other members of that group. Subrules of subrules of this rule describe Missions for the groups to which they are a subrule.

Sequel Police

The Secret Police

A Nervous Tic

A member of The Secret Police can investigate a Citizen with a lower Clearance and a clone-number of at least 3. The investigator shall inform the High-Programmer privately the designation of the Citizen he is investigating, and the High-Programmer shall reply with the name of a group that the investigated Citizen is a member of, or any group if the Citizen is not a member of a group. The investigated Citizen secretly receives -1 TP.

The third time that a member of The Secret Police investigates someone since most recently joining that group, he is stripped of his membership in The Secret Police.

Remulak, A Small Town In France

The Alien Subversives

We, The People

A member of The Alien Subversives can contact the High-Programmer asking him to remove an entry from the Code of Conduct by citing its designation and the designations of three members of The Alien Subversives who have triggered it. If the information is correct, the High-Programmer must remove it from the Code of Conduct and should not reintroduce it or a substantially similar entry. If the information is not correct, the Citizen secretly receives 3 Treason Points.

Do Or Do Not; There Is No Try

The Rebel Usurpers

Infiltration at All Levels

If a Citizen posts, in a story post whose title begins with “Infiltration”, the Designations of exactly four Citizens, each of them being members of The Rebel Usurpers having a different clearance level; and the High-Programmer confirms this to be the case in a comment, then:

1. Every member of The Rebel Usurpers is awarded -4 Treason.

2. Every member of The Rebel Usurpers is stripped of their membership in that group, and the High-Programmer shall put them into one or more other groups.

3. The High-Programmers shall select one or more other Citizens and put them into The Rebel Usurpers.

The Christian League Had The Seedy Underbelly Shut Down

The Criminal Underground

Political Assassination

A member of The Criminal Underground can terminate any Citizen of equal or lower Clearance and with at least 0 Treason Points by posting this in a Story Post. The member of The Criminal Underground has his membership in that group revoked and receives 3 Treason Points.

BLUE

The Mission

The following list is the Mission Requirements. If no additions have been made to this list within the past 10 days, any ULTRAVIOLET Officer may add a requirement to this rule and make a Story Post announcing it, but the requirement is not added unless the High-Programmer comments on the announcement Story Post with an ARROW.

  • An ULTRAVIOLET Officer has a clone-number of greater than 2.
  • No Citizen is in a Sector with no other Citizens, unless that Citizen is also the only Citizen of their Clearance level.
  • There is a Rule of each clearance level.

Debriefing

If all Mission Requirements have been met, then all Citizens with clone numbers less than 7 are Surviving Troubleshooters. If there are any Surviving Troubleshooters, then being Terminated sets a Citizen’s Clone Number to 7 instead of incrementing it by one. If all Mission Requirements have been met, then no Citizen who is not a Surviving Troubleshooter may achieve victory.

GREEN

Code of Conduct

There exists a Code of Conduct document - initially empty - which lists any number of possible game actions, each of which has a trigger condition, a six-letter designation and an attached Treason or PP modifier, which may be positive or negative. The Code of Conduct document is maintained by the High-Programmer at a URL of his choice anywhere on the Internet. Any Officer may privately request the URL of the Code of Conduct document; the High-Programmer should privately respond to their request with the URL.

The High-Programmer may add a new action to the Code of Conduct document at any time, but may not remove or alter an existing action.

If a Citizen performs the trigger condition of an action listed on the Code of Conduct document, and that instance of the action has not yet been Processed, then any Officer may - within 24 hours of the action - Process the action by modifying the triggering Citizen's Treason or PP by the proscribed amount, and citing the designation of the action (in either a blog comment, a blog post or a GNDT comment).

The Underground

As a daily action, any Citizen may add 1 to their Treason to change up to two letters in their sector. Their new sector must hold a legal value.

Forms

A Form is a special type of Story Post. A form must match one of the formats set out in the wiki page entitled List_of_forms. Forms are similar to Proposals in that they may be passed or failed, but deciding whether or not a Form passes does not follow the same rules as Proposals.

The Form-at

A Form entry in the wiki page entitled “List of forms” consists of five parts. The first part is the title, which consists of no more than 4 capitalized letters and any number of digits. The title is used to identify the Form uniquely, and therefore no two Forms may have the same title. The title is a first level heading in the wiki page.

The second part is the description, which contains a description of the effects of passing that Form. The description should be written like a rule in that it describes exactly what happens when the Form passes, any necessary time frames involved, and in what order the listed actions should be taken. The description should NOT describe how a Form is passed. The description is under a second level heading of the wiki page.

The third part is the Form’s text. The Form’s text consists of labels with blanks (denoted by a series of underscores) next to them, with optional instructional text. A reasonable number of unnecessary labels and blanks are encouraged. The Form’s text is under a second heading of the wiki page.

The fourth part is the list of required signatories. This is a list of Citizens who must sign the form for it to be passed. There must be at least a required primary signatory, who is the Citizen who submits a Form to the blog. The list of required signatories may include specific Citizens, Citizens of a minimum or maximum Clearance, and/or any other criteria desired, including none. The list of required signatories is under a second heading of the wiki page.

The fifth part is an optional requirement of passage. This is a description of any other rules involved in the passage of a Form. It may include rules on who may pass the Form, when the Form may be passed, if any signatures are optional under certain conditions, etc. If included, the requirement of passage is under a second heading of the wiki page.

Form-ula for Passage

In order to use a Form, the Citizen wishing to use the form creates a Story Post with only the title of the Form and the Form’s text in its body. When placing the Form’s Text in the body of the Story Post, the Citizen must replace all of the blanks in the text with information as requested by the associated label. In order to post the Form, the Citizen must satisfy any requirements set out in the list of required signatories regarding the primary signatory. If he does, he automatically signs the Form when he posts it. Anyone who can be a signatory of a Form may sign it by posting a comment with an arrow icon.

Once all required signatures have been collected, and the requirements set out in the requirements of passage have been satisfied, anyone explicitly permitted by the Form may pass the form by carrying out the description of the form. If no Citizen is explicitly permitted, then the primary signatory of the Form may pass it and carry out its description.

If any Citizen notices any error anywhere in the body of a Form post, he may post an against voting icon along with a description of the problem. If the concern is valid, the High-Programmer may fail the Form immediately, add 1 Treason point to the Citizen who posted the Form, and subtract 1 Treason point from the Citizen pointing out the error. Unless otherwise specified in the requirements of passage section of the Form, any Form which has not been passed in 48 hours may be failed by any Citizen. To fail a Form, the Citizen who wishes to fail the Form must post a comment to that effect. A failed form may never be passed, and a form which has been passed may not be passed again or failed, unless specified by the Form.

YELLOW

Popsy Pervy

At any time, a Citizen may spend Perversity Points in order to perform an action enumerated in the subrules to this rule once for each time the cost is paid. That Citizen must have Perversity Points greater than or equal to the cost of the action prior to paying the cost. Each subrule must list the cost of the action and the action’s effect.

Influence through the outfluence door

Cost: 1 Perversity Point. Action: Increase or decrease the Treason Points of any Citizen by 1.

Professional killing is a growth industry

Cost: 1 + the absolute value of the numeric difference in clearance levels between the Citizen and the victim. Action: The Citizen may terminate any other Citizen (referred to in this rule as the victim) as long as the victim’s Treason Points are greater than or equal to 6. The Citizen performing the termination gains no PP for it.

Hook and ladder

Cost: 2 + the numeric value of the resulting clearance (with INFARED being 0, RED being 1, etc.) Action: Raise or lower the clearance of a Citizen by one level, restore the number of Treason points the Citizen had prior to the clearance level change, and then add an additional Treason point for the Citizen’s inappropriate cutting of red tape.

Please alert the police in advance of any crimes

Citizens shall not attend any group meetings which have not been scheduled. Citizens can schedule group meetings by filling out form B3DD8Q, or form IU9MN if the purpose of the meeting is treasonous.

You are hereby assigned to kill me

The High-Programmer shall, as soon as possible after this rule is enacted, assign every Citizen to one or more groups. Then this rule is repealed.

The Mantis Mantra

The mantra of all Citizens is as follows:

Great Wall of Prophecy, reveal to us Friend Computer’s will that we will blindly obey.
Free us from thought and responsibility.
We shall read things off you.
Then do them.
Your words guide us.
We’re dumb.

ORANGE

Travel Permits

Each Officer may change their sector to match any Citizen’s sector as a weekly action.

An ULTRAVIOLET Officer SHOULD Promote or Demote this rule at least once each week.

The Locked Room

A Citizen in Sector BLN is considered to be in Room 23-J if and only if that Citizen has a Briefing Room Key. The following Citizens and Officers have Briefing Room Keys: lilomar, Bucky, lilomar, Put, flurie, Qwazukee, glopso, coppro, spikebrennan, Rodney, Galdyn.

Taboo Topics

A non-Proposal, non-CfJ blog post is Treasonous if it contains the words “paranoia”, “paranoid” or “communist”, the phrases “secret society” or “mutant power”, or any mention of a Clearance above Ultraviolet. It is also treasonous to mention or discuss the contents of rules 3.5.1 or 3.5.2.

RED

No Thinking Allowed

No Citizen shall read from the Great Wall of Prophecy. Any Citizen caught doing so may be summarily terminated by any Officer.

INFRARED

Slander

Slander is disharmonious, which leads to unhappiness. Accordingly, any Citizen who posts a blog post that constitutes slander of an Officer will have his Treason score increased by one. A statement is slanderous if (1) any Officer with a Clearance Level of VIOLET or higher says so in a comment to that blog post, or (2) the statement satisfies such requirements as are issued in a blog post from time to time by an Officer with a Clearance Level of GREEN or higher that have not been superseded by a subsequent blog post by an Offier with a higher Clearance Level, or with ULTRAVIOLET Clearance.

Thank you for your loyalty, Citizen!

Within 24 hours of the Enactment of a proposal they authored, a Citizen may raise their Clearance by one level.

Glossary

Keywords

A keyword defined by a rule supersedes the normal English usage of the word. A keyword defined in this glossary supersedes that defined by a rule. (eg. A rule specifying "bananas are blue" cannot be overruled by posting a dictionary definition or a photo of a banana, and a rule specifying "every day is Sunday" will be overruled by the glossary entry below.)

Can
"is able to"
Comment
A blog comment published to the BlogNomic weblog at blognomic.com
Core Proposal

A Proposal whose changes are limited to the creation, deletion, and/or amendment of core rules and/or the glossary, and/or renaming, banning, and/or the granting or removing of admin status from one or more Citizens.

Daily Action
If a game action is a Daily Action, each Citizen able to perform it may take that action once each day, but not more than once every six hours.
Day
References to a “day” as an entity rather than as a duration (e.g. “Sunday”, “The day after performing this action”, or “August 2nd”), unless otherwise stated, refer to a day beginning at and including 00:00:00 GMT, ending when the next day begins. It can never be 2 different days at the same instant.
Dice
References to "YDICEX" refer to Y X-sided dice, rolled within the GNDT. To roll dice, post DICEX in the comments field of the GNDT, replacing X with the number of sides on the die you wish to roll.
Dynastic Proposal
A Proposal whose only changes are the creation, deletion, and/or amendment of dynastic rules and/or gamestate defined by dynastic rules.
Effective Vote Comment (EVC)
A Citizen's Effective Vote Comment with respect to a given Proposal means that Citizen’s Comment to that Proposal (if any) that contains that Citizen’s Vote on the Proposal that is given effect in accordance with Rule 1.4 when the Proposal is Resolved, not including explicit Votes of abstention..
Flavour Text
When posting a blog entry, a Citizen may use the “Commentary or flavour text” field of the blog publishing form to add their own comments or description of their post. For the purposes of all other rules, such text is not considered to be part of the post.
Gamestate
Any information which the Ruleset regulates the alteration of.
IRC Channel
The Blognomic IRC channel is located at #nomic on the slashnet network (irc.slashnet.org).
May
"is permitted to"
Post
A blog post published to the BlogNomic weblog at blognomic.com
Quorum
Quorum of a subset of Citizens is half the number of Citizens in that subset, rounded down, plus one. If the word Quorum is used without qualifying which subset of Citizens it is referring to, it is referring to a Quorum of all Citizens.
Resolve/Resolution
If used in a context of Proposals, Call for Judgements or Declarations of Victory, the world “Resolve” means to perform the act, as an Admin, of enacting or failing a Proposal, a Call for Judgement or a Declaration of Victory. The world “Resolution” means then the act of doing so. If used in another context, the meaning of both “Resolve” and “Resolution” is the standard English meaning of these words.
Shall
"is required to"
Should
"is recommended that"
Story Post
A Story Post is an Official Post that is not a member of any specific category of Official Posts mentioned or defined in a Core Rule (excluding Official Post).
Subject
The "subject" of a blog entry is the part of the Title of an entry which is after the first colon. If the Title does not contain a colon, then the whole Title is the subject. Any entry whose subject is "" (i.e. an empty string) is not valid.
Votable Matter
The word “Votable Matter”, means a Proposal, a CFJ or a DoV.
Vote
The word “Vote”, used as a noun, means a Vote that is cast in accordance with Rule 1.4 “Voting”. The word “Vote”, used as a verb, means the act of casting such a Vote.
Voting Icons
For use in voting, a check box http://blognomic.com/images/vote/for.gif shall represent a Vote FOR, an X http://blognomic.com/images/vote/against.gif shall represent a Vote AGAINST, an IMP http://blognomic.com/images/vote/imperial.gif shall represent a Vote of DEFERENTIAL, and an Imperial Seal http://blognomic.com/images/vote/seal.gif shall represent the Imperial Veto.
Week
References to a week as an entity rather than as a duration (e.g. “At the beginning of each week”, or “already happened this week”), unless otherwise stated, refer to a period of time between the beginning of a Monday and the end of the following Sunday.
Weekly Action
If a game action is a Weekly Action, each Citizen able to perform it may take that action once each week, but not more than once every twenty-four hours.
Wiki
The BlogNomic Wiki at http://blognomic.com/wiki/index.php?title=Main_Page

Clarifications

Numbers and Variables

  • Unless otherwise specified, game variables defined to hold numeric values can hold only non-negative integers, and any action that would set those values below zero instead sets them to zero. Any situation which would require a roll of DiceX when X is zero or lower always yields a value of 0 unless stated otherwise.
  • All numbers, unless stated otherwise by a rule, are in base ten.
  • Unless otherwise specified, when “X” is a number, to spend X of a numeric value “V” means to subtract X from V (i.e. replace V with V-X); to gain X of a numeric value “V” means to add X to V; and to transfer X of a numeric value “V” from A to B means to subtract X from A's V and add the amount A's V was reduced by to B's V. Unless otherwise specified, a rule that allows Citizens to transfer a numeric value only allows them to transfer that value from themselves to another Citizen (of their choice unless otherwise stated).
  • A Citizen who has a choice in whether to take an action defined by a dynastic rule may not take that action if both of the following conditions are true: a) the action's effects are limited to changing values tracked in the GNDT and/or similar gamestate-tracking entities (such as a wiki page), and b) the action would change one of those values to an illegal value.
  • If a rule implies that the result of a division should be an integer (for instance, by attempting to store that result in, or add it to, a gamestate variable that can only hold integers), the result of the division is instead the result rounded towards 0.

Rules and Proposals

  • If a new rule is created by a proposal and its location is not noted in that proposal, that new rule is to be placed in the Dynastic Rules.
  • Where a Proposal would amend the effects of Proposal Enactment, this does not apply to its own enactment unless explicitly stated (eg. a proposal proposing that enacted proposals earn their author a banana when enacted would not earn a banana for its own author, when enacted).
  • Rules which trigger upon the Enactment or Failure of a Proposal are the responsibility of the Admin who Enacts or Fails it.

Time

  • For the purpose of all rules, time in Blognomic is in GMT.
  • All references to time must be either specific or defined within the ruleset to be considered achievable in the gamestate. Abstract concepts of time (e.g. "dinnertime", "twilight") cannot be achieved until they fulfil one of these criteria.
  • Where the month, day and/or year of a calendar date are ambiguous (eg. "04/10/09"), it shall be assumed that the date is in a day/month/year format.

Spelling

  • Superficial differences between the spelling of geographic versions of English, e.g, British English, American English and Australian English shall be construed as irrelevant for the purposes of play.

Names

  • Within the ruleset, a word only refers to the name of a Citizen if it is explicitly stated that it refers to a Citizen's name.