Document Review with Unsiloed and TypeSafe Jev
ritzaco
46 points
7 comments
October 13, 2026
Related Discussions
Found 5 related stories in 94.7ms across 9,386 title embeddings via pgvector HNSW
- Show HN: Jeff – A read-only CLI for semantic code review using Jev imalessandro · 20 pts · September 18, 2026 · 58% similar
- Jev vs. Kev: open-source Jev alternative tested side by side felix089 · 12 pts · September 25, 2026 · 56% similar
- Introducing System One Models and Jev albelfio · 1080 pts · September 15, 2026 · 56% similar
- Show HN: jevals – replacing LLM judges with typed Jev decisions gbayomi · 15 pts · September 20, 2026 · 55% similar
- Jev in practice: typed decisions, scoped authority niyikiza · 28 pts · September 23, 2026 · 54% similar
Discussion Highlights (3 comments)
armcat
They use the OCR + structured data extraction in this example, but I'm thinking you could extrapolate this to any scenario where you are extracting some data (from a table, markdown file, OCRed doc), and then use a decision model to perform a fast on-the-fly review/validation.
rohansood15
Jev is cool, but this example is really bad. The example flags a '10 tablets' dose as a possible erroneous extraction, when the text says exactly that. So it is a false positive. Furthermore, even if your goal was to catch logical errors rather than extraction errors, you are better off using programmatic checks on the extracted value and having a dedicated error handling path including additional full LLM calls, rather than decision model.
rohankhameshra
I agree that Jev is pretty cool but example is pretty bad, there is lot more that can be done with it, particularly in unstructured data processing pipeline. One big problem I see is just figuring out if there is new training point is to be found in the data, because with stream of data coming in its waste of resource to process everything