Skip to main content

Module tasks

Module tasks 

Source
Expand description

A person’s decision as an agentplane human task.

Where a call needs a person, the attempt waits on a task whose justification is the call exactly as the prompt shows it. Whoever answers — at the terminal, in an editor, or later with speccoder task approve — decides that task with an operator; the decision is journal history, bound to the digest of what was shown.

Structs§

Read
What the attempt reads from a recorded decision. An expiry is a refusal nobody made: by is None and expired is set.

Constants§

APPROVAL
The task kind of a call waiting for approval.
DEADLINE
The obligation every wait for a person is bounded by.
QUESTION
The task kind of a question to a person.

Functions§

approval_task
The waiting task for a call: the exact call, the question as the journal holds it, and the object an approval would cover. Only journaled facts go in — the approval is bound to this task’s digest, so replay must rebuild it byte for byte; the presentation (the file as it is, the sandbox) is built live by whoever asks.
ask
Asks approver about a waiting task now. None when the person answers “later” (the call keeps waiting), the call waits in its run’s batch (the asking budget is used: nobody is interrupted), or the task is not one of ours. The answer comes with the decision.
decision_for
A person’s answer as the decision recorded for its task: the scope, note, channel and any answer text travel in the amendment.
presentation_of
The waiting call as the person sees it here, now.
question_task
The waiting task for a question from task (skill/<name>).
read
Reads a recorded decision back.
request_of
The question a waiting approval task carries.