`today`

How's today. Her answer to How's today (good, busy, not_great, else, or not_now), with her words if she gave any.

Where it is

In the road area (her next step, her taps, coaching moments, her programme, immersives, her review, what waits for her yes, what was made, and her office as her phone reads it): open it with tools_for { area: "road" }, then call it with use_tool { name: "today", args }.

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: her How's today tap on her own record; her words reach only the safety gate.

Inputs

Input	Type	Needed	About
`answer`	"good" \| "busy" \| "not_great" \| "else" \| "not_now"	yes
`words`	string	no	Her own words, if she gave any: only the safety gate reads them. · up to 500 characters
`request_key`	string	yes	Your key for this one act: the same key again is the same act, never twice. · format `^[A-Za-z0-9][A-Za-z0-9:._-]{0,99}$`
`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": "today",
  "arguments": {
    "answer": "good",
    "request_key": "request key",
    "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.