• AI reference · Area road

office_do

A small act in her office. A small act in her office, as her phone does it: her choice on a coaching moment, a notice switched on or off, the bookings checked.

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: "office_do", args }.

Does it need a yes?

Depends on what it changes: the everyday part runs at once, anything that reaches people or core files waits for the owner's yes. Here: her moment choice, a notice switch or the bookings check, as her phone does them.

Inputs

InputTypeNeededAbout
what"moment_choice" | "notice_switch" | "bookings_check"yes
momentstringnomoment_choice: the moment's id. · up to 10 characters
choice"keep" | "adjust" | "new" | "not_now" | "no"no
situationstringnoup to 300 characters
trystringnomoment_choice: what she'll try, in her words. · up to 300 characters
idstringnonotice_switch: the notice's id (from office_read notices). · up to 80 characters
onbooleanno
request_keystringyesYour 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_idstringyesThe run_id from start. Pass it on every call: it keeps your task held. · 1 to 100 characters

Example

{
  "name": "office_do",
  "arguments": {
    "what": "moment_choice",
    "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.