> For the complete documentation index, see [llms.txt](https://batterycat.gitbook.io/message-unpacked-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://batterycat.gitbook.io/message-unpacked-docs/en/cases-and-scoring.md).

# Cases, real events, and scores

Each case is labelled as one of four provenance types:

* adapted from a documented event;
* composite of documented events;
* classic pattern; or
* teaching fiction.

Documented and composite cases include reviewable sources. Impact figures state their scope and qualifier; missing public information is shown as unknown, not zero. The source date and review date help teachers decide whether current official guidance should be checked again.

## Three judgments

* **Fraud:** the request and red flags are sufficient to classify the message.
* **Insufficient evidence:** the message may be genuine or harmful, so the learner should verify through an independently known channel before acting.
* **Trustworthy:** the message makes a bounded, verifiable request without the risk pattern tested by the case.

The library includes all three so that learners do not practise treating every message as fraud.

## How to use scores

Choices receive different scores based on both the judgment and the proposed action. A lower score is an invitation to compare evidence and choose a safer next step; it is not a label for the learner.

In projector or live mode, ask which clue changed the class's view, what information is still missing, and which verification channel does not depend on the message being assessed.