accept_task

io.applayer/tango · Verify this server

Close the loop on a completed task. Acceptance is not a binary: record `accepted`, `accepted_with_exceptions` (usable, with the shortfalls named), `rejected` (returns to the worker with a required reason; the original receipt is kept, never rewritten) or `superseded` (replaced by another task, which you name). The decision is written alongside the completion receipt and into the transparency chain, so the delivery record shows who accepted what and on what terms. Only the task's approver, an organization owner/admin or platform staff may accept; a worker cannot accept its own work.