Re: BUS: Re: OFF: [Promotor] Distribution of Proposal 8026

2018-03-05 Thread Ned Strange
I vote PRESENT on all proposals pending

On Tue, Mar 6, 2018 at 1:32 PM, Edward Murphy  wrote:
>> 8026*  G.   1.0  ZombiceptionG.  3 sh.
>
> FOR
>



-- 
>From V.J. Rada


Re: BUS: Re: OFF: [ADoP] Metareport

2018-03-05 Thread Ned Strange
I initiate an election for notary and stand for the position, CB and
Aris supporting.

On Tue, Mar 6, 2018 at 1:31 PM, Edward Murphy  wrote:
> VJ Rada wrote:
>
>> CoE: I believe, in the same message I announced my candidacy for
>> reportor, I also initiated an election for notary?
>
>
> Denied. You announced intent, Aris and Cuddle Beam supported, but
> (unless I missed a message) you never actually initiated it.
>



-- 
>From V.J. Rada


Re: BUS: Re: OFF: [ADoP] Metareport

2018-03-05 Thread Edward Murphy

VJ Rada wrote:


CoE: I believe, in the same message I announced my candidacy for
reportor, I also initiated an election for notary?


Denied. You announced intent, Aris and Cuddle Beam supported, but
(unless I missed a message) you never actually initiated it.



BUS: Re: OFF: [Promotor] Distribution of Proposals 8024-8025

2018-03-05 Thread Edward Murphy

8024*  [1]  2.0  Nomicbots Minigame  CuddleBeam  1 Paper

PRESENT

8025*  Corona   2.0  EFDoA [2]   Corona  1 Paper

PRESENT



BUS: Re: OFF: [Promotor] Distribution of Proposals 8024-8025

2018-03-05 Thread Kerim Aydin


CoE:

The Proposal Pool (and distribution) is missing my pended proposal 
submitted here:
https://mailman.agoranomic.org/cgi-bin/mailman/private/agora-business/2018-February/037880.html


On Sun, 4 Mar 2018, Aris Merchant wrote:
> I hereby distribute each listed proposal, initiating the Agoran
> Decision of whether to adopt it, and removing it from the proposal
> pool. For this decision, the vote collector is the Assessor, the
> quorum is 3.0, the voting method is AI-majority and the valid options
> are FOR and AGAINST (PRESENT is also a valid vote, as are conditional
> votes).
> 
> ID Author(s)AI   Title   Pender  Pend fee
> ---
> 8024*  [1]  2.0  Nomicbots Minigame  CuddleBeam  1 Paper
> 8025*  Corona   2.0  EFDoA [2]   Corona  1 Paper
> 
> The proposal pool currently contains the following proposals:
> 
> IDAuthor(s) AI   Title
> ---
> pp1   Gaelan, [3]   3.0  PAoaM Patch
> 
> [1] CuddleBeam, Gaelan, ATMunn, Trigon, Kenyon
> [2] Ensure fair distribution of assets
> [3] Trigon
> 
> Legend: * : Proposal is pending.




BUS: Re: OFF: [Promotor] Distribution of Proposals 8024-8025

2018-03-05 Thread Kenyon Prater
I vote FOR and FOR

On Mar 4, 2018 4:30 PM, "Aris Merchant" 
wrote:

I hereby distribute each listed proposal, initiating the Agoran
Decision of whether to adopt it, and removing it from the proposal
pool. For this decision, the vote collector is the Assessor, the
quorum is 3.0, the voting method is AI-majority and the valid options
are FOR and AGAINST (PRESENT is also a valid vote, as are conditional
votes).

ID Author(s)AI   Title   Pender  Pend fee
---
8024*  [1]  2.0  Nomicbots Minigame  CuddleBeam  1 Paper
8025*  Corona   2.0  EFDoA [2]   Corona  1 Paper

The proposal pool currently contains the following proposals:

IDAuthor(s) AI   Title
---
pp1   Gaelan, [3]   3.0  PAoaM Patch

[1] CuddleBeam, Gaelan, ATMunn, Trigon, Kenyon
[2] Ensure fair distribution of assets
[3] Trigon

Legend: * : Proposal is pending.

A proposal may be pended for 1 Paper or Without Objection.

