BEHIND THE CURTAIN

THE JUDICIAL ENGINE

1

RAG KNOWLEDGE INGESTION

Process

User text and uploaded PDF whitepapers are processed through a chunking pipeline. Documents are split into overlapping segments of 512 tokens, each converted into dense vector embeddings using the all-MiniLM-L6-v2 sentence transformer model.


These embeddings are stored in a ChromaDB vector database with cosine similarity indexing, enabling sub-millisecond nearest-neighbor search across the entire knowledge base.

INGESTION PIPELINE

User Input → PDF Parser → Text Chunker
↓
Sentence Transformer (MiniLM-L6-v2)
↓
384-dim Vector Embeddings
↓
ChromaDB (Cosine Similarity Index)
Embedding Model all-MiniLM-L6-v2
Vector DB ChromaDB (DuckDB+Parquet)
PDF Parser PyPDF2
Chunk Size 512 tokens, 50 overlap
▼
2

SCIENTIFIC GROUNDING

Cross-Reference Protocol

The system performs real-time queries against three major scientific databases: arXiv (physics, CS, math), PubMed (biomedical), and Semantic Scholar (cross-domain with citation data).


Results are deduplicated, embedded, and similarity-ranked against the user's pitch. The top-k=5 most relevant papers are extracted and injected into the LLM context as evidence for scientific validation.

RETRIEVAL SOURCES

arXiv API → XML Parse → Filter
PubMed API → E-Utilities → XML Parse
Semantic Scholar → REST API → JSON
↓
Deduplication + Re-ranking
↓
Top-5 Papers → Context Injection
arXiv Export API (XML)
PubMed E-Utilities (JSON+XML)
Semantic Scholar Graph API v1 (JSON)
Concurrency asyncio.gather (parallel)
▼
3

MARKET STRESS-TESTING

Analysis Methodology

The system constructs market context by querying the vector database with business-oriented queries derived from the user's pitch. It evaluates unit economics, CAC/LTV ratios, and competitive moats.


Market data is sourced from Y-Combinator deal structures, Gartner reports, and CB Insights market analysis. The RAG pipeline retrieves the most contextually relevant market benchmarks to ground the evaluation.

MARKET ANALYSIS

User Pitch → Query Generation
↓
Vector DB Search (market_reports)
↓
CAC/LTV Analysis
Competitive Moat Assessment
Market Size Validation
↓
Top-3 Reports → Context Injection
Query Types Market Analysis, Business Model, Competition
Metrics CAC, LTV, TAM, SAM, SOM
Sources Y-Combinator, Gartner, CB Insights
▼
4

GROQ API & LPU ACCELERATION

Technical Overview

THE VERDICT leverages Groq's custom LPU (Language Processing Unit) architecture for ultra-low latency inference. Unlike traditional GPU-based inference, Groq's deterministic single-core execution model eliminates memory bottlenecks and delivers consistent sub-second response times.


The primary model deepseek-r1-distill-llama-70b provides deep reasoning capabilities for complex analytical evaluation, while fallback models (llama-3.3-70b-versatile, mixtral-8x7b-32768) ensure system resilience.

GROQ INFERENCE

System Prompt + Context
↓
Groq API (openai/v1/chat/completions)
↓
LPU Hardware Acceleration
↓
JSON Response (Score + Critique)

MODELS:
Primary: deepseek-r1-distill-llama-70b
Fallback: llama-3.3-70b-versatile
Fallback: mixtral-8x7b-32768
API Provider Groq (api.groq.com)
Primary Model deepseek-r1-distill-llama-70b
Response Format JSON (structured output)
Hardware Groq LPU (custom silicon)
Latency Sub-second inference
SYSTEM ARCHITECTURE
┌─────────────────────────────────────────────────────────┐ │ THE VERDICT │ │ AI RAG PROJECT JUDGE │ ├─────────────────────────────────────────────────────────┤ │ │ │ [Frontend] ←→ [FastAPI Backend] ←→ [Groq API] │ │ │ │ │ │ │ │ │ │ │ │ │ │ ▼ ▼ ▼ ▼ │ │ HTML/CSS/JS ChromaDB Research LPU Engine │ │ VectorDB APIs │ │ │ │ │ ┌────────┴────────┐ │ │ │ arXiv │ │ │ │ PubMed │ │ │ │ Semantic Scholar│ │ │ └─────────────────┘ │ └─────────────────────────────────────────────────────────┘