frequency_penalty Broke My JSON: 47 of 88 Long Invoices Lost Items
This story is from 2026-10-29. It is preserved in the archive; the latest stories are on the live feed.
The invoice had 34 line items. The JSON my extractor returned had 19. It parsed. It passed schema validation. Nobody noticed for two weeks. The cause was one line in a shared client config: frequency_penalty=0.3 . I had added it to stop a summarizer from looping. It was also quietly applied to my i…
Read the full story at DEV Community — Machine Learning ↗
Timeline · 1 report
- 2026-10-29 00:02 · DEV Community — Machine Learning
frequency_penalty Broke My JSON: 47 of 88 Long Invoices Lost Items