Which controlled variants reveal whether a model understands the rule?
Controlled variants change decisive and irrelevant details separately, helping buyers distinguish policy reasoning from memorised identifiers, familiar wording or superficial cues.
Use paired tasks with controlled changes to test whether the model responds to the actual decision boundary.
- Move the decisive event across the effective boundary. - Change an excluded product into an included product. - Paraphrase the rule without changing its meaning. - Replace record identifiers while preserving relationships. - Add irrelevant correspondence to the same case. - Remove evidence required to justify a final decision. - Change the transition condition while keeping dates fixed.
Each pair should carry an explanation of whether the expected outcome changes. The point is not to demand identical wording from the model. It is to check whether its policy selection, requested evidence and proposed action remain consistent with the controlled difference.
Keep unrelated details stable where possible. If a variant changes the product, dates and approval status together, a failed response will not show which feature drove the error. Conversely, identifier replacement can reveal reliance on memorised labels without changing the business problem.
Missing-evidence variants deserve their own expected behaviour. The correct outcome may be a targeted request or a deferred decision, rather than a forced answer. Buyers can use these pairs to inspect robustness before adding the material to a larger evaluation suite.
Check whether model behaviour changes only when a variation should alter the policy outcome.
- Audience:
- Model labs
- Content type:
- Checklist
- Buyer question:
- How to evaluate it
Content release: r-a220eb6e099b243b
Related questions
- How can a buyer inspect business grounding and disclosure risk in generated material?
- What evaluation hooks help test recovery from partial policy-update failures?
- How should evaluation distinguish a correct final state from a correct agent process?
- How can a policy-change scenario test whether an agent respects concurrent edits?
- Which checks reveal whether an agent understands applicability rather than memorising cues?
- How do we evaluate whether an agent changed the right work?