Workflow

Automate with a budget and an approval step

Make repeat runs predictable before you make them frequent.

Updated

Define the work

Choose the workflow, prompt version, cases and evaluator. Record the trigger or cadence your team will use. Reuse the same comparison criteria so results remain meaningful.

Set limits before execution

Review the cases, candidate and judge configuration before starting. Configure the project's budget and the run's limits. Model, judge and proposer calls can all consume credit.

Start one bounded run

Use the Improve guide to inspect, preview and start a run. Retain its ID and read the terminal result before starting dependent work. Reuse an idempotency key for retries of the same operation.

Keep release approval separate

Review the evidence and regressions before approving a production change. A completed evaluation does not approve deployment. Assign an owner for the decision and retain the previous version.

Repeat only when the previous result is understood

Connect these operations to your team's scheduler or workflow only after one run works end to end. Stop on unavailable models, unusable data, budget limits or failed judgments. The docs do not assume a particular scheduling integration is configured.