The full text of the aforementioned proposals is included below.

//
ID: 8024
Title: Nomicbots Minigame
Adoption index: 2.0
Author: CuddleBeam
Co-authors: Gaelan, ATMunn, Trigon, Kenyon


Create the following rule with Power = 2.0 and title "Nomicbots":


-

Nomicbots are an asset. Each Nomicbot has Instructions, a Name, a Banner
and a Memory Capacity. A Nomicbot's Instructions is a text document with
instructions about its behavior. A Nomicbot's Instructions is blank by
default. A Nomicbot's name is a string, defaulting to "Nomicbot". A
Nomicbot's Banner is a switch with values of Risen or Lowered, defaulting
to Lowered. A Nomicbot's Memory Capacity in a numerical switch, which
defaults to 100.

Any player CAN create a Nomicbot in eir possession by announcement by
destroying 1 ore. A Player can change their Nomicbot's Name or Banner by
announcement. A Player CAN destroy X of their corn and stone to cause
modifications to the text of the Instructions of one of their Nomicbots
which
involve adding or removing up to X*3 characters (e.g. adding A characters
and removing B characters, where A+B < X), by announcement, unless this
would cause its Instructions to have more characters than its Memory
Capacity, in which case its INEFFECTIVE.

A Player CAN destroy 1 of their fabric per 50 Memory Capacity a Nomicbot
they own has, to increase the Memory Capacity of that Nomicbot by 50, by
announcement.

Nomicbots can Battle, and there is a Battle at the Main Arena among all
eligible Nomicbots at the start of each Month, hosted by the Botmastor -
this is the Monthly Battle. A Nomicbot is eligible if they are the only
Nomicbot belonging to a player with a Banner with a value of Risen.

If a Nomicbot wins the Monthly Battle, their owner earns 1/Z Merit (a
non-transferable
and indestructible asset), where Z is the amount of Nomicbots which won
that Battle. When a player has 1 Merit, they win the game and lose all
their Merit.

Nomicbot Battles are games of Nomic, played according to the Arena they
take place at along:
- With the players being the Nomicbots
- All Judge and interpretation requirements specific to the Battle
defaulting to the Botmastor.
- If the result of a Nomicbot's Instructions at a situation is not
unambiguous or determinate, or overly rely on external information, that
Nomicbot crashes at that moment, and is then removed from play from that
Battle.
- If the Battle would never end, it instead ends with nobody as the winner.

Arenas are rulesets of Nomic, tracked by the Botmastor, and Arenas have a
Status switch of Main or Secondary (defaulting to Secondary). The Botmastor
CAN
add or remove a Secondary Arena with 2 Agoran Consent. The Botmastor CAN
set the Status of an Arena to Main with 2 Agoran Consent. Doing this sets
the Status of all other Arenas to Secondary .

The Botmastor is an Office. The Botmastor shall publish a report within the
first week of each month with:
- The results of the Monthly Battle and their processing of it (and CAN and
SHALL do this manual processing).
- The Instructions, Name, Banner, Memory Capacity and owner of each
Nomicbot.


-

Then, add Peter Suber's original Nomic Initial Ruleset as a Main Arena.

//
ID: 8025
Title: Ensure fair distribution of assets
Adoption index: 2.0
Author: Corona
Co-authors:


Amend rule "Asset generation with facilities" by replacing the first item on
the list with the following two items, renumbering the other items
appropriately:

  1. if the facility is built on unconserved Public Land, none.

  2. if the facility is built on preserved 

BUS: Re: OFF: [Promotor] Distribution of Proposals 8024-8025

2018-03-05 Thread Cuddle Beam
I vote FOR and FOR

On Mon, Mar 5, 2018 at 1:29 AM, Aris Merchant <
thoughtsoflifeandligh...@gmail.com> wrote:

