Reading the record
Behind every checkbox, a story the form could not hold
The Consumer Financial Protection Bureau sorts every complaint into a Product, an Issue, and a Sub-issue. Those labels are chosen from a menu. The narrative is written by a person. This edition asks a typed-answer model to read the narratives and report what the menu left out.
Official complaint categories are useful because they are countable. "Dealing with your lender or servicer" can be tallied by month, by company, by state. But the category is a container, not a description. Two complaints filed under the same Sub-issue can describe entirely different experiences: one person was transferred between four departments and never reached a human; another was told two contradictory things by two agents on the same afternoon; a third has disputed a debt for eleven months and still receives collection letters.
This atlas gives each narrative a second reading. TypeSafe AI's Jev model answers a fixed set of typed questions about every complaint: which of five reported experiences dominates, whether each experience appears at all, how long the problem had been going on, and whether the text reads as a personal account or a templated letter. Every answer comes with a probability. The charts in Section B fade any judgment the model was unsure about, so uncertainty stays visible on the page rather than being rounded away.
The five experiences were chosen because they recur in the record and cut across the Bureau's menu: repeated transfers, contradictory instructions, inability to reach a person, disputed debt, and unresolved errors. They describe what it was like to deal with the company, not which product was involved. That is the gap this edition tries to measure.
Start at the Desk in Section A. Pick a beat, pull a sample, and run it. The Record in Section C prints every clipping with its labels. Section D is for your letter to the editor: what did you see that the categories did not?