## TL;DR

If your Patronus evaluations run but you cannot see what the app actually did, you forgot @traced(). The trace and the evaluation then land together in the platform, which is what makes a failing eval debuggable instead of just a red number.

## Steps

1. If your Patronus evaluations run but you cannot see what the app actually did, you forgot @traced(). Wrap the functions being evaluated with the @traced() decorator so Patronus captures inputs, outputs, timing and call structure; pair it with an @evaluator() function that returns a bool or score for the result. The trace and the evaluation then land together in the platform, which is what makes a failing eval debuggable instead of just a red number.

## When to use

You are seeing this: Wrap the functions being evaluated with the @traced() decorator so Patronus captures inputs, outputs, timing and call structure; pair it with an @evaluator() function that returns a bool or score for the result. Use this skill when you run into "Patronus: wrap evaluated functions with @traced() or failures are undebuggable".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