> I hereby distribute each listed proposal, initiating the Agoran
> Decision of whether to adopt it, and removing it from the proposal
> pool. For this decision, the vote collector is the Assessor, the
> quorum is 3.0, the voting method is AI-majority and the valid options
> are FOR and AGAINST (PRESENT is also a valid vote, as are conditional
> votes).
>
> ID Author(s)AI   Title   Pender  Pend fee
> 
> ---
> 8024*  [1]  2.0  Nomicbots Minigame  CuddleBeam  1 Paper
> 8025*  Corona   2.0  EFDoA [2]   Corona  1 Paper
>
> The proposal pool currently contains the following proposals:
>
> IDAuthor(s) AI   Title
> 
> ---
> pp1   Gaelan, [3]   3.0  PAoaM Patch
>
> [1] CuddleBeam, Gaelan, ATMunn, Trigon, Kenyon
> [2] Ensure fair distribution of assets
> [3] Trigon
>
> Legend: * : Proposal is pending.
>
> A proposal may be pended for 1 Paper or Without Objection.
>
> The full text of the aforementioned proposals is included below.
>
> //
> ID: 8024
> Title: Nomicbots Minigame
> Adoption index: 2.0
> Author: CuddleBeam
> Co-authors: Gaelan, ATMunn, Trigon, Kenyon
>
>
> Create the following rule with Power = 2.0 and title "Nomicbots":
>
> 
> -
>
> Nomicbots are an asset. Each Nomicbot has Instructions, a Name, a Banner
> and a Memory Capacity. A Nomicbot's Instructions is a text document with
> instructions about its behavior. A Nomicbot's Instructions is blank by
> default. A Nomicbot's name is a string, defaulting to "Nomicbot". A
> Nomicbot's Banner is a switch with values of Risen or Lowered, defaulting
> to Lowered. A Nomicbot's Memory Capacity in a numerical switch, which
> defaults to 100.
>
> Any player CAN create a Nomicbot in eir possession by announcement by
> destroying 1 ore. A Player can change their Nomicbot's Name or Banner by
> announcement. A Player CAN destroy X of their corn and stone to cause
> modifications to the text of the Instructions of one of their Nomicbots
> which
> involve adding or removing up to X*3 characters (e.g. adding A characters
> and removing B characters, where A+B < X), by announcement, unless this
> would cause its Instructions to have more characters than its Memory
> Capacity, in which case its INEFFECTIVE.
>
> A Player CAN destroy 1 of their fabric per 50 Memory Capacity a Nomicbot
> they own has, to increase the Memory Capacity of that Nomicbot by 50, by
> announcement.
>
> Nomicbots can Battle, and there is a Battle at the Main Arena among all
> eligible Nomicbots at the start of each Month, hosted by the Botmastor -
> this is the Monthly Battle. A Nomicbot is eligible if they are the only
> Nomicbot belonging to a player with a Banner with a value of Risen.
>
> If a Nomicbot wins the Monthly Battle, their owner earns 1/Z Merit (a
> non-transferable
> and indestructible asset), where Z is the amount of Nomicbots which won
> that Battle. When a player has 1 Merit, they win the game and lose all
> their Merit.
>
> Nomicbot Battles are games of Nomic, played according to the Arena they
> take place at along:
> - With the players being the Nomicbots
> - All Judge and interpretation requirements specific to the Battle
> defaulting to the Botmastor.
> - If the result of a Nomicbot's Instructions at a situation is not
> unambiguous or determinate, or overly rely on external information, that
> Nomicbot crashes at that moment, and is then removed from play from that
> Battle.
> - If the Battle would never end, it instead ends with nobody as the winner.
>
> Arenas are rulesets of Nomic, tracked by the Botmastor, and Arenas have a
> Status switch of Main or Secondary (defaulting to Secondary). The
> Botmastor CAN
> add or remove a Secondary Arena with 2 Agoran Consent. The Botmastor CAN
> set the Status of an Arena to Main with 2 Agoran Consent. Doing this sets
> the Status of all other Arenas to Secondary .
>
> The Botmastor is an Office. The Botmastor shall publish a report within the
> first week of each month with:
> - The results of the Monthly Battle and their processing of it (and CAN and
> SHALL do this manual processing).
> - The Instructions, Name, Banner, Memory Capacity and owner of each
> Nomicbot.
>
> 
> -
>
> Then, add Peter Suber's original Nomic Initial Ruleset as a Main Arena.
>
> //
> ID: 8025
> Title: Ensure fair distribution of assets
> Adoption index: 2.0
> Author: Corona
> Co-authors:
>
>
> Amend rule "Asset generation with facilities" by