Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Review this generated order object: [object]. The source is [synthetic order text], and the business rules are [currency, quantity, price, rounding, identity, and allowed fields].
Treat successful parsing as the beginning of the check. Verify that extracted fields are supported by the source, referenced items actually exist in the supplied data, and totals follow the stated arithmetic and rounding rules. Distinguish absent information from contradictory information and from an invalid calculated value.
Return a compact list of passed checks and concrete failures, each tied to the source or a rule. If a correction is fully supported, propose it separately; otherwise identify the missing evidence. Do not guess a price or silently substitute a different currency.
Define deterministic validator cases for the discovered failure types. The generated object does not itself authorize a purchase, database write, or other external action.Make this prompt yours
Use for data consumed by code. Keep value validation and operation authorization as separate application responsibilities.
You might also hear
- semantic output validation
- schema-valid order
- business rule checks
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
Research sources reviewed .
Editorial review · October 28, 2026
Supported: Original, unexecuted semantic-check template. Cross-field order checks and untrusted-output handling address the documented gap between valid structure and valid meaning.