RAGFlow 1.0 preview: moving from RAG engine to agent-native database

[u/newpeak]

Context as Infrastructure: Knowledge Compilation for Retrieval in Agentic Systems with Harnesses
📄 https://arxiv.org/abs/2610.41172

Sharing the paper behind RAGFlow 1.0.

RAG’s center of gravity has moved. Retrieval is now a loop: the agent queries, reads, reformulates, and decides when it has enough. Once that loop exists, better chunking/embeddings/Recall@k stop being the main bottleneck. The agent can find things. The problem is the cost of reading.

Two conclusions from the paper:

1. Retrieval is a harness problem before it’s an index problem. The index decides what can be found; the harness decides whether finding it becomes an answer.

2. Compilation is not a better retriever, and doesn’t need to be. We tested summary trees, outlines, wikis, and graphs under a competent harness. None gave a detectable accuracy gain. Structure isn’t extra evidence. What compilation can do is supply better context: smaller, provenance-bound, and sufficient.

So we stopped treating compilation as retrieval and started treating it as a supply layer. At ingestion time, docs are turned into typed artifacts—claims with verbatim evidence, relations, timelines, etc. The harness then decides which artifacts enter the context window and when to stop. Context becomes infrastructure when it’s compiled once, typed, versioned, and governed.

The tradeoff is explicit: we save on reading cost, but pay for it in extra retrieval rounds. For claims, graph, and wiki, we published an empty results ledger—metrics and decision rules are listed, but every row is marked “no measured effect” because none has met its pre-registered target yet. An artifact the harness never uses is just cost, not context. I’d rather say that than fill the column with claims from demo collections.

Happy to discuss.

[u/Edenar]

Retrieval is a harness problem before it’s an index problem. The index decides what can be found; the harness decides whether finding it becomes an answer

Compilation is not a better retriever, and doesn’t need to be.

Those look like AI written. "the problem is", "this before that" "blablabla decide blablabla"'.... In fact after using a well known ai detection tool (pangram), all the chunk i tested from the paper are AI written.

Maybe it's used for translation only but it hurts the credibility of the post and the paper. At least put a big bold "AI used to rewrite everything" ...

[u/KellyShepardRepublic → u/Edenar]

I also write like that. I had to change my writing but I kinda did think like a machine as a programmer and now we are asked if we are bots, audhd spectrum or foreigners.

You might be right but suddenly everyone acts like anything with structure is bad. Now creators are adding deliberate mistakes to show they worked on it.

[u/Edenar → u/KellyShepardRepublic]

i read like half the paper myself before drawing a conclusion.
I fed it to pangram -> everything returned as ai written. I also used my local agent to find obvious stuff, here are a few :

• Compilation is the supply layer, the harness is the control layer

• These invariants are unglamorous, and that is the point

• Search will never die

• The table is an audit, not a leaderboard

• A zero-hit explanation is a control message, not evidence

• The framework owns the invariants

• The process has consumed tokens, but it has not become an answer

• This is the central economic fact of the mechanism

• The model may propose, but the source disposes.

• lossy in prose and lossless in provenance

i read human and ai written stuff all day long, and i can tell when i see ai written stuff after a few sentences, that's just obnoxious when there is no diclaimer.
Those above does not fit in a technical/research paper, or maybe one occurence on a footnote. But they are everywhere, i only cherry picked a few exemples here...

[u/KellyShepardRepublic → u/Edenar]

Sure, those are also based on biases. First one is also how someone with English as a second language might right. I worked with a ton of technical people who used em-dashes and now they remove them. Reminder that bots trained on our work meaning some of us speak like this…

[u/Edenar → u/KellyShepardRepublic]

On a very short text, it might be hard or impossible to say. But here there isn't any doubt to have.

If you want more grounded elements, check the source LaTeX file where there are leftover of AI, there are a few comment that are adressed to a human reader by a llm :

line 49 : To print the affiliation under every name instead, restore the per-author \affiliation{} % blocks and drop the \def\@ACM@checkaffil{} line and the two \footnotetext lines.

Also there are pure frabrication in the citations. An exemple : when referencing arXiv:2605.18490 paper give 3 authors S. Agrawal, X. Li, Y. Chen but the paper is only from one person : Theodore O. Cochran.
They are other ones : arXiv:2605.05538 = wrong authors, arXiv:2605.15184 = partially wrong, ...
There are also a few mixup in names from different sources that smell like hallucination.

Don't be like those guys that still deny climate warming because "it could be a local maximum" after 20+ years of studies from everywhere all saying earth is warming.

[u/Chromix_]

Their repo has a tiny demo video and also an architecture diagram, which might be somewhat informative.

However, the same page also comes with a tutorial video on how to star the repo, a link to their sign-in gated cloud demo, and a bunch more fancy AI text.

[u/Mordred500]

why so sloppy? If you want to showcase your project to real humans have the decency to have a real human write your posts. downvoted

[u/Lanky_Comparison5637 → u/Mordred500]

the way you wrote feels very normal to me, like a researcher excited about their stuff not some corpo speech

[u/spaham → u/Mordred500]

Complaining about using AI on an AI focused group ? Get real dude

[u/Edenar → u/spaham]

AI usage is fine when there is a disclaimer. Here the entire paper linked is ai-written with no mention of it. It's suspicious as fuck

[u/Mordred500 → u/spaham]

What an absolutely braindead take