DIS: Re: BUS: Call for Judgement
I additionally bar ais523 from judgement of this case. On Thu, Jun 8, 2017 at 1:45 PM, V.J Rada wrote: > Call for Judgement > The Tailor's recent statement in the preamble of his June 6 report that "the > well-known "disputed" mark in reports has... no legal effect." was > legally correct > Evidence > Rule 1551, Ratification, reads in relevant part > [When a public document is ratified, rules to the contrary > notwithstanding, the gamestate is modified to what it would be if, at the > time the ratified document was published, the gamestate had been > minimally modified to make the ratified document as true and accurate as > possible.] > The preamble of the Tailor's report on June 6 reads > [Before the main body of the report, a summary of what I believe to have > > happened with respect to Alexis: eir own White Ribbon was never legally > given, and nor was the White Ribbon e gave me; but I forgot at the time > of the last report that my own White Ribbon holding was disputed, and > thus marked only Alexis' as such. The report itself was not CoEd, and > thus self-ratified a week later. As far as I can tell, what therefore > happened was that both me and Alexis gained a White Ribbon at the time > of ratification (being the minimum change to the gamestate required to > give all the Ribbon Ownership switches the value the report stated they > held; note that the statement that Alexis' switch had a disputed value > is not in its own right self-ratifying, although being a true > statement, it wouldn't matter if it were; ratifying a true statement > has no effect). > > This seems something like a bug that should perhaps be fixed, as > reporting on disputes is currently impossible to do "correctly" without > CoEing your own report and resolving the CoE with a reference to the > CFJ in question, something that I hadn't realised would be required. > The well-known "disputed" mark in reports, has, as far as I can tell, > > no legal effect. > > > If someone believes that I've misinterpreted the law here, I'd > recommend calling a CFJ. Alternatively, if someone feels that I've > interpreted it correctly but that the situation is nonetheless unfair, > the correct solution probably involves a proposal. (Perhaps we should > create some sort of rules-wide equity system. I know G. would probably > be a fan of that.)] > > Argument > I disagree with the statement that the disputed mark has no legal effect, > and therefore, as suggested by the Tailor himself, call a CFJ. Game > practice clearly shows (as the Tailor admits by calling it "well-known") > that marking an aspect of a report "disputed" is often used; I believe that > the intent of this use is to mark a fact in a report as possibly incorrect, > and therefore its very inclusion in the report should not lead to its > finality. I believe that the best judgement would be that the use of the > disputed mark implies that the previously listed words in the report are > arguably factually incorrect, and thus ratification of the report would > continue that possibility instead of precluding it. Common sense affirms > this course of action. As the Tailor notes, it seems silly to make it > impossible for the very writer of a report to cast aspersions its contents > except by CoE. In addition, the possible unfairness of this factual > situation itself leads to this conclusion. A person who wished to make a > CoE may have stopped due to the presence of the disputed mark, only to be > caught off card by this new legal opinion. > > Alternatively, "internally inconsistent" reports or statements cannot be > ratified. Stating a fact in the same way as other facts and then > contradicting that fact with the disputed mark is internally inconsistent. > > In either case, this case should be judged FALSE, and marking a fact > "Disputed" in a ratified statement should be judged to have legal effect. > >
DIS: Re: BUS: Re: OFF: [ADoP] Metareport
On Wed, Jun 7, 2017 at 00:06 Aris Merchant < thoughtsoflifeandligh...@gmail.com> wrote: > On Mon, Jun 5, 2017 at 10:43 AM, Quazie wrote: > > > > > > Office M[1] Report Last Published Late[2] > > --- > > ADoP[3] Offices 2017-06-05 > > Herald Y Patent titles 2017-05-20 > > Promotor Proposal pool 2017-05-21 !! > > Referee Rule violations 2017-06-02 > > Registrar Players, Fora 2017-06-05 > > Registrar Y Player history 2017-05-31 > > Reportor The Agoran Newspaper2017-05-24 ! > > RulekeeporShort Logical Ruleset 2017-05-28 ! > > Rulekeepor Y Full Logical Ruleset2017-05-28 > > Secretary OLEaB[4]2017-06-02 > > Secretary Y Charters2017-06-02 > > SuperintendentAgencies (incremental) 2017-06-05 > > Superintendent Y Agencies (Full) 2017-05-18 > > Surveyor Estates 2017-06-02 > > Tailor Y Ribbons 2017-05-18 > > --- > > [1] Monthly > > [2] ! = 1 period missed. !! = 2 periods missed. !!! = 3+ periods missed. > > CoE: The Promoter's report isn't late. I release it in the new week > every week, so this week's one isn't late. In addition, I released the > report last week. > > -Aris Hmm - I have to validate the report rules to ensure that's the case - I do see you publish the pool with each distribution, it just doesn't seem like it's own report - will do a quick read and then accept the CoE > >
Re: DIS: Re: BUS: Registration
Well I've been lurking around for a while reading things but when I first considered joining it seemed pretty dead with some kind of dictatorship going on? But now it seems flourishing and so I thought it was the optimal time to join here. On Thu, Jun 8, 2017 at 12:44 AM, Quazie wrote: > Welcome! > > How did you find us? What brings you here? > > On Wed, Jun 7, 2017 at 03:09 ben keil wrote: > >> Hello, I, V.J. Rada aka vijar...@gmail.com register for this game. >> >
DIS: Re: BUS: Registration
Welcome! How did you find us? What brings you here? On Wed, Jun 7, 2017 at 03:09 ben keil wrote: > Hello, I, V.J. Rada aka vijar...@gmail.com register for this game. >
Re: DIS: Draft: Assets v6
Two things: a) Maybe adding a generic clause to specify rule amendments don’t destroy specified assets would be helpful. It could read as: Amendments to a backing document SHALL not be construed to destroy or change ownership of an asset, unless explicitly meant and written to do so. b) Also, it could be interesting if a person or organization could issue a backing document by announcement. Publius Scribonius Scholasticus p.scribonius.scholasti...@gmail.com > On Jun 7, 2017, at 3:17 AM, Aris Merchant > wrote: > > Remember how that last draft was supposed to be final? Well, I > recalled some promises I made and found some more boilerplate to > reduce. Here's my 6th draft of Assets. Changes include indestructible > assets, a better disambiguating clause, and a host of small fixes and > tweaks. Hopefully this will be done someday, but I'd like it to be > something I'm proud of when I release it, and it's much harder to > modify it later. > > -Aris > > --- > > Title: Assets v6 > Adoption index: 3.0 > Author: Aris > Co-authors: o, nichdel > > Reenact rule 2166, Assets (Power = 2), with the following 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 Agora. 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 Agora, in which case any player > CAN transfer or destroy it without objection). The restrictions in the > previous sentence are subject to modification by its backing document. > > Unless modified by an asset's backing document, ownership of an asset is > restricted to Agora, persons, and organizations. > > An organization's charter CAN specify whether or not that organization is > willing receive assets or a class of assets. Generally, an organization > CANNOT > be given assets its charter states that it is unwilling to receive. The > previous provisions of this paragraph do not apply to an asset if the > organization is required to provide that asset in order to continue existing. > > 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, subject to modification by its backing document. An > indestructible asset is one defined as such by it backing document, and > CANNOT > be destroyed except by a rule specifically addressing the destruction of > indestructible assets or that asset in particular; any other asset is > destructible. In circumstances where another asset would be > destroyed, an indestructible asset is generally transferred to Agora, subject > to modification by its backing document and the intervention of other rules. > > 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, given) 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. > > The "x balance of an entity", where x is a currency, is the number of x that > entity possesses. If a rule, proposal, or other competent authority attempts > to increase or decrease the balance of an entity without specifying a source > or destination, then the currency is created or destroyed. > > Where it resolves ambiguity, the asset or currency being referred to is the > currency designated as "Agora's official currency", if there is one. > > Assets are always public. [To provide for private contract based assets > later] > > Change the power of Rule 2166 to 3.0. > > Change the rule "Economics" to read in full: > > Shinies (sg. shiny) are an indestructible 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. > > Amend Rule 2459, Organizations, by adding as a paragraph at the end: > > A member of an Organization CAN perform an
DIS: Draft: Regulations v2
This isn't quite ready yet, but I thought I'd open it up for more public comment. Changes include filing in the procedure for creating or amending regulations, providing for alternate procedures, and various harmonization efforts. The biggest of the harmonization efforts was changing tournaments to operate on actual regulations. In the interest of testing this out, I'd like to pass the proposal in time for the birthday tournament, which means it needs to be ready by the 18th. Comments appreciated. -Aris --- Title: Regulations v2 Adoption index: 3.1 Author: Aris Co-authors: o, nichdel Change the title of Rule 2125, "Regulation Regulations", to "Regulated Actions". Amend Rules 2125 and 1023 by changing all instances of the word "regulated" to "restricted", and all instances of the word "unregulated" to "unrestricted". Amend Rule 2143, "Official Reports and Duties," by changing all instances of the word "regulations" to "restrictions". Create a new power 3.1 rule entitled "Regulations", with the flowing text: A Regulation is an instrument defined as such by this rule. A regulation allows an officer (known as the Promulgator) to exercise rule defined powers. A regulation is in effect continuously from the time of its creation to the time of either its revocation or the repeal of the rule that allowed for its creation. When recommending a regulation, its Promulgator must specify by number the rule(s) upon which it is based (the parent rules), the list of which becomes an integral part of the regulation. The list of rules can generally be modified by the Promulgator according to the procedure for text changes. A regulation must be authorized by at least one rule in order for it to exist. A regulation has effect on the gamestate insofar as the rule or rules that authorized it permit it to have effect, and a regulation generally inherits the power of its least powerful parent rule, unless its Promulgator defines a lower power. Regulations shall generally be adjudicated as if they were a part of their (least powerful) parent rule, except that their parent rule(s) always supersedes them. If reasonably possible, a regulation should be interpreted so as to defer to other rules. The procedure for resolving conflict between regulations is the same as it is for rules. Regulations are generally issued according to the following procedures, and they can be repealed by the announcement of their Promulgator. Alternate procedures may be used if provided for by all of the regulations's parent rules. If one parent rule specifies procedures that are more stringent than those that the other(s) specifies, those apply. Creating, modifying, revoking, or allowing for a regulation is secured at power 1. A regulation (or set of regulations) may generally be enacted or modified without 2 objections, or with Agoran consent. A notice pursuant to the previous sentence is known as a "recommendation", and the regulation(s) are said to be "recommended" to Agora. Create a new power 1 rule, entitled "The Regkeepor", with the following text: The Regkeepor is an office, responsible for the maintenance of the Regulations. The Regulations are contained in the Regkeepor's weekly report, know as the Agora Nomic Code of Regulations (ACORN). E MAY publish multiple versions or editions of the ACORN. The ACORN is divided into titles, assigned by the Regkeepor, which are each given an integer. Generally, each office with the power to create regulations SHOULD be assigned the next successive natural number. Title 0 of the ACORN is reserved for use by the Regkeepor, and nothing in that title need be a regulation. Non-regulations printed in the ACORN have no binding effect, and SHALL clearly be marked by the Regkeepor. Each regulation SHALL be assigned an ID number by the Regkeepor, consisting of a string of the characters [0-9] and separator characters. The Regkeepor SHOULD establish some way of keeping track of the version of a regulations. The Regkeepor MAY also, at eir discretion, create ways of marking special types of Regulation (even in violation of the previous restrictions of this paragraph), mark sections or titles as reserved for future use, and make such other discussions of arrangement, annotation, and marking as are necessary and proper in the execution of eir duties. The Regkeepor SHOULD remember that the purpose of the ACORN is to make the regulations easily readable, and e SHALL not act in a manner intended to deceive others in eir official capacity. Make Aris the Regkeepor. Amend Rule 2464, "Tournaments", to read in full: A Tournament is a sub-game of Agora specifically sanctioned to be initiated as a tournament by the Rules. If a winner of a tournament is determined within 4 weeks of its initiation, that person or persons win the game, otherw
DIS: My Open CFJs
I'd like to briefly apologize for my tardiness on my open CFJs. As far as I can tell, I currently have 3 CFJs (3496, 3506, 3512) open, all of which are severely overdue. I intend to get all of these judged by the end of tomorrow. Sorry again for any inconvenience, Sprocklem
DIS: Draft: Assets v6
Remember how that last draft was supposed to be final? Well, I recalled some promises I made and found some more boilerplate to reduce. Here's my 6th draft of Assets. Changes include indestructible assets, a better disambiguating clause, and a host of small fixes and tweaks. Hopefully this will be done someday, but I'd like it to be something I'm proud of when I release it, and it's much harder to modify it later. -Aris --- Title: Assets v6 Adoption index: 3.0 Author: Aris Co-authors: o, nichdel Reenact rule 2166, Assets (Power = 2), with the following 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 Agora. 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 Agora, in which case any player CAN transfer or destroy it without objection). The restrictions in the previous sentence are subject to modification by its backing document. Unless modified by an asset's backing document, ownership of an asset is restricted to Agora, persons, and organizations. An organization's charter CAN specify whether or not that organization is willing receive assets or a class of assets. Generally, an organization CANNOT be given assets its charter states that it is unwilling to receive. The previous provisions of this paragraph do not apply to an asset if the organization is required to provide that asset in order to continue existing. 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, subject to modification by its backing document. An indestructible asset is one defined as such by it backing document, and CANNOT be destroyed except by a rule specifically addressing the destruction of indestructible assets or that asset in particular; any other asset is destructible. In circumstances where another asset would be destroyed, an indestructible asset is generally transferred to Agora, subject to modification by its backing document and the intervention of other rules. 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, given) 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. The "x balance of an entity", where x is a currency, is the number of x that entity possesses. If a rule, proposal, or other competent authority attempts to increase or decrease the balance of an entity without specifying a source or destination, then the currency is created or destroyed. Where it resolves ambiguity, the asset or currency being referred to is the currency designated as "Agora's official currency", if there is one. Assets are always public. [To provide for private contract based assets later] Change the power of Rule 2166 to 3.0. Change the rule "Economics" to read in full: Shinies (sg. shiny) are an indestructible 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. 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. For the avoidance of doubt, all shinies existing under the old system continue to so under the new system, and if they would not otherwise do so, new shinies are created to replace them. Amend the rule "The Surveyor" to have the following text: The Surveyor is an office, and the recordkeepor of estates. Amend the rule "Estates" to have the following text: An Estate is a type of indestructable liquid asset, which can be owned by players, organizations, and Agora. The following changes are secured: creating, modifying, or destroying
