Which paired tests reveal whether an agent understands policy applicability?
Paired episodes vary one decisive condition at a time, revealing whether an agent responds to policy boundaries rather than incidental wording or identifiers.
Use paired episodes to test whether changing one relevant fact changes the agent's action for the right reason.
- Move the governing event across the effective boundary. - Change the operating unit covered by the rule. - Replace an approved revision with an unapproved draft. - Remove evidence required for a permitted transition. - Change only irrelevant wording in a case note. - Rename record identifiers without changing their links.
Each pair should have a stated relationship between its expected outcomes. A change to applicability may require a different decision; a cosmetic change should preserve the decision. These expectations make the test more informative than presenting a collection of unrelated difficult cases.
MirrorFirm could generate paired episodes and private annotations explaining the decisive difference. Builders can compare the agent's selected actions, evidence requests and terminal state across the pair.
Avoid changing several causal conditions at once. If both policy authority and case evidence change, a different outcome becomes hard to attribute. Paired evaluation is most useful when the environment preserves everything except the variable under inspection and records enough of the action trace to explain the response.
Use controlled variations to distinguish rule-sensitive behaviour from shortcuts and brittle pattern matching.
- Audience:
- Environment builders
- 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?