Mutation intent is not an ARTF Intent value
The declared intent is outside the enum, so the orchestrator cannot tell why the change is being proposed.
What it means
The mutation's intent is not one of the ARTF Intent values and does not match the document's own legacy spellings either.
Why it matters
ARTF's whole evaluation model is that a mutation declares its purpose so the orchestrator can accept or reject it on that basis. An unreadable intent is a change with no stated reason, which an orchestrator can only reject.
How to fix it
Send an enum value name or its number. Check the current proto before assuming a value is invalid: the intent set is growing, and an unknown value can be a newer intent rather than a typo.
Example that trips it
{ "intent": "ROTATE_CREATIVE", "op": "OPERATION_REPLACE", "path": "/imp/imp-1" }Check your payload
Paste a bid request or response into the tester to see whether this code fires against it, or gate on the id in CI with the CLI: the id is stable, wording is not.
Back to the full diagnostic code reference.