`programme_start`

Start a programme. Start a programme she asked for, by its id. Only one on sale; one per area. Starting costs nothing.

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: "programme_start", 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: a programme she asked for (programme.start move); costs nothing; only one on sale, one per area.

Inputs

Input	Type	Needed	About
`package_id`	string	yes	The programme's id, from her programme list or her ask. · format `^[a-z0-9][a-z0-9-]{0,79}$`
`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": "programme_start",
  "arguments": {
    "package_id": "package id",
    "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.