# Sample Six-Category Codebook

This is a **demonstration codebook**, built to show methodology and coding
discipline. A real engagement always codes against the client's own
codebook and definitions — this sample stands in for one so a buyer can see
how a job gets handled before commissioning it.

| Code | Label | Definition |
|------|-------|------------|
| IR | Informational Request | Speaker asks for, or supplies, facts, clarification, or instructions. |
| PR | Problem Report | Speaker describes a fault, obstacle, or discrepancy they've encountered. |
| EE | Emotional Expression | Speaker's primary content is a feeling — frustration, gratitude, worry, relief, excitement. |
| SA | Solution / Action Proposal | A next step, fix, or decision is proposed and/or agreed. |
| SR | Social / Relational | Greetings, congratulations, small talk — rapport-building with no task content. |
| OU | Off-topic / Uncodable | Doesn't fit the above, or the text is too unclear/garbled to code. |

## Coding rules applied

1. **One code per exchange**, chosen by the *dominant* content — a message
   can contain a pleasantry and still code as PR if the fault report is the
   point of the exchange.
2. **Ties broken toward the substantive code.** Social framing around a
   real request or problem does not push it to SR.
3. **OU is a last resort** — used only when no other code plausibly fits,
   not as a dumping ground for ambiguous-but-codable text.
4. Every row carries a **one-line rationale** so a client can audit the
   call, not just the label.

See `coded-sample.csv` for the full worked example (20 exchanges, this
codebook applied).