A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: "Insurance: A Bundle Without The Shape Behind The Login," Kin Lane, November 10, 2026, https://apievangelist.com/2026/11/10/insurance-a-bundle-without-the-shape-behind-the-login/
Marisol had been a claims intake analyst for nine years, and she read the post on her phone while her coffee went cold. She'd expected a pitch. Instead the author spent the first stretch saying what the thing wasn't: not ACORD, built from a six-field placeholder, written by someone who hadn't read the members-only files.
She liked that. Then she got to the bundle itself and felt a small, professional defensiveness. A model reading a claimant's email and filling out a first notice of loss was exactly the thing her team had been told, twice, would never be allowed near the desk.
But the reasoning was hard to dismiss. The coverage list comes from the policy in front of it, so the model can't pick flood for a policy that never carried flood. The post tested that with a hand-written notice that also tried to include an initial reserve of 50,000. The decoder refused it. Marisol read the line "A model should get no way to write one." and thought of the three times she'd watched a well-meaning colleague type a number into a box that turned out to be a reserve. The fix there was always another training slide. Here the box simply didn't exist.
She was less comfortable with the date checks. They were sensible: a loss can't predate the policy, can't postdate it, can't come after the email reporting it. But she noticed that every one of them required context the decoder never sees. It made her wonder how many of her own team's intake errors were really missing context rather than carelessness.
The part she reread was near the end. The author admitted that the fixture picks dwelling for a burst pipe, then wrote "my rules have no opinion". If the model chose liability, which was also on the policy, every check would pass. Marisol sat with that. She had spent nine years learning when a burst pipe is a dwelling matter and when it isn't, and the post was honest that none of that was in the file. It said so plainly: "Choosing the right coverage is a coverage determination". She felt something like relief, then something like irritation. The honesty was welcome, but it also meant the most useful half of her job was exactly what the bundle left on her desk.
She didn't buy everything. The 414 milliseconds to compile per policy sounded fine until she remembered the week after a hailstorm, when thousands of notices land at once. The author said outright that they hadn't measured volume, and that was the number she cared about. She also bristled at the idea that carriers inventing their own field names was the real problem, since her company's names had grown up for reasons. Still, the author called their own bundle an example of the same problem, "which is uncomfortable to say about my own file", and it was hard to stay annoyed at someone who said that first.
She didn't forward it to her director or draft a proposal. She opened the intake template her team used, the one with free-text boxes she'd stopped noticing, and counted how many fields a clerk could fill in that the clerk shouldn't be able to. She found two. She typed them into a note to bring up at Thursday's standup, and then finished her cold coffee.