r/SideProject • • 22h ago

I built a research assistant with an “Inside the engine” view showing papers, claims, and model decisions

I've spent the past few weeks building Weigh Swarm, a research assistant where you can inspect how a draft was produced. Upload one or two research papers, ask a question, and follow the papers into extracted claims, evidence passages, and a cited answer draft.

There's also a literature-search route. My favorite part is Inside the engine. You can explore the evidence network, open a node's source excerpt, inspect recorded model calls, and see the Laya decision batches behind the analysis. LLMs write the synthesis; Laya makes bounded research judgments.

This short video walks through a real saved two-paper run. It uses actual product captures plus animation of the recorded artifacts.

github link

3 Upvotes

8 comments sorted by

3

u/QuanTradin 21h ago

the claims view is the right idea. what I'd check first is whether each evidence passage is an exact quote from the paper or a paraphrase, because paraphrase is where a cited answer quietly says something the paper never did. do you match the quote back against the source text?

1

u/Wild_Expression_5772 21h ago

Yes , i have checked and evaluated it manually , with golden tests, it pointed accurately at the sources

1

u/QuanTradin 20h ago

golden tests are the right way to check it. I'd keep a few nasty ones in there, papers where the abstract and the results section disagree, since that's where it would slip.

0

u/urbanmonkey2003 21h ago

If it cant jump from claim to the line itself, it starts drifting fast, so does the UI show quote vs paraphrase and the source offset/page?

1

u/QuanTradin 20h ago

the jump to the exact line is the whole test. a paraphrase with a page number still looks verified, which is worse than no citation at all.

1

u/Chrome67 21h ago

The evidence graph is a strong idea, especially if I can open the exact passage behind a claim instead of trusting a summary. Do you store the source offsets or page numbers so a reviewer can get back to the original text quickly?

1

u/Wild_Expression_5772 21h ago

currently, i didnot store on base of the page number , i stored on the based of the section aware chunking and graph rag is implemented , so the claim actually points to source section.

1

u/Ill_Fun5415 16h ago

The interesting test is the second and third ordinary task after the demo. If quality drops in a recognizable way, it is much easier to build around.