Skip to content

Welcome to the

0

Labs experiment

Evals and tracing: every agent run traced, scored and compared before it ships

An evaluation and tracing setup that treats agent quality like a test suite. Every run is traced step by step, answers are scored by an LLM judge against a rubric, saved cases are replayed before each release and the cost of every run is tracked.

Where this pattern fits

  • Agents that have to stay reliable while prompts and models change
  • Choosing between models or prompts with data instead of guesses
  • Release processes that should block regressions
  • LangSmith
  • Langfuse
  • Python
  • Pytest

How it works

Agent runTracerSpan captureLLM judgeRegression suiteCost monitorDatasetsDashboardsAlerts

Select any node to see what it does.

Simulated run
  1. 00.00cieval suite started on 120 cases
  2. 02.14judgeaccuracy 0.93, 4 regressions found
  3. 02.30costmedian run cost down 18 percent
  4. 02.41cirelease blocked until regressions are fixed

The architecture, step by step

Each part of the diagram, in the order a run moves through it.

  1. Agent runWhere every run starts.
  2. TracerCaptures every step of every agent run.
  3. Span captureRecords each call with its inputs, outputs and timing.
  4. LLM judgeScores answers against a rubric.
  5. Regression suiteReplays saved cases before each release.
  6. Cost monitorTracks tokens and cost per run.
  7. ToolsThe agents act through the datasets, dashboards and alerts.

How it is built

The design choices that make the pattern hold up with real users.

visitor@azan-portfolio: ~

_ ___ ___ _____

/_\ ____ __ _ _ _ / __| _ \_ _|

/ _ \ |_ / / _` || ' \ | (_ | _/ | |

/_/ \_\/__| \__,_||_||_| \___|_| |_|

Hi, I am AzanGPT. Ask me about Azan's work, stack, services or how to reach him.

Type 'help' for commands, or ask a question. Tab completes, the arrow keys walk your history.

AzanGPT runs on an AI model that knows this site. It can get things wrong, so check anything important with Azan.