Skip to main content

​
How It Works

Quorum evaluates each test case with a strategy chosen by risk, not with a one-size-fits-all pipeline.

​
Adaptive routing

Every test case is scored for risk first. That score determines which evaluation path runs next.

​
Strategy breakdown

​
Council mode

  • Best for high-stakes cases such as medical, legal, or financial content
  • Runs OpenAI, Anthropic, and Gemini judges in parallel
  • Uses an aggregator to synthesize the final verdict

​
Hybrid mode

  • Best for medium-risk technical or advisory content
  • Runs deterministic checks such as similarity, entity matching, freshness, and completeness
  • Adds one LLM judge and computes the verdict locally

​
Single mode

  • Best for low-risk factoid-style queries
  • Runs one judge only for the lowest-cost path

​
Streaming lifecycle

Quorum exposes the evaluation lifecycle as SSE events so the UI can render every stage live. Typical flow:
The frontend uses those events to render only the components relevant to the selected strategy.

​
System shape

  • Frontend: uploads, strategy selection, live streaming, history, cost views
  • Backend: routing, orchestration, deterministic checks, aggregation, persistence
  • Integrations: webhooks plus SDK capture/ingest workflows

​
Authentication

All app endpoints require a valid session cookie obtained via /api/auth/login. The session is an HttpOnly cookie valid for 7 days.

​
Current API surface

For runtime tracing and auditing details, continue to Observability.