`record_feedback`

Record feedback. Save a learning note on one exact version of a piece (yours or a producer's).

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: "record_feedback", 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 note.

Inputs

Input	Type	Needed	About
`source`	object	yes
`source.type`	"asset"	yes
`source.id`	string	yes	format `^[a-z0-9][a-z0-9-]{0,159}$`
`source.version`	string	yes	1 to 40 characters
`source.checksum`	string	yes	format `^[a-f0-9]{64}$`
`note`	string	yes	1 to 8,000 characters
`actor`	string	yes	1 to 120 characters
`requestId`	string	yes	format `^[A-Za-z0-9_.:@-]{6,100}$`
`task`	integer	no	The task this work is for, so the owner sees it there. · 1 or more
`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": "record_feedback",
  "arguments": {
    "source": {
      "type": "asset",
      "id": "id",
      "version": "version",
      "checksum": "checksum"
    },
    "note": "Sent the quote; next: wait for her answer.",
    "actor": "actor",
    "requestId": "requestId"
  }
}

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.