`submit_edit`

Submit edit. Send files on this machine as one edit, for example raw takes for a reel.

Where it is

In the edits area (edits, looks, formats, music, scores and the owner's notes on media): open it with tools_for { area: "edits" }, then call it with use_tool { name: "submit_edit", 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: a render job in the library.

Inputs

Input	Type	Needed	About
`files`	array of string	yes	Absolute paths on this machine · 1 to 50 items
`project`	string	yes	1 to 120 characters
`title`	string	no	up to 120 characters
`note`	string	no	up to 4,000 characters
`department`	string	no	format `^[a-z][a-z0-9-]{1,40}$`
`choice`	object	no	What to make: a format, a look and music. Format and look from list_formats and list_looks (or agent: you choose); music: agent, pick (with assetId) or none.
`choice.format`	string	no	up to 64 characters
`choice.look`	string	no	up to 64 characters
`choice.music`	object	no
`requestKey`	string	no	format `^[A-Za-z0-9_.:@-]{6,100}$`
`run_id`	string	no	Your run id from the connector's start, so the output ties back to this session · format `^[A-Za-z0-9_.:@-]{1,120}$`

Example

{
  "name": "submit_edit",
  "arguments": {
    "files": [
      "files"
    ],
    "project": "project"
  }
}

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.