All articles

Boundaries

What Jev should not do

Jev should not send, pay, execute, delete, write the artifact, or drive the browser. Each refusal has a check that stays in bounds.

Actions stay with your agent

Sending a message has a recipient. Moving money has an amount. Running a tool changes something. Jev does not do those things. A choice named send, prepare, or clear is advice about evidence you supplied.

Writing the novel or the implementation is also out of bounds. Jev returns a typed answer. It does not produce the draft, the code, or the plan.

Use the nearby check

Review the draft with reply-review before anyone sends it. Review the refund request with payment-review before anyone moves money. Classify the exact tool call with tool-approval before anything runs. A clear result is still not permission to execute.

Flag instructions inside a retrieved passage with passage-policy. That flag is not a security boundary. Treat the text as data. Triage a support message with ticket-triage. The recipe recommends a queue. It does not close the case.

A probability is not proof

A yes-or-no result near 0.5 means that question is uncertain. Confidence appears on a choice or a score only when the provider sends it. You choose any cutoff from cases you have labeled. System One does not retry a failed call.

Keep going

Search a job on Can Jev run this, or read How to read a Jev answer.