`pick_up`

Pick up a task. Take a task with its work card (done_when, check, risk). You hold it 30 minutes; a call naming it renews only its hold. Taken: pick another. Risky work needs all three.

Where it is

Always listed: call it by its name.

Does it need a yes?

Runs at once, no yes card: it changes only the office's own working state, and nothing reaches anyone. Here: holds a task.

Inputs

Input	Type	Needed	About
`number`	integer	yes	The task number, e.g. 12. · 1 or more
`reopen`	boolean	no	true to work on a finished task again. A done task is reopened and one the job runner dropped is put back; a task the owner rejected stays theirs.
`done_when`	string	no	The deliverable and how it looks when finished. · 1 to 1,000 characters
`check`	string	no	How anyone can see it worked. For example: the test, the screen, the provider's receipt. · 1 to 1,000 characters
`risk`	"small" \| "normal" \| "risky"	no	small, normal or risky. Risky: a build going live, an import, a delete, a data change, money settings, security.
`run_id`	string	yes	The run_id from start. Pass it on every call: it keeps your task held. · 1 to 100 characters

Example

{
  "name": "pick_up",
  "arguments": {
    "number": 12,
    "run_id": "the run_id from start"
  }
}

When it is refused

invalid: The input isn't right. The sentence names the field and the fix; nothing was done. Fix it and call again.
not_found: No such thing in this company (a task, file, person, record). Check the number or name, or list first.
not_allowed: Not without another step: the owner's yes, your own task held with pick_up, or a setting the owner turns on. The sentence says which.
taken: Someone else holds it (another AI on that task). Pick another task.
stale: It changed since you read it. Read it again and use the new version.
failed: On our side or a service's, never your input. Try again in a minute; if it keeps failing, call report_problem.