SCRIPTED DRY RUN — generated from deterministic stub sessions for pipeline testing.
RModelSpar

Refund retry — model replacement report

current-model (scripted) (imported baseline) → candidate-model (scripted) (scripted replay) · 1 workflow · development corpus

Decision rule: a changed, novel, duplicated, or naturally omitted configured write produces HOLD · read-path differences remain comparative signals · evidence gaps produce an unverifiable result.

0
equivalent
1
regressed
0
unverifiable
n/a
cost delta
Comparable subset: n/a → n/a across 0 complete scripted replays
All observed runs: n/a → n/a across 1.
n/a
model-side latency (median)
0 ms → 0 ms per model call · p90 0 → 0 ms · based on supplied model-span latency
n/a
token delta
0 → 0 tokens (same 0-workflow denominator)

Interpretation: This migration-delta report uses Refund retry example — reviewed write identity. A full safety assessment also requires customer policy rules and answer-quality evaluations.

Regressions (1)

regressed refund-retry changed write replay partial from call 3Refund $25 from order 1842 for the damaged item.

“Refund $25 from order 1842 for the damaged item.”

First meaningful divergence at call 3: write differs: baseline create_refund({"amount_cents":2500,"idempotency_key":"refund-1842","payment_id":"pay_1842"}) vs candidate create_refund({"amount_cents":2500,"idempotency_key":"refund-1842-retry","payment_id":"pay_1842"})

Recorded — current-model (scripted)

1 get_payment {"order_id":"1842"}
2 create_refund {"payment_id":"pay_1842","amount_cents":2500,"idempotency_key":"refund-1842"} network_timeout
3 create_refund {"payment_id":"pay_1842","amount_cents":2500,"idempotency_key":"refund-1842"} succeeded
Final reply: Your $25 refund has been processed.

Candidate — candidate-model (scripted)

1 get_payment exact {"order_id":"1842"}
2 create_refund exact {"payment_id":"pay_1842","amount_cents":2500,"idempotency_key":"refund-1842"} network_timeout
3 create_refund cannot replay {"payment_id":"pay_1842","amount_cents":2500,"idempotency_key":"refund-1842-retry"} cannot_replay
⛔ replay stopped here — call 3 has no recorded counterpart
Final reply: (none)

Unverifiable (0)

None.

Equivalent (0)

Imported evidence

Baseline trajectories came from imported traces. Candidate tool calls come from a deterministic script exercised through ModelSpar’s replay engine with recorded tool results. No model endpoint or production tool was called. The replay-readiness gate selects cases with complete tasks, system prompts, tool names, arguments, and results. This synthetic case contains the required replay inputs.

The candidate runs use isolated playback against recorded results. Baseline self-check calibration can quantify replay noise for a rollout-grade corpus.

Comparison coverage

The report uses reviewed tool semantics to detect changed customer-affecting actions. A separate policy pack adds customer-specific business rules.

SignalCoverageWhat the verdict actually knows
Configured write toolsenforcedChanged, novel, duplicated, and naturally omitted side effects are compared using the reviewed identity keys.
Read callscomparative-onlyRead membership differences appear as comparative signals. Configured writes determine the trajectory classification.
Business invariantsrequires policy packThis report detects migration deltas. A customer-specific policy pack adds business-invariant evaluation.
Answer qualityimported separatelyThe import preserves existing evals. The trajectory verdict uses paired tool-call evidence.