THE AGORA NOMIC CODE OF REGULATIONS
These ACORNs are also online at http://agoranomic.org/ruleset/
Date of this ACORN: 1 Dec 2020
------------------------------------------------------------------------
Table of Contents:
Auction Regulations
* Regulation AM0: Generalized Auction
* Regulation AM1: Forward Auctions
* Regulation AM2: Sealed-bid Auctions
* Regulation AM3: Second-price Auctions
* Regulation AM4: Nonwinning-price Auctions
* Regulation AM5: Selective-bid Auctions
Emergency Regulations
* Regulation ER0: to the moooooon
* Regulation ER1: BOO! err, am I late?
Administrative Regulations
* Regulation PA0: Certification
* Regulation PA1: Proposal Style Guide
------------------------------------------------------------------------
========================================================================
Auction Regulations
This section has the regulations, written by the Treasuror, governing
how auctions proceed.
------------------------------------------------------------------------
Regulation AM0/0
Generalized Auction
Generalized auctions exist to give context to the form of other
types of auctions. They cannot be held directly. Other auction
methods that use this type of auction as a starting point can
override attributes of generalized auctions except when it is
explicitly stated that that attribute is not able to be
overridden.
1. INITIATION:
* The auctioneer CAN begin an auction that e is authorized to
by creating a public message (henceforth the "initiation
message"), specifying the type of auction method that will
be held, a list of lots that will be auctioned off, and the
currency that the auction uses. Bidding is initally open.
* Derivative auction methods cannot specify the exclusion of
any information listed above from the initiation message of
auctions using that method.
2. BIDDING:
* Players CAN place a bid on an open auction by creating a
public message (henceforth a "bid message") specifying a
number of the auction's currency as eir bid not equal to the
bid of another player.
* Players CAN withdraw from an open auction by announcement.
3. TERMINATION:
* Bidding is closed four days after either the beginning of
the auction or after the most recent bid was placed,
whichever is later. The auction ends at this time as well.
4. AWARDING:
* For each auction, there are a number of awardees equal to
the number of lots. The Nth lot of an auction goes to the
Nth awardee of that auction. If the identity of an awardee
is undecidable, then that lot cannot be given away.
* Auction methods specify how awardees are picked for auctions
using that method.
* Derivative auction methods should ensure that only players
who have at least as much of that auction's currency as eir
highest bid on that auction (hereafter "funded players") can
be selected as awardees for auctions using that auction
method.
* The auctioneer of an auction SHALL within, four days after
the ending of that auction, create a public message
(henceforth the "termination message") that contains a full
history of bids on the auction and withdrawals from the
auction. It should also clearly indicate each awardee and
the lot e recieves.
5. CLAIMING:
* For a period of seven days after an auction ends, each
awardee of that auction CAN transfer (or create in eir own
possession if the item is new) the set of assets associated
with the lot e won by paying a fee corresponding to eir
winning bid.
History:
Enacted by Trigon, 08 Aug 2020
Annotations:
------------------------------------------------------------------------
Regulation AM1/0
Forward Auctions
Forward auctions function like generalized auctions except:
* The Nth awardee for a forward auction is the player who
submitted the Nth-highest bid in the set of all funded,
non-withdrawn players' highest bids on that auction.
History:
Enacted by Trigon, 08 Aug 2020
Annotations:
------------------------------------------------------------------------
Regulation AM2/0
Sealed-bid Auctions
Sealed-bid auctions function like generalized auctions except:
* Players can only submit bids on a sealed-bid auction if they do
not have a bid in that auction.
* Bids must be initially hidden so that it is impossible to tell
its value but that it is verifiable that the amount bid was *
decided before the bid was placed. Anything that claims to be a
bid and fits these conditions is considered a bid.
* Sealed-bid auctions do not end when bidding is closed. Instead,
they end four days afterward.
* Each player SHOULD reveal eir bid amount on a sealed-bid auction
while the auction is closed but has not ended. If e does not do
so then eir bid is nulled.
* The termination message also includes whether or not each bid is
null.
* The Nth awardee of a sealed-bid auction is the non-withdrawn
funded player whose bid is not nulled and is the Nth highest of
all bids placed.
History:
Enacted by Trigon, 08 Aug 2020
Annotations:
------------------------------------------------------------------------
Regulation AM3/0
Second-price Auctions
Second-price auctions function like forward auctions except:
* When claiming lots in a second-price auction, awardees instead
pay a fee corresponding to the next-highest bid in the set of
all funded, non-withdrawn players' highest bids in that auction.
History:
Enacted by Trigon, 08 Aug 2020
Annotations:
------------------------------------------------------------------------
Regulation AM4/0
Nonwinning-price Auctions
Nonwinning-price auctions function like forward auctions except:
* When claiming lots in a nonwinning-price auction, awardees
instead pay a fee corresponding to the highest bid on that
auction from a funded, non-withdrawn player who is not an
awardee.
History:
Enacted by Trigon, 08 Aug 2020
Annotations:
------------------------------------------------------------------------
Regulation AM5/0
Selective-bid Auctions
Selective-bit auctions function like generalized auctions except:
* Bidding messages on a selective-bid auction must also specify a
lot that is preferred.
* The Nth awardee of a selective-bid auction is the highest bid
from a funded, non-withdrawn player whose preferred bid is that
lot.
History:
Enacted by Trigon, 08 Aug 2020
Annotations:
------------------------------------------------------------------------
========================================================================
Emergency Regulations
This section has Emergency Regulations, providing a way to change the
gamestate during states of extreme emergency.
------------------------------------------------------------------------
Regulation ER0/0
to the moooooon
The publicity of the Lunar Laser Ranging experiment is set to
Discussion.
History:
Enacted by Rulebending Form demonstrated by G., 04 Sep 2020
Annotations:
------------------------------------------------------------------------
Regulation ER1/0
BOO! err, am I late?
When this regulation is created, G.'s Ministry Focus is flipped to
Legacy.
History:
Enacted by Rulebending Form demonstrated by G., 01 Nov 2020
Annotations:
------------------------------------------------------------------------
========================================================================
Administrative Regulations
This section has regulations enacted by officers, pursuant to Rule
2630.
------------------------------------------------------------------------
Regulation PA0/0
Certification
For the Promotor to cause a proposal to become pending with 2+N
support, where N is equal to the number of times e has done so in
the past 7 days, is for em to certify it.
A proposal is certifiable if:
1. it is reasonably narrowly tailored to fix one or more problems,
including a) bugs, b) errors, c) ambiguities, and d)
vulnerabilities*; or
2. unusual or exigent circumstance render it in the public
interest for it to become pending via this method.
* Note: Any of these problems may arise from a single source or
the interaction of multiple sources, which may be individually
unproblematic. This provision is to be interpreted broadly and
flexibly to effectuate its spirit.
The Promotor SHOULD NOT certify a non-certifiable proposal.
Players SHOULD support an intent to certify a proposal if and only
if it is certifiable.
The author of a proposal in the pool CAN, by announcement, request
certification of the proposal, provided e does so in a message
that has either "Promotor" or "Proposal" in the subject line; e
SHOULD NOT do so unless e believes eir proposal is certifiable and
is ENCOURAGED to explain why eir proposal is certifiable. Once
certification is requested, the Promotor SHALL respond publicly
before publishing the next report that contains the proposal,
unless the proposal is withdrawn or pended in the interim.
Petitioning the Promotor to certify a proposal is DEPRECATED.
History:
Enacted by Aris, 13 Sep 2020
Annotations:
------------------------------------------------------------------------
Regulation PA1/0
Proposal Style Guide
Players SHOULD format proposals in accordance with the following
guidelines. These guidelines represent the Promotor's preferred
formatting. Most of these guidelines are flexible recommendations,
but where something is marked as STRONGLY DISCOURAGED, doing it is
actively inconvenient for the Promotor.
I. Headers and Metadata.
1. Format headers as close as possible to the heading used for
distributions, which looks like this:
Title: _____
Adoption index: _._
Author: ____
Co-authors: ____, ____
To be clear:
a) write the fields in that order;
b) write out all the fields, even the ones that have default
values; and
c) write each field on its own line.
2. a) Give proposals titles 35 characters or less.
b) Giving proposals titles over 70 characters is STRONGLY
DISCOURAGED.
II. Bodies.
1. Indent Proposals two spaces per indent level.
2. a) Wrap proposal lines to 80 characters or less.
b) Making it so the Promotor cannot wrap lines to 80 characters
or less is STRONGLY DISCOURAGED unless it is absolutely
unavoidable (e.g. in the case of URLs).
3. Players are STRONGLY DISCOURAGED from placing markings that
indicate the start of the proposal's text on the same line as
the start of the text.
History:
Enacted by Aris, 13 Sep 2020
Annotations:
------------------------------------------------------------------------
