Mutation path does not start with a slash

artf.mutation.path_not_absoluteerrorARTF mutation set

ARTF semantic paths are rooted at the payload, so they begin with /.

What it means

The path is present but does not start with /. Every path in the specification and in the reference implementation is rooted.

Why it matters

A relative-looking path leaves the orchestrator guessing what it is relative to, and the two plausible guesses, the payload root and the previous mutation's target, resolve to different entities.

How to fix it

Root the path at the payload: imp/imp-1 becomes /imp/imp-1.

Example that trips it

{ "intent": "ACTIVATE_DEALS", "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.