Skip to main content
← Back to Projects

Case study

ClearSignal — Evaluation-First Fraud Explanation System

Role / statusIndependent project

Date2026

Strongest verified outcomeProduction ML pipeline delivered

ClearSignal fraud-explanation demo showing source evidence, a plain-language explanation, and honesty checks.

01 — Context

Problem

Turns a fraud model's risk score into a plain-language explanation for call-center agents.

02 — Approach

Solution

The workflow below is a visual summary of the documented implementation; it is not a claim of additional system components.

  1. 01

    Built the full pipeline that includes domain pretraining, LoRA fine-tuning (SFT and DPO), and vLLM serving with two hot-swapped adapters, reaching sub-second p95 latency (roughly 4–10× faster than a GPT-4o call) and cutting GPU memory ~47% by sharing one base model.

  2. 02

    Wrote an evaluation harness with automated hallucination checks, adversarial test cases, and an LLM judge that decided whether the model was good enough to ship, using pass/fail criteria fixed in advance so results couldn't be gamed.

  3. 03

    Added a router that keeps easy cases on the local model and escalates hard ones, which cut frontier-model cost about 63%, plus three safety guards that catch missing or malformed inputs before the model can respond.

03 — Engineering judgment

Key decisions

  • Built the full pipeline that includes domain pretraining, LoRA fine-tuning (SFT and DPO), and vLLM serving with two hot-swapped adapters, reaching sub-second p95 latency (roughly 4–10× faster than a GPT-4o call) and cutting GPU memory ~47% by sharing one base model.

  • Wrote an evaluation harness with automated hallucination checks, adversarial test cases, and an LLM judge that decided whether the model was good enough to ship, using pass/fail criteria fixed in advance so results couldn't be gamed.

  • Added a router that keeps easy cases on the local model and escalates hard ones, which cut frontier-model cost about 63%, plus three safety guards that catch missing or malformed inputs before the model can respond.

04 — Evidence

Results

This project record verifies the delivered implementation, but does not report a comparable performance metric.

Product & System Views

ClearSignal demo showing a safety escalation after the input evidence is deliberately removed.
When evidence is missing, the system escalates rather than guessing.

Continue exploring

See another case study or learn more about my background.

Supporting technology
Qwen2.5LoRASFTDPOvLLMcontinued pretrainingfine-tuningLLM evaluationLLM-judgeadversarial testingmodel servingStreamlitFastAPIDocker