Obsidian Metadata
| type | concept |
| sources | Source - AI Evals FAQ |
Minimum Viable Eval Setup
Start with Error Analysis, not infrastructure.
- Spend 30 minutes manually reviewing 20–50 LLM outputs whenever you make significant changes.
- Use one domain expert who understands your users as the quality decision-maker (a Benevolent Dictator).
- Use a notebook to review traces and analyze data, or have an AI coding assistant (Claude, Codex) build a small custom annotation interface. Either way you can write arbitrary code, visualize data, and iterate quickly (see the video “Build Your Own Eval Tools With Notebooks!” in Video Library).
- Log Traces so there’s something to review.
- Add cheap assertions for obvious objective failures.
- Hold off on LLM judges, dashboards, and vendor platforms until error analysis tells you what matters.
Next steps: follow the Eval Playbook.

