spoon-business: Revision of Haiku and a new Proposal

["Jonathan Van Matre" <JVanMatre@xxxxxxxx>]

First, a revision.  

In the Haiku Bonus proposal, replace

{{
A player who submits a proposal in haiku form earns 10 Score points for submitting the proposal, regardless of whether the proposal is adopted or rejected.  If the player subsequently revises the proposal, it must remain in haiku form, or else the player will forfeit the 10 Score points previously awarded.
}}

with 

{{
A player who submits a proposal in haiku form earns 10 Score points if the proposal is adopted, in addition to any points received as a normal consequence of the adoption of a proposal.
}}

Next, here's a new proposal to cut down on the need for self-modifying "if this rule exists" stuff in proposals:

__Dependent Proposals__

{{
A proposal may be specified as being "Dependent" on another proposal or rule.  This is specified by including the phrase "Dependent on [object type] [serial number]", where object type is either "Proposal" or "Rule".  

If the serial number is given without the revision number, the proposal is dependent on the most current revision of that object at the moment the proposal is enacted.  If a revision number is specified, the proposal is dependent on that specific revision of the object being active.

I. Dependent on Other Proposals

If a proposal is dependent on another proposal, and the proposal it is dependent on passes, then the dependent proposal is enacted like a normal proposal. However, if the proposal it is dependent on does not pass, the dependent proposal becomes Inactive and is not enacted.

II.  Dependent on Rules

If a proposal is dependent on a rule, and the rule it is dependent on is  active at the time the dependent proposal is enacted, then the dependent proposal is enacted like a normal proposal. However, if the rule it is dependent on is not active, the dependent proposal becomes Inactive and is not enacted.

III.  Multiple Dependencies

A proposal may have multiple dependencies.  If a proposal has multiple dependencies, and any one of those dependencies will inactivate the proposal, the proposal is inactivated regardless of the status of its other dependencies.  [[i.e. if one is broken, the whole thing breaks]]

IV.  Failed Dependency Clause

Dependent Proposals may specify a Failed Dependency Clause.  The Failed Dependency Clause is a portion of the proposal that is only activated when the proposal has been inactivated by one or more dependencies.  Notwithstanding the "Inactive" status of the proposal, and if and only if the Dependent Proposal has been inactivated by a dependency, the Failed Dependency Clause is treated as an active proposal and adopted instead of the rest of the inactivated Dependent Proposal.