…
Unified retrievallexical · semantic · metadata · claims · graph
⌕
Enter a query to retrieve cited evidence from the corpus.
idle LISA — Literature Intelligence & Search Architecture · built by github.com/theflyingrahul
drag background to pan · scroll to zoom · drag a node to move it — focal paper in amber
Author–Keyword Co-occurrence bipartite: authors ↔ keywords, weighted by paper count
drag background to pan · scroll to zoom · drag a node to move it — blue: authors, green: keywords
Co-authorship Network papers connected by shared authors, weighted by count
drag background to pan · scroll to zoom · drag a node to move it — click opens paper
Keyword Co-occurrence keywords connected by shared papers, weighted by count
drag background to pan · scroll to zoom · drag a node to move it
Author–Institution Network authors ↔ institutions, weighted by paper count
drag background to pan · scroll to zoom · drag a node to move it — blue: authors, purple: institutions
Corpus map
Corpus overview
Paper
About LISA
⚙ Settings
Unified retrieval
Loading active bundle…
Every search, evidence, and verify request uses this one sealed bundle: lexical, semantic, metadata, claim, and graph signals, followed by exact evidence refinement and one pinned Jina Turbo rerank. There is no model or index selector.
Storage & sources
Bundle lifecycle is operator-managed and atomic: lisa retrieval build, install, activate, rollback, and status.
Accounts
Create user
Users
Active sessions (minted login tokens)
Compare papers
Welcome to LISA

LISA retrieves cited evidence from your own PDF library through one deterministic retriever. It combines lexical, semantic, metadata, claim, and graph signals, recovers exact source passages, and applies one pinned Jina Turbo rerank.

Retrieval models and indexes are sealed into a content-addressed project bundle. There is no engine chooser, so the CLI, HTTP API, MCP server, and Web UI always return results from the same runtime.
Corpus synchronization
Add PDFs to this project
Publish corpus changes
idle 

      
      
Search remains available on the current bundle throughout scanning, incremental preparation, construction, and validation. The active pointer changes only after the replacement passes its smoke checks; cancellation or failure leaves the current bundle untouched. Repeated changes during a run queue one follow-up scan.

    

  





  

    
…

    

      

        

      

        
        
      

    

  





  

    
…

    

      

      

    

  





  

    
System logs