Mutation intent is INTENT_UNSPECIFIED
The mutation declares no purpose, so it cannot be evaluated independently, which is what ARTF requires of every change.
What it means
intent is the enum's zero value, indistinguishable in protobuf from never being set.
Why it matters
The specification requires that agentic changes declare their intentions so orchestrators understand why a change is proposed, and that each change be evaluable in isolation. An unspecified intent fails both.
How to fix it
Name the intent the change serves. If no defined intent fits, the change does not have a home in v1.0, and inventing one silently is worse than not proposing it.
Example that trips it
{ "intent": "INTENT_UNSPECIFIED", "op": "OPERATION_ADD", "path": "/imp/imp-1", "ids": { "id": ["deal-2"] } }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.