Litmus: Zero-Label, Code-Driven Metric Specification for Evaluating AI Systems

arXiv:2606.23403v2 Announce Type: replace Abstract: As agentic LLM systems move from prototypes to deployment, evaluating them has become more important and more difficult. Evaluation goals are often left implicit. Without a clear account of what a system is expected to do, how it can fail, and which failures matter, metric choices become difficult to justify, interpret, or validate. We present Litmus, a zero-label system that designs evaluation and monitoring metrics for AI pipelines by eliciting evaluation intent from source code and targeted interrogation. Litmus first identifies what must be measured and why, then converts those answers into constraints for a justified, per-stage metric portfolio. We evaluate Litmus on three real, code-defined pipelines against AutoMetrics and three DynamicRubric baselines. Litmus achieves broader concern coverage on account grouping at matched size, spans more stages, produces a near-zero-redundancy portfolio, and, under a zero-label design-time constraint, ranks first in validity against per-row quality labels on all three pipelines, decisively on scientific QA ($\rho{=}0.72$ vs. $0.47$ for the strongest baseline on the stitched single-vector score), with overlapping intervals on the other two. Results support a shift from automatic metric implementation to automatic metric specification: before asking which metric to compute, evaluation systems should ask what must be measured and why.

Abstract:As agentic LLM systems move from prototypes to deployment, evaluating them has become more important and more difficult. Evaluation goals are often left implicit. Without a clear account of what a system is expected to do, how it can fail, and which failures matter, metric choices become difficult to justify, interpret, or validate. We present Litmus, a zero-label system that designs evaluation and monitoring metrics for AI pipelines by eliciting evaluation intent from source code and targeted interrogation. Litmus first identifies what must be measured and why, then converts those answers into constraints for a justified, per-stage metric portfolio. We evaluate Litmus on three real, code-defined pipelines against AutoMetrics and three DynamicRubric baselines. Litmus achieves broader concern coverage on account grouping at matched size, spans more stages, produces a near-zero-redundancy portfolio, and, under a zero-label design-time constraint, ranks first in validity against per-row quality labels on all three pipelines, decisively on scientific QA ($\rho{=}0.72$ vs. $0.47$ for the strongest baseline on the stitched single-vector score), with overlapping intervals on the other two. Results support a shift from automatic metric implementation to automatic metric specification: before asking which metric to compute, evaluation systems should ask what must be measured and why.

25 pages, 4 figures. Accepted at EMNLP 2026 (Industry Track)

Artificial Intelligence (cs.AI)

arXiv:2606.23403 [cs.AI]

(or arXiv:2606.23403v2 [cs.AI] for this version)

https://doi.org/10.48550/arXiv.2606.23403 Focus to learn more arXiv-issued DOI via DataCite

arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website.

Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them.

Have an idea for a project that will add value for arXiv's community? Learn more about arXivLabs.

analiza aiqbench

Litmus: Zero-Label, Code-Driven Metric Specification for Evaluating AI Systems

Subiecte conexe