Write answerability cases with expected decisions before running the policy. Include absent and contradictory evidence.
Name the expected effect, metric and what would count against the hypothesis.
Record fixtures, source, version, parameters, units, controls and how cases are split.
| Case and split | Baseline result | Changed result | Interpretation |
|---|---|---|---|
A high-scoring passage can be about the right topic while lacking the required fact; removing a source must change answerability.
Record your new case and rerun the original cases after redesign.
Explain the mechanism, one exact result and what would overturn your conclusion.
This policy tests answerability logic, not natural-language entailment or generated answer correctness.
Next test: _ . Project filename: _ . Work that is mine and tools I used: ____ .
Use fictional data. Download a resumable project before changing devices. On a shared device, turn remembering off and clear your work when finished.