github-starred/awesome-llm-apps
2
0
Fork 0
mirror of https://github.com/Shubhamsaboo/awesome-llm-apps.git synced 2026-07-17 08:22:34 -05:00
Code Issues 136 Packages Projects Releases Wiki Activity

[GH-ISSUE #865] Add VORTEXRAG — 7-Layer RAG with Semantic Drift + Context Poisoning elimination #14234

New Issue
Closed
opened 2026-07-12 22:16:21 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-07-12 22:16:21 -05:00
Owner
Copy Link

Originally created by @vignesh2027 on GitHub (Jun 7, 2026).
Original GitHub issue: https://github.com/Shubhamsaboo/awesome-llm-apps/issues/865

VORTEXRAG — Open Source RAG Framework

VORTEXRAG is a complete 7-layer RAG framework that solves two fundamental problems:

  1. Semantic Drift — retrieves causally-relevant chunks, not just topically similar ones
  2. Context Window Poisoning — provably-optimal purging of low-signal chunks

Key Results

  • EM: 74.8 (+13.6 vs Naive RAG, +6.4 vs Self-RAG)
  • F1: 82.6 | Faithfulness: 0.94
  • Latency: 185ms (2.2× faster than Self-RAG)
  • 229 unit tests, MIT license, Python 3.10–3.13

Links

Would love to be added to the RAG or LLM apps section!

Originally created by @vignesh2027 on GitHub (Jun 7, 2026). Original GitHub issue: https://github.com/Shubhamsaboo/awesome-llm-apps/issues/865 ## VORTEXRAG — Open Source RAG Framework VORTEXRAG is a complete 7-layer RAG framework that solves two fundamental problems: 1. **Semantic Drift** — retrieves causally-relevant chunks, not just topically similar ones 2. **Context Window Poisoning** — provably-optimal purging of low-signal chunks ### Key Results - EM: **74.8** (+13.6 vs Naive RAG, +6.4 vs Self-RAG) - F1: **82.6** | Faithfulness: **0.94** - Latency: **185ms** (2.2× faster than Self-RAG) - 229 unit tests, MIT license, Python 3.10–3.13 ### Links - **Code:** https://github.com/vignesh2027/VORTEXRAG - **Paper:** https://doi.org/10.5281/zenodo.20579702 - **Demo:** https://huggingface.co/spaces/vigneshwar234/VORTEXRAG Would love to be added to the RAG or LLM apps section!
GiteaMirror commented 2026-07-12 22:16:22 -05:00
Author
Owner
Copy Link

@harshil-1402 commented on GitHub (Jun 23, 2026):

Could this be assigned to me? I'd like to add VORTEXRAG to the RAG section — the 7-layer pipeline approach (causal-relevance retrieval + provably-optimal context purging) is a useful addition alongside the existing entries.

I'll open a PR shortly with the entry added in the right place, following the repo's existing format.

<!-- gh-comment-id:4776422338 --> @harshil-1402 commented on GitHub (Jun 23, 2026): Could this be assigned to me? I'd like to add VORTEXRAG to the RAG section — the 7-layer pipeline approach (causal-relevance retrieval + provably-optimal context purging) is a useful addition alongside the existing entries. I'll open a PR shortly with the entry added in the right place, following the repo's existing format.
GiteaMirror commented 2026-07-12 22:16:23 -05:00
Author
Owner
Copy Link

@vignesh2027 commented on GitHub (Jun 23, 2026):

Hey @harshil-1402 — yes, please go ahead! Would love to have VORTEXRAG in the RAG section.

A few details that might help you write the entry:

What makes it different from the other RAG entries:

  • 7-layer pipeline (not just retrieve + generate) — each layer has a specific job
  • Layer 3 (SDC) eliminates semantic drift before chunks enter the context window
  • Layer 4 (CPG) purges poisoned/contradictory chunks
  • Layer 7 (FV) verifies faithfulness after generation and regenerates if needed
  • Faithfulness score: 0.94 vs 0.81 (Self-RAG) and 0.71 (Naive RAG)

Links for the entry:

Feel free to ping me here if you need anything else for the PR. Looking forward to it!

<!-- gh-comment-id:4776733412 --> @vignesh2027 commented on GitHub (Jun 23, 2026): Hey @harshil-1402 — yes, please go ahead! Would love to have VORTEXRAG in the RAG section. A few details that might help you write the entry: **What makes it different from the other RAG entries:** - 7-layer pipeline (not just retrieve + generate) — each layer has a specific job - Layer 3 (SDC) eliminates semantic drift before chunks enter the context window - Layer 4 (CPG) purges poisoned/contradictory chunks - Layer 7 (FV) verifies faithfulness after generation and regenerates if needed - Faithfulness score: 0.94 vs 0.81 (Self-RAG) and 0.71 (Naive RAG) **Links for the entry:** - GitHub: https://github.com/vignesh2027/VORTEXRAG - Paper: https://doi.org/10.5281/zenodo.20579702 - Demo: https://huggingface.co/spaces/vigneshwar234/VORTEXRAG Feel free to ping me here if you need anything else for the PR. Looking forward to it!
GiteaMirror commented 2026-07-12 22:16:23 -05:00
Author
Owner
Copy Link

@harshil-1402 commented on GitHub (Jun 23, 2026):

Sure thanks a lot for the info, i'll start right away!

<!-- gh-comment-id:4781621763 --> @harshil-1402 commented on GitHub (Jun 23, 2026): Sure thanks a lot for the info, i'll start right away!
GiteaMirror commented 2026-07-12 22:16:24 -05:00
Author
Owner
Copy Link

@Shubhamsaboo commented on GitHub (Jun 26, 2026):

Thanks for sharing VORTEXRAG, and credit for the open-source release and test coverage. The fit here is the issue: awesome-llm-apps collects self-contained, runnable tutorial apps, not standalone frameworks/libraries, and adding VORTEXRAG would be a README link to an external repo. The published benchmark numbers are also self-reported and not independently verified, so we'd rather not feature them in the list.

Note for anyone planning a PR from this thread: the earlier "go ahead" reply was from the project's own author, not a maintainer, so please don't open a README-link PR expecting it to be merged. Closing as out of scope. Appreciate the work regardless.

Generated by Claude Code

<!-- gh-comment-id:4806935047 --> @Shubhamsaboo commented on GitHub (Jun 26, 2026): Thanks for sharing VORTEXRAG, and credit for the open-source release and test coverage. The fit here is the issue: awesome-llm-apps collects self-contained, runnable tutorial apps, not standalone frameworks/libraries, and adding VORTEXRAG would be a README link to an external repo. The published benchmark numbers are also self-reported and not independently verified, so we'd rather not feature them in the list. Note for anyone planning a PR from this thread: the earlier "go ahead" reply was from the project's own author, not a maintainer, so please don't open a README-link PR expecting it to be merged. Closing as out of scope. Appreciate the work regardless. --- _Generated by [Claude Code](https://claude.ai/code)_
GiteaMirror commented 2026-07-12 22:16:24 -05:00
Author
Owner
Copy Link

@harshil-1402 commented on GitHub (Jun 26, 2026):

may i know the reason for the issue to be closed as "not planned"

<!-- gh-comment-id:4811977655 --> @harshil-1402 commented on GitHub (Jun 26, 2026): may i know the reason for the issue to be closed as "not planned"
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-llm-apps#14234
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?