As LLMs are increasingly deployed in high-stakes professional workflows, engineers and researchers require principled protocols to systematically track, monitor, and improve model performance across deployment cycles. We present a mathematical framework for iterative LLM evaluation and deployment, and demonstrate its application to AI systems used in criminal justice. Our framework formalizes LLM integration in high-stakes, high-risk, and resource-constrained domains across model selection, rubric design, evaluations and deployment via a weighted multi-objective optimization. We demonstrate that MERCI Cards can guide improvements of the system across deployment iterations, direct developer attention toward under-performing areas, and focus user attention on validation and error-correction in the LLM's outputs.
Whether context is supplied, and whether it is withheld during selection
C
C
Candidate model set
M
D
Table 2. Choices the framework leaves to the deploying team. The framework requires that each be recorded on the MERCI card with its rationale; it does not prescribe the value.
Figure 1. Framework pipeline. The expert configures the task, rubric, and generation model, evaluation is set up, the task is run and scored, and a release decision is made. The quality vector Q returns to the configuration stage.
Section
Field
Kind
Identity
System name, domain, iteration τ
record
Card version, date issued, prior card reference ( τ−1 )
record
Deploying team and accountable contact
record
Task
T : task description and what a task result is (e.g., answer, report, summary, drafted document)
record
N : number of inputs the task was run on; how they were selected
record
Scoring granularity per dimension: continuous, discrete, or categorical, with the mapping onto [0,1]
choice
Table 3. MERCI Card specification. One card per iteration τ . choice fields are decisions the deploying team makes: record the value and the reasoning. derived fields are computed from the run. record fields are factual. optional fields improve the card without being necessary to interpret the iteration.
Dimension
Tests whether the report
OR CI score
contextualizes odds ratios with CI width and whether the interval spans 1
RR CI score
does the same for relative risk
OR Smp score
contextualizes odds ratios with sample size
RR Smp score
does the same for relative risk
χ2 Smp score
does the same for chi-square
p score
contextualizes p -values against the significance threshold
Table 4. Examples of evaluation rubric dimensions
Generation model
Judge
F(G)
native
ρ
F(J)
ρ
Jd
S^m
t (s)
c ($)
Opus
none
0
GPT
3
0.92
11.60
40
0.06
Opus
adapt / med
2
GPT
3
0.92
10.92
53
0.08
Opus
adapt / high
3
GPT
3
0.92
11.94
55
0.08
Opus
adapt / max
4
GPT
3
0.91
10.31
96
0.16
Sonnet
adapt / high
3
GPT
3
0.90
9.91
180
0.21
Table 5. Model selection sweep: ∣M∣=11 configurations over N=18 reports and ℓ=15 judge runs. Native settings appear with the normalized reasoning level ρ the team declared for them. Jd is the mean judge score across the nine dimensions; S^m is the composite including cost and latency ( wCmp=5 , wd=1 otherwise, wc=wt=1 ). Sorted by Jd . Highlighted row is the selected G .
Judge
Human
Δ from τ=0
Dimension
Jd
sd
Hd
sd
ΔJd
ΔHd
OR CI score
0.94
0.03
0.89
0.16
+ 0.15
+ 0.09
OR Smp score
1.00
0.00
0.80
0.13
+ 0.51
+ 0.19
RR CI score
0.86
0.04
0.87
0.18
+ 0.10
+ 0.07
RR Smp score
1.00
0.00
0.80
0.13
+ 0.51
+ 0.19
Cmp score
0.74
0.01
0.76
0.35
+ 0.05
− 0.02
Table 6. Scores per rubric dimension at τ=1 ( N=30 , ℓ=15 , V=3 ), with the change from the prior iteration. Judge sd is the mean standard deviation across the ℓ runs per report; human sd is the inter-reviewer standard deviation.
Section
Field
Entry
Identity
Prior card
τ=0
N inputs
30 reports; 18 in the selection sweep
Task
Granularity
any value in the range [0,1]
agg
Qd=21(Jd+Hd) for deployment evaluation, i.e. both humans and LLM judges are used; Qd=Jd for model selection, i.e. no humans are used
In recent years, large language models (LLMs) have emerged as a popular alternative for evaluation. Often referred to as LLMs as judges (LLJs), these systems have been widely adopted by researchers and practitioners across a broad range of measurement tasks, driven by their strong performance, scalability, and cost-effectiveness relative to human judgment. However, a growing body of work has shown that the use of LLJs raise concerns about their validity and reliability as evaluators. Existing efforts to address these challenges have largely focused on developing bias-mitigation techniques and refining prompting strategies. While these approaches represent an important step forward, they primarily offer technical fixes and leave a more fundamental challenge unaddressed: the lack of standardized, transparent, and reproducible evaluation practices. In this paper, we introduce LLJ Cards, a framework that synthesizes best practices from measurement theory, natural language generation, and machine learning literature into practical guidelines for LLJ-based evaluations. While LLJs offer a promising path toward scalable evaluation, their effective use requires grounding in rigorous evaluation principles to ensure validity, reliability, and reproducibility. LLJ Cards addresses this need by providing a structured framework for applying these principles in the design and reporting of automated evaluations.
Large language model (LLM) applications are increasingly expected to satisfy deterministic institutional requirements while relying on probabilistic generative components. This mismatch makes ordinary post-hoc benchmarking insufficient for systems that must be safe, reliable, auditable, and economically useful. This paper contributes an evaluation-protocol extension for operational LLM systems grounded in acceptance-test-driven development, safety engineering, and business-centric validation. The extension translates stakeholder goals into executable behavioral contracts, release gates, monitoring signals, and evidence artifacts before prompt, model, retrieval, or agent changes are accepted. It adapts the red-green-refactor discipline of test-driven development to a red-train-green lifecycle: first define failing acceptance tests for desired behavior, then improve the LLM system through prompt changes, retrieval design, fine-tuning, guardrails, or data augmentation, and finally release only when multidimensional gates are satisfied. The contribution is a governance-oriented metric stack, reference architecture, and empirical protocol for comparing acceptance-test-driven LLM development against prompt-first and benchmark-after workflows.
LLM-agent evaluation reports behavioral scores but leaves the identity of the deployed runtime stack unreported. A tampered deployment that preserves evaluated outputs passes every output-only evaluator. We introduce DIB-Bench, a benchmark that measures this deployment-integrity blindness across 7,560 scored examples, six tamper types, and an evaluator ladder from regex scorers through LLM judges to GPT-5-nano. Stronger evaluators accept more tampered outputs: mean acceptance rises from 88.6% (rule-based) to 94.1% (GPT-5-nano), and a trigger-conditional tamper invisible on the evaluation suite produces 48-100% harmful outputs, rising with model capability. A PAC-style bound shows that tampers with zero output shift are undetectable from outputs at any sample size; a manifest-hash identity channel detects them with zero samples. Behavioral fingerprinting identifies the model component above chance (76.7%) but covers one of six stack components. We also propose a graded deployment-identity descriptor for evaluation reports.