
IntelliRAG
Answers need receipts. Trace the passage, test the claim, and refuse when the docs fall short.
- PINNED SOURCE EVIDENCE
- 20 SUPPORT SCENARIOS
- 54 RAG CHECKS
- PUBLISHED FAILURES
Pick a star for the whole story, or click the central Tetris piece for GitHub. The full galaxy connects every chapter.
EXPLORE THE FULL GALAXY ↗Ask a better question.
Analyst at MiQ, ex-Flipkart - I build RAG, memory and eval systems.
A September-only replay of public merged PRs, ending with the month at a glance.
Checking current public GitHub activity...
Choose a piece. Follow the decisions down to the work.
An answer you can trust. A pattern worth following. Something that feels easier to use. Choose what you came looking for.
Line width highlights the main story, not a performance score. Every connection is curated from the work.
Start with the systems I am building now. Follow the code, try the live work, then explore the rest.

Answers need receipts. Trace the passage, test the claim, and refuse when the docs fall short.

Six memory blocks. Every useful line stays linked to its source.

Forecasts meet rooftop truth. Bias checks and a leaderboard show what holds up.

A shared board for the messy middle: drag, decide, move.

Agent research with a visible confidence check, not a mystery verdict.

Drone footage into blackbuck detections. Computer vision with a field job.

Generate the shape and its label together. 1,000+ bolts ready for CAD ML.
Analytics taught me to look for the signal. Building makes me test whether I understood it. Here’s the loop I’m trying to get better at.
You press Enter and an answer appears. I spent months on what happens in between. Stretched out, those two seconds are exactly one Tetris line: ten cells, and the model only turns up for the last five.
Before anything can be remembered or retrieved, one question has to be answered. The login screen you scroll past is solving the hardest problem on the internet, and it isn't intelligence. It's identity.
Three invisible systems, then the model. Half the wait is the part everyone credits; the other half is the part that makes it possible.
The board keeps growing. Explore the daily stack, language pieces, and the next repositories in the queue.
I really love designing systems that love me back :)
“Most tutorials show you how to call an API. I want to understand how to build the infrastructure that makes AI work reliably at scale.”
I care about correctness over convenience, documented tradeoffs over hand-waving, and systems that fail gracefully when things go wrong.
A systematic look at prompting strategies for scientific event extraction — what general-purpose models can (and cannot) pull from experimental procedures.
READ ON ARXIV ↗Working across MENA markets.
OPEN RESUME ↗Seller funnel analytics on the search personalization team. Pipelines and dashboards turning behavior into product decisions across millions of daily searches.
OPEN RESUME ↗Production-grade systems from first principles: RAG, multi-agent AI, computer vision, quantitative finance. Documented tradeoffs, measured failure modes.
OPEN RESUME ↗1 CREDIT IN THE TRAY
Product analytics, AI systems, or any technically interesting problem. Usually reply within 24 hours.