On 07/06/2026 23:04, msh210 wrote:
My recent mistake (
https://www.mail-archive.com/[email protected]/msg57919.html
) shows that one _cannot_ create a scheduled action on behalf of
someone else, since there's no rule allowing one to do so. Am I
missing something (again)?
There are generally two preconditions:
1. You must have authorization to act on someone else's behalf.
2. The specific action you're trying to take must not forbid it.
By default, you are not authorized to act on someone else's behalf, but
you can create Contracts and Promises to provide blanket authorization.
(This means that the loophole is opt-in, so it's not *that* critical,
but it still exists.)
I don't see that the action taken would be by B as emself. The rule
says that the scheduled action's "creator [presumably B] performs
actions as if e had published its Payload at that time" of the
trigger. Even so, it's not clear to me that B performs actions as if
e had published the payload _on eir own behalf_ at that time. The
rule doesn't certainly say so. Quite possibly, the rule means that B
performs actions as if e had published the payload _via agent A_ at
that time. (Of course, that's what you're protoproposing anyway, so
it sounds good to me. I'm just saying I'm not convinced it's
necessary.)
Acting on one's own behalf is the default state. The loophole hinges on
the idea that, after a Scheduled Action has been created, it is an
independent entity that *doesn't care* about how it came into existence.
It only cares about its Trigger and its Payload, and, once the Trigger
is reached, it executes its Payload just like any other Scheduled Action
would.
--
Salad