AI evaluation · research-claim verification · reproducibility

Judge the work by the evidence.

I’m Robert “Bobby” Morong. I build inspectable evaluations that test whether AI, benchmark, statistical, and technical claims survive reruns, provenance checks, held-out tests, and adversarial scrutiny. I publish the code, frozen evidence, corrections, and limits.

Open to remote AI evaluation, research engineering, benchmark reliability, and technical verification work.

Selected work

Verification infrastructure first, evidence cases underneath

Agent evaluation · RCV-Bench

Can an AI agent verify a research claim?

A 14-task benchmark separates simple rerunning from harder provenance and robustness judgments. The naive rerun baseline scores 9/14 but misses every FRAGILE and FABRICATED case; a first autonomous local-agent baseline catches one fabricated case but remains weak overall.

The point is diagnostic, not leaderboard theater: can an agent distinguish a reproduced result from a deviation, unsupported evidence, or a result that collapses under a declared robustness test?

Benchmark, harness, baselines, and agent protocol ↗

Evaluation reliability · Inspect AI

Measure whether a benchmark score is stable

Eval Invariance Engine wraps multiple-choice evaluations with semantics-preserving perturbations and reports score drift and item-level flip rates inside Inspect AI.

It measures a narrow question directly: how much does the evaluation result depend on representation details that are not supposed to change the underlying task?

CLI, Inspect wrapper, metrics, and tests ↗

AI evaluation · MMLU

Option-order robustness

The regenerated Qwen harness changes its underlying answer on roughly 78% of sampled questions under four cyclic option orderings in both bf16 and fp32.

The headline robustness failure regenerated while several historical stability and calibration quantities did not. Tie-breaking and dtype controls did not remove the effect; the unresolved quantities remain explicitly unresolved.

Regeneration, Inspect port, results, and provenance ↗

AI evaluation · ARC-Challenge · two model families

Does a model's score depend on option order?

Four small open models (Qwen2.5 0.5B and 1.5B, SmolLM2 360M and 1.7B) were scored on all 1,165 four-option ARC-Challenge test questions under four cyclic option orderings. Within Qwen the order effect shrinks with size (74.6% of answers flip at 0.5B, 31.6% at 1.5B), but SmolLM2-1.7B flips 59.8%, so size alone does not predict it.

Four models are not a scaling law, and precision differs across runs (disclosed, with a tie-break control). SmolLM2-360M scores at chance and is excluded from comparisons. Pinned revisions, raw predictions, and every statistic are generated by code.

Read the writeup Code, raw predictions, provenance, and limits ↗

Scientific reproducibility · DESI DR2

Stress-test which observation carries the result

De-Stress Lab packages selection-aware influence analysis, empirical null calibration, frozen result ledgers, and a reproducible DESI DR2 application.

In the flagship analysis, LRG2 is load-bearing for the observed preference, but its localization is not additional independent evidence after conditioning on the global fluctuation.

Package, DOIs, diagnostics, and result manifest ↗

Reasoning evaluation · ARC-AGI-2

When candidate selection helps but generation still fails

Corrected same-holdout analysis puts k=1 demonstration reliability at 32.8%. MDL improves ambiguous-case selection by 11.1 points over random, while the candidate oracle is only 3.7 points above MDL.

The public correction overturned the earlier optimistic calibration story. The frozen solver remains 0/167; the contribution is the measurement and selection analysis, not a competitive ARC solver.

Corrected paper, frozen results, and CI ↗

External validation wanted

The next threshold is outside use, not more self-authored projects

These requests are intentionally small and falsifiable. Failed reproductions, compatibility problems, and technical criticism are useful outcomes.

RCV-Bench

Run an outside agent

Evaluate an agent on the 14-task protocol under a declared model, tool, network, budget, and isolation policy.

Wanted: one independent run External-run protocol ↗

Eval Invariance Engine

Try it on an existing Inspect task

Report whether the wrapper preserves task shape and scoring semantics, plus any observed drift or item-level flips.

Wanted: one outside user Outside-user request ↗

MMLU Robustness Audit

Reproduce the pinned protocol

Run the fixed 300-question protocol using the declared model and dataset revisions and compare the regenerated evidence.

Wanted: one independent rerun Rerun instructions ↗

Writing and tools

Practical material for people who run evaluations

Method

How the work is built

Reproduce before interpretingMatch the published result before diagnosing where it comes from.
Calibrate selectionAccount for the search that identified the most influential observation.
Freeze provenanceBind claims to versioned code, artifacts, checksums, and explicit status.
Publish limitsSeparate completed evidence, reconstructed results, and work still awaiting independent rerun.

These projects are independent analyses. They narrow what the public evidence supports; they do not substitute authority for verification or turn a localized hint into a discovery claim.

Applied verification

The same evidence discipline can be used on decision-relevant technical claims

A secondary applied track uses the same reproduce → stress-test → localize → qualify workflow for AI and statistical claims. It is supporting work, not the main research identity of this site.