You want it to work where the players are the input device and Agora
regularly checks for changes from the players, but I want it to be that
players are the input and change Agora.
On 10/15/2017 08:52 PM, Gaelan Steele wrote:
I’m afraid I don’t get the analogy.
Gaelan
On Oct 15, 2017, at 5:52 PM, Publius Scribonius Scholasticus
<p.scribonius.scholasti...@gmail.com> wrote:
I disagree with this. I think the distinction is that you want Agora to work
like USB, whereas now Agora works like PS/2.
On 10/15/2017 08:45 PM, Gaelan Steele wrote:
There are many places where Agora essentially calls eval(T), where T is some
text from a player. This includes:
The rules, of course
Proposals
Regulations
Other powered instruments (do we have any of those lying around?)
Public messages
Orgs
Agencies
Contracts
Old Pledges
Conditional votes
CFJs
I think we need a simple way to state in the rules that agora “reads” a piece
of text and changes the gamestate accordingly, according to some list of things
that that text is allowed to do:
* Proposals can impact things tracked by the rules
* Public messages can perform by-annoucement actions, etc
* Contracts can authorize player actions (contract-by-announcement) and punish
players
* Conditional votes can choose a vote
* CFJs can pose a question
* The rules (I think) actually have no power over anything beyond their own
scope
I think we might want to define something like “invoking” a piece of text, or
giving an instrument with zero power the right to specify some limited things,
or something.
Gaelan
