Ask with the job, not the model
Open Can Jev run this and type the job in plain words. Issue the refund, send the email, check a claim, and route a support ticket are different requests. The page treats them differently.
A yes means Jev can run a bounded check: a yes or no, a choice among names you supply, or a score on a rubric you write. A no means the job is an action. The page then names the closest check that stops at a typed answer.
Read the four parts of a yes
The example is the recipe sample. Replace it with evidence from your task. The run block is the sysone_run body, or the same JSON sent to POST /v1/patterns/run.
The cost block is an input-list-rate comparison for that sample. It is not a measured saving, and it does not change a fixed-price subscription. The expectation is the recipe policy. Your agent still chooses any cutoff and still takes the action.
Where to go next
Search again when the first match is only nearby. Then open the capability article for the recipe id before you send customer evidence.
{
"pattern": "evidence-check",
"state": "Claim and the evidence you actually have."
}Keep going
Search a job on Can Jev run this, or read What Jev should not do.