Independent engineering case study

Norrelium Research

An evidence-first AI research environment that turns current web information into inspectable answers, multi-pass reports, comparisons and source analyses—while keeping claims linked to supporting material.

AI knowledge systems · Production-minded reference implementation

Norrelium Research application overview with four research modes, a research question and inspectable evidence preview
AUTHENTIC PRODUCT INTERFACEOpen live application

PRODUCT DEMONSTRATION

See the complete research workflow.

This 2 minute 21 second product demonstration follows Quick Answer, Deep Research, Compare, Source Analysis and the reusable research workspace.

01 / EVIDENCE

The problem

Conventional search leaves people to verify and synthesize a list of links. Fluent AI answers remove that work, but can become difficult to challenge when source selection, citation coverage and evidence quality remain hidden.

02 / EVIDENCE

Four research modes

The same evidence-first workflow adapts to different research tasks instead of forcing every question through one generic answer format.

Quick Answer

Focused questions return a concise source-grounded answer with numbered citations, ranked source cards and suggested follow-ups.

Deep Research

Complex questions are broken into research areas, investigated across multiple passes and synthesized into a structured cited report.

Compare

Two alternatives are evaluated against the same question, keeping key differences, trade-offs, conclusions and supporting sources together.

Source Analysis

A submitted publication is summarized, decomposed into claims and examined through visible evidence and independent checks.

03 / EVIDENCE

Evidence users can inspect

Citation markers connect claims to ranked source cards containing the publisher, retrieval date, extraction status and evidence excerpt. Coverage and alignment signals make incomplete support visible, while clearly stating that automated checks do not establish factual truth.

  • Inline claim-to-source citation markers
  • Ranked source cards with retrieval metadata
  • Mechanical citation coverage and alignment signals
  • Visible limited-evidence states and honest caveats

04 / EVIDENCE

Research that remains reusable

Completed work is not discarded after the first answer. Users can continue a question, export or save a result, revisit session history and organize useful findings into named collections.

  • Contextual follow-up questions
  • Export and save controls
  • Persistent anonymous-session history
  • Named collections and permanent workspace deletion

05 / EVIDENCE

System architecture

A Next.js application on Vercel proxies requests to a FastAPI service on Railway. LangGraph coordinates search, extraction, ranking and synthesis; external retrieval comes from Serper or Brave Search, OpenAI produces cited synthesis, Upstash Redis supports caching and rate limiting, and Supabase PostgreSQL stores research state.

  • Browser → Next.js server-side proxy → FastAPI
  • LangGraph research orchestration
  • Serper or Brave Search retrieval
  • OpenAI GPT-4.1-mini cited synthesis
  • Upstash Redis caching and rate limiting
  • Supabase PostgreSQL persistence
  • NDJSON status, progress and final-result streaming

06 / EVIDENCE

Evaluation and production controls

The evidence snapshot was validated on 13 August 2026. Automated gates covered API contracts, anonymous-session isolation, persistence, citation mechanics, workspace behaviour, security controls and production build integrity.

310 backend tests passed

API contracts, isolation, persistence, retrieval hardening, workspace controls, retries, security, observability and rate limiting.

6 of 6 citation evaluations passed

Deterministic checks for rank binding, invalid markers, duplicate accounting and declared-versus-visible citation coverage.

7 frontend contract suites passed

Saved results, citation integrity, Compare follow-up, research metadata, Source Analysis and workspace behaviour.

Release gates passed

Frontend lint, TypeScript checking, production build and deployed production smoke testing completed successfully.

07 / EVIDENCE

Trust boundaries

The browser never receives provider or database credentials. A signed HttpOnly anonymous-session token establishes workspace authority; the backend ignores client-supplied project identifiers, keeps service credentials server-side and validates external URLs and redirects before extraction.

  • Server-side credential boundary
  • Signed anonymous-workspace authority
  • Schema-qualified persistence
  • Input, URL and redirect validation
  • Session-scoped rate limiting
  • Structured logs and persisted research traces

08 / EVIDENCE

Known limitations

This is a tested independent engineering case study, not evidence of commercial adoption or an enterprise service-level guarantee. Generated answers can still be incomplete or wrong, external providers affect freshness and availability, and citation checks verify mechanics rather than semantic entailment or factual truth.

  • Anonymous workspaces are browser-cookie scoped
  • No cross-device accounts or organization tenancy
  • No public operational metrics endpoint
  • Source Analysis does not independently verify every claim
  • Enterprise use would additionally require SLOs, load testing, formal retention, incident response and a larger human-reviewed evaluation set

09 / EVIDENCE

What this demonstrates

End-to-end AI knowledge-system engineering: a multi-mode research product, visible evidence, persistent workflows, evaluation gates, security boundaries and honest limitations brought together in one production-minded implementation.

Next step

Discuss a similar challenge.

Start with the business context, desired outcome and current constraints. We will establish whether Norrelium is a sensible fit.