Do you need to file a feature request?
Feature Request Description
I’m currently using LightRAG for a regulatory/legal RAG system with RBI regulations and amendment documents, and I’m facing an issue with amendment handling during retrieval. Since original regulations and amendment documents are treated as independent semantic chunks, retrieval often returns both outdated clauses and newer amended clauses together, causing the LLM to generate blended or conflicting answers instead of prioritizing the amendment as the authoritative/latest version. In some cases, the amendment document does not get retrieved at all because the original regulation has stronger semantic weight, denser graph relationships, and more connections across the knowledge base, so LightRAG tends to rank the older chunk higher. For example, if an original regulation states “180 days” and a later amendment changes it to “270 days,” the system may still retrieve or prioritize the outdated clause. This seems to expose a broader issue in amendment-heavy legal corpora where semantic similarity alone is not enough, and there may be a need for priority-based or authority-aware retrieval that can account for supersession, temporal validity, and amendment precedence.
Additional Context
No response
Do you need to file a feature request?
Feature Request Description
I’m currently using LightRAG for a regulatory/legal RAG system with RBI regulations and amendment documents, and I’m facing an issue with amendment handling during retrieval. Since original regulations and amendment documents are treated as independent semantic chunks, retrieval often returns both outdated clauses and newer amended clauses together, causing the LLM to generate blended or conflicting answers instead of prioritizing the amendment as the authoritative/latest version. In some cases, the amendment document does not get retrieved at all because the original regulation has stronger semantic weight, denser graph relationships, and more connections across the knowledge base, so LightRAG tends to rank the older chunk higher. For example, if an original regulation states “180 days” and a later amendment changes it to “270 days,” the system may still retrieve or prioritize the outdated clause. This seems to expose a broader issue in amendment-heavy legal corpora where semantic similarity alone is not enough, and there may be a need for priority-based or authority-aware retrieval that can account for supersession, temporal validity, and amendment precedence.
Additional Context
No response