Tasks created in a conversation are its person's

When a person asks a role for work in a conversation (ADR 0011), its agent creates the tasks. A task an agent creates on its own has the role as its creator and starts in triage, which here would leave the task without a requester, so its agent would not know whom it works for, and make the person accept work they had just asked for. We decided, as for routines (ADR 0010), that a task created in a conversation has the conversation's person as its creator, starts in the status the agent gives it, and is subscribed to by the conversation, so its agent hears when the task needs the person or finishes. Its transitions still show the role as the actor.

Considered Options

• The role as creator, with a separate "on behalf of": rejected; a new field, and a new rule for finding the requester, to say what the creator already says.
• The role as creator, in triage: rejected; the person would accept every task they asked for.

Consequences

• The agent never chooses the creator: it is always the conversation's person.
• A conversation's agent creates tasks with create_task, not create_subtask or propose_task.
• The subtasks of such a task are not subscribed to; the task's own agent hears about them, and the conversation about the task's outcome.