On 04/14/2010 02:56 PM, Charles Reiss wrote:
If - e has not already done so, or - if at least two other players done so so e last did so, or - three days have passed since e last did so, a player may publish a Fragment. A Fragment SHOULD be a short"CAN publish" to trigger R2125(c)'s document clause and add self-ratification of the list of fragments in the Granulator's report.
The CAN was meant to be there, but would not make the report self-modifying. I'll make that addition anyway though.
(possibly as small as a sentence) body of text intended to become a portion of a Rule. A new Fragment SHOULD bear some relation to existing Fragments. The Granulator is an office, and eir weekly report includes a listing of all Fragments.and their authors
Thanks.
- In the same message in which it is submitted, the author lists at least 4 Fragments, each of which would have their text added to the Ruleset were the Proposal to take effect. These Fragments make up the Proposal's Inode."initial"
Thanks.
A player CAN, without objection from the Proposal's author, add a"(or the Proposal's author CAN by announcement)"
Thanks.
When a Defragmentation Proposal is adopted, the author of the Proposal is awarded a Leadership Token. Additionally, each player who authored one or more Fragments in the Proposal's Inode is awarded Leadership Tokens equal to one third the number of such Fragments e authored, rounded up. Lastly, all Fragments cease to be Fragments.Please specify whether this occurs before or after the proposal takes effect.
Good idea.
If a Fragment that is a member of a Defragmentation Proposal's Inode ceases to be a Fragment, it is still treated as one for the purpose of rules relating to that Proposal. For this reason, it is RECOMMENDED that the Granulator not restart the numbering of Fragments."distinct from any ID number previously assigned to an entity of that type" in R2161(b) already prohibits that.
Good catch, I thought it only applied to existing entities of that type. -coppro
