Re: DIS: [Proto] Promises
> > Might be better to make that consent conditional on the promise being > > cashed? I can't think of a plausible situation in which it could > > matter, but here's a contrived situation. Suppose I create a promise > > saying I become a candidate for the election for some office. That > > might count as consent to be made the holder of the office under > > R1006, but probably shouldn't unless the promise actually gets cashed. > > Fair point. How about "By creating a promise, a person consents to it > being carried out when it is cashed"? Yes, I think that would take care of it. - Falsifian
Re: DIS: [Proto] Promises
Thank you for your comments! > I wonder if this rule text could be a contract. Anyone can join, and > anyone who's not the creator of a promise can leave. I thought about that. It would definitely need a helper amendment (for the acting on behalf thing, which I'm going to need to add anyway), but it *could* be. The biggest reason I'm not going that route is that I want the Notary to have responsibility for tracking (even if the current Notary agreed to track the contract state, what about future Notaries?). Anyway, this fits well in the ruleset even if it doesn't strictly speaking need to be there. > > Promises are a class of assets, tracked by the Notary. Their essential > > attributes are their title, text, and creator. A person CAN, by > > announcement, > > create a promise, specifying its text and becoming its creator. A > > promise's > > owner is referred to as its bearer. Promises with the same title, text, > > creator, and bearer are fungible. > > I think you need to say who owns a promise when it's first created. Yep. > > By creating a promise, a person consents to it being carried out. > > Might be better to make that consent conditional on the promise being > cashed? I can't think of a plausible situation in which it could > matter, but here's a contrived situation. Suppose I create a promise > saying I become a candidate for the election for some office. That > might count as consent to be made the holder of the office under > R1006, but probably shouldn't unless the promise actually gets cashed. Fair point. How about "By creating a promise, a person consents to it being carried out when it is cashed"? -Aris
Re: DIS: [Proto] Promises
I wonder if this rule text could be a contract. Anyone can join, and anyone who's not the creator of a promise can leave. > Promises are a class of assets, tracked by the Notary. Their essential > attributes are their title, text, and creator. A person CAN, by > announcement, > create a promise, specifying its text and becoming its creator. A promise's > owner is referred to as its bearer. Promises with the same title, text, > creator, and bearer are fungible. I think you need to say who owns a promise when it's first created. > By creating a promise, a person consents to it being carried out. Might be better to make that consent conditional on the promise being cashed? I can't think of a plausible situation in which it could matter, but here's a contrived situation. Suppose I create a promise saying I become a candidate for the election for some office. That might count as consent to be made the holder of the office under R1006, but probably shouldn't unless the promise actually gets cashed. - Falsifian
Re: DIS: [Proto] Promises
On 5/17/20 3:04 AM, Aris Merchant via agora-discussion wrote: > A promise's bearer CAN, by announcement, cash the promise, > provided that any conditions for cashing it specified by its text are > unambiguously met and provided that e recites the promise's essential > attributes in the same message. When e does so, e acts on the creator of > the promise's behalf, causing em to act as if e published the promise's > text. > By creating a promise, a person consents to it being carried out. Is the "as if" sufficient to bypass R2466's prohibition on acting on behalf to post messages? Since this is in a rule, it can just say that the creator performs the actions (with appropriate safeguards for things the creator CAN/CANNOT do) without any acting on behalf. -- Jason Cobb
DIS: [Proto] Promises
This represents a reenactment of an old game system, with new text. I mentioned that I was considering something like this a while ago. The original is from [1], but I didn't go back and look at it until I'd almost finished mine (that was when I decided to add the Library and the fungibility clause, but I don't think I stole much else). I'm not actually sure how much they'll be used, but I've managed to squeeze it down to a single rule so the ruleset addition isn't huge even if they aren't used much. Thoughts and comments are welcome! [1] https://mailman.agoranomic.org/cgi-bin/mailman/private/agora-official/2011-June/008818.html -Aris --- Title: Promises Adoption index: 2.0 Author: Aris Co-authors: Enact a new power 2.2 rule, entitled "Promises", with the following text: Promises are a class of assets, tracked by the Notary. Their essential attributes are their title, text, and creator. A person CAN, by announcement, create a promise, specifying its text and becoming its creator. A promise's owner is referred to as its bearer. Promises with the same title, text, creator, and bearer are fungible. A promise's bearer CAN, by announcement, cash the promise, provided that any conditions for cashing it specified by its text are unambiguously met and provided that e recites the promise's essential attributes in the same message. When e does so, e acts on the creator of the promise's behalf, causing em to act as if e published the promise's text. By creating a promise, a person consents to it being carried out. In a promise's text, "the bearer" (or the like) refers to the promise's bearer, and "this promise" (or the like) refers to the promise. The text of the promise can refer to the context of the message in which it is cashed, but the context of the message does not otherwise change the meaning of the promise. The Library is an entity and CAN own promises. Any player CAN take a promise from the Library by announcement, provided e cashes the promise in the same message. Amend Rule 2608, "The Notary", by changing the numbered list to read as follows: 1. every pledge, along with its title, creator, time window, time of creation, and time of expiry; 2. every contract, with its title, full provisions, and parties; and 3. every promise, along with its title, text, creator, and bearer.
