Video yükleniyor...
Video Yüklenemedi
introducing Jevbox: an open-source document drive that organizes itself, answers questions, and cites everything (all powered by Jev). TLDR; - upload anything and Jev categorizes and files it into the folder tree - search is hierarchical: Jev picks the folder, then the document, then the section. No embeddings, no... show more
173,895 görüntüleme • 4 gün önce •via X (Twitter)
31 Yorum

open source repo here:

where can i try this?

Cool. Jev is solving retrieval problems

if you squint, everything is a classification problem

gh repo?

here you go:

Insane

@andrewlu0 is insane

@ameyaajoshi the use cases with extend + jev are crazy

cool

this is cool, organizing folders is a pet peeve of mine. I really don't enjoy it. Notion could use a similar approach honestly. Cool use case for Jev, I have been building a tool router for machine payments with Jev it's quite interesting. Will launch soon too.

no vector db is the real flex here, cant wait to stress test the hierarchy

@theo I recall you doing something about file organisation and files not needing to be at one exact path. This seems like the most natural evolution of that ideao.

I’d use GLiDE for the folder → document → section choices. It beats Jev on Decision Index retrieval, 60.9 vs 55.4, and can reason further when two paths look plausible. That’s worth testing on the same document library.

The filing is the easy half. What actually breaks document search in a real company is that the drive holds three versions of the same policy and nothing marks which one is current. A citation only helps if somebody decided that page was still true.

Looks interesting

Is this a different kind of vector database? What’s the benefit over graphrag?

Retrieval-time permission checks are the part most RAG stacks get wrong, cached chunks serve after access is revoked. The failure I would eval first is miscategorization, a misfiled doc goes invisible to hierarchical search. AI engineer working on agent harnesses and evals.

people here are doing crazy things!

what problem does this solve? Is this advantageous to a local wiki style knowledgebase with vector database?

Super slick UI, but needing paid SaaS endpoints for search & parsing hurts. Wish it had native fallbacks for fast, non-autoregressive System 1 models like Laya for scoring/ranking + local OCR for files. A completely free, offline Jevbox stack would be amazing.

No vector DB is such a refreshing design, I’ll go check out the repo later.

What size library have you tested this on so far? Curious how many Jev calls a question spanning several folders needs.

The useful detail is that Jevbox checks permissions at retrieval, so losing access to a source also removes access to answers built from it.

this is amazing Great work!

@typesafeai built using the hierarchical classification cookbook ✍️

hierarchical classification is the sweet spot for auto‑organizing docs

I built this for HTML internally _yesterday_

Does it ever reshuffle the folder tree after you've already learned where things live?

文档自己会归类 提问还能带出处 这活以前得专人干

Sounds expensive, how much does it cost to run it all?
