Module 06 Summary

What this module established

Refusal is a specified feature: a fixed string, an empty citation list, and a flag the caller can act on. The costs of the four outcomes are not symmetric - an unnecessary refusal is visible and recoverable, while a fluent wrong answer is acted on and surfaces later attributed to something else.

Carry forward

• "Not in the documents" and "not retrieved" produce the same output and need opposite fixes. Log every empty result; that log is your backlog.
• Compound questions are common. Answer the supported half, name the unsupported half, and expose a flag saying the response was partial.
• An eval set with no unanswerable questions never runs the refusal path, so a bug in it surfaces first in production.

Before moving on

Move on when at least a quarter of your eval cases expect refusal and you report the two failure directions separately rather than summed.

Mark complete