I think it's good to prohibit "none" from being an AI for a proposal -
it makes it easier to reason about the rest of the Rules that touch
proposals, and it might make bugs less likely for later changes that
touch AIs - you don't have to think about proposals having an AI of
"none" (even if an Agoran Decision might still have such an AI).
Currently, I don't see anything that explicitly prohibits a proposal
with an AI of "none".
If that's done, since "none" can no longer be an AI for a proposal, we
have to set the default earlier - in this case, at the time the proposal
is created.
I agree that dealing with announcements with invalid parameters should
be fixed more broadly - but I thought that I could fix it in this
specific instance since I was touching this area of the Rules anyway.
Jason Cobb
On 7/1/19 2:32 PM, Aris Merchant wrote:
I don’t think this is a great idea. It seems like a rather large addition
of rule text to fix one specific incidence of a larger problem.
-Aris
On Mon, Jul 1, 2019 at 11:30 AM Jason Cobb <jason.e.c...@gmail.com> wrote:
I submit the following proposal:
Title: Proposal AI fix
Author: Jason Cobb
AI: 3
Text:
{
[Comment: restrict proposal AIs to valid adoption indices. Explicitly
provide the default for proposals, rather than Agoran Decisions as a
whole - this means that a proposal, once created, always has a valid
(numeric) adoption index.]
Amend Rule 2350 ("Proposals") by adding the following paragraph after
the paragraph beginning "Creating a proposal":
The above notwithstanding, if a player makes an announcement that e
is creating a proposal with an adoption index of "none" or an
invalid adoption index, the attempt to create the proposal is
INEFFECTIVE. If a proposal is created by an announcement that does
not specify an adoption index, the adoption index of the proposal is
1.0.
}
--
Jason Cobb
