Skip to main content
Goal: replace the invoice example with exact rules that your organization owns. You are done when: your customized check has a local passed: true report for a pass, a rejection, and a technical failure with no verdict. Use this recipe when a candidate must satisfy a schema, contain required fields, match approved identifiers, or pass arithmetic and cross-field rules. Do not use a semantic evaluator for arithmetic, schema validation, allowlists, or another rule that ordinary code can decide exactly. An invoice passes when its supplier is approved and its total equals the sum of its integer minor-unit amounts. A mismatch or non-integer amount_cents rejects; an unavailable policy source returns no verdict.
1

Create the example

Expected result: selected_recipe is a, selected_check ends in recipe-a-structured-output.mjs, deployed_check ends in selected-check.mjs, and next_action tests selected-check.mjs.
2

Run the local cases

Run the printed command:
Expected result: passed is true. Check the labelled outcomes if a case fails.
  • labelled.a-pass-reconciled-invoice as a pass;
  • labelled.a-reject-total-mismatch as a rejection;
  • labelled.a-reject-fractional-cents as a rejection; and
  • labelled.a-technical-policy-store as HTTP 500 with no verdict.
Recovery: if the CLI does not recognize --recipe, stop. Check the install guide for a recipe-capable version; until it lists one, use its non-recipe path. If a labelled case fails, change the rule and its expected case together, then rerun the same local command.
3

Replace the example rules

Edit recipe-a-structured-output.mjs:
  1. replace the example supplier IDs with your approved values;
  2. define every required field and accepted type;
  3. require safe integer minor units in amount_cents and total_cents;
  4. keep optional completeness in scoreQuality;
  5. add representative pass, rejection, and unavailable-dependency cases.
A high quality score must not override a failed identifier or total check. Rerun the Step 2 command against selected-check.mjs after your edits. Deploy only when your own pass, rejection, and technical-failure cases all pass.
4

Continue to deployment

Read the shared endpoint contract and reserved-probe limits. Your next executable step is Deploy and test HTTPS. Continue with Recipe 0 for connection, paid-run approval, receipt reading, and recovery. In the final receipt for a checked run, confirm supplier_approved, line_amounts_valid, and total_reconciles under named results.
Give the assistant only non-secret business rules and representative fixtures. Require it to show the three labelled outcomes before deployment. Enter keys yourself, approve endpoint test traffic, and approve any paid run separately.