On Jan 17, 2017, at 1:06 AM, Aris Merchant <thoughtsoflifeandligh...@gmail.com> wrote:
> {Reenact rule 2166, Assets (Power = 2), with the folowing text:
> An asset is an entity defined as such by a rule (hereafter its backing
> document), and existing solely because its backing document defines its
> existence.
>
> Each asset has exactly one owner. If an asset would otherwise
> lack an owner, it is owned by the Lost and Found Department.
Reintroducing this (and making shinies a kind of asset) closes something I
half-considered exploiting: right now, shinies held by Organizations poof off
into the ether if the Organization ceases to exist.
This also streamlines (well, almost entirely eliminates) wills and estates.
> If an asset's backing document restricts its ownership to a class
> of entities, then that asset CANNOT be gained by or transferred
> to an entity outside that class, and is destroyed if it is owned
> by an entity outside that class (except for the Lost and Found
> Department, in which case any player CAN transfer or destroy it
> without objection).
>
> The recordkeepor of a class of assets is the entity (if any)
> defined as such by, and bound by, its backing document. That
> entity's report includes a list of all instances of that class
> and their owners. This portion of that entity's report is
> self-ratifying.
>
> An asset generally CAN be destroyed by its owner by
> announcement, and an asset owned by the Lost and Found
> Department generally CAN be destroyed by its recordkeepor by
> announcement, subject to modification by its backing document.
> To "lose" an asset is to have it destroyed from one's
> possession; to "revoke" an asset from an entity is to destroy it
> from that entity's possession.
>
> An asset generally CAN be transferred (syn. payed) by its owner to another
> entity by announcement, subject to modification by its backing
> document. A fixed asset is one defined as such by its backing
> document, and CANNOT be transferred; any other asset is liquid.
>
> A currency is a class of asset defined as such by its backing
> document. Instances of a currency with the same owner are
> fungible.
It feels weird not to reuse the Switches framework for this. I realize you’re
reinstating an existing rule, but is it worth refactoring this to avoid
reintroducing another kind of recordable state?
> Assets are always public.
>
> Change the rule "Economics" to read in full:
>
> Shinies (sg. shiny) are a liquid currency, and the official currency of
> Agora.
> They may be owned by Agora, any player, or any organization. The Secretary is
> the recordkeepor for Shinies.
>
> The Secretary CAN cause Agora to pay any player or organization by
> announcement if doing so is specified by a rule.
After the discussion on my first attempt at a payday notice, I’d strongly
prefer that this clause be rephrased, or removed in favour of “CAN and SHALL”
enabling clauses on the Secretary’s responsibilities.
> The balance of an entity is the number of Shinies that entity possesses. If a
> rule or proposal attempts to increase or the balance of an entity without
> specifying a source or destination, then the Shinies are created or
> destroyed.
>
> Amend Rule 2459, Organizations, by adding as a paragraph at the end:
> A member of an Organization can perform any action the rules authorize that
> Organization to perform, if the Organization's charter states that doing so
> is Appropriate.}
> See the "Services rendered" thread for justification and explanation.
Overall, I like it.
-o
signature.asc
Description: Message signed with OpenPGP
