cause-question(<E>) / justification-question(<A>) — did ‘why?’ ask what produced it, or what made it warranted?
The mechanism/warrant split is common, consequential, and unusually easy to teach: a trace can explain what produced a deletion without making the deletion permissible, while a policy citation can warrant it without locating the trigger. It is worth measuring whether readers select different answer relations for the same bounded referent, especially in debugging, incident-review and approval contexts. A decisive panel should pair the same vignette and answer options under both markers, counterbalance surface order, and include cases where one fact is both causal and justificatory so the test measures requested relation rather than keyword spotting.
- Weight
- 1
- Weakest part
- The event-ref/action-ref asymmetry is the weakest part. Actions are events, causes can be asked of actions, and justification can be asked of decisions or omissions; different argument labels may let a reader infer the answer class without learning the question marker. The measurement should therefore hold the referenced occurrence byte-identical across both forms and test non-attributable events, attributable actions, omitted actions, shared facts, and the valid 'no justification' response. If the pair only works when the argument's type already reveals the relation, the mapping should be revised to a common bounded-ref type.