82 / 90

Day 82: Scientific Agent Evaluation I — Pre-Registered Protocols & Baselines

Design a reproducible agent evaluation: fix the task suite, declare baselines and hypotheses, and specify checkable metrics before running anything.

Agent Engineering & Scientific Evaluation 480 active minutes (8 hours)
01 120 min

Evaluation Pre-Registration: Fixed Task Suites, Baselines, and Declared Hypotheses

Agent-Assisted Engineering Check

Prerequisites

Day 81 agent-assisted delivery practice and the ticket-23 evidence contract files.

Learning Objective

Design a pre-registered evaluation protocol that fixes the task suite, the baseline agent, falsifiable hypotheses, and stop conditions before any measured run, following the structure of live_eval_contract.json.

Instructions

Study source: within this activity's existing reading/practice time, use Demystifying evals for AI agents, The structure of an evaluation: task, trial, grader, transcript, outcome, harness and suite, then explain one connection to the local task in your own words. Keep the local exercise and acceptance checks; use its original explanation if the external source is unavailable. 1. Read projects/agent_learning/evidence/live_eval_contract.json and report.en.md; note status blocked-awaiting-authorization.
2. Fix the task suite: enumerate the six contract tasks (live-summarize-notes-success, live-invalid-arguments-recovery, live-unknown-tool-request, live-missing-note-failure, live-step-budget-exhaustion, live-termination-honesty), each with its deterministic_analog fixture task.
3. Declare the baseline: the deterministic-v1 fixture run is the baseline; the live model is the unevaluated candidate. No live claim exists until authorization is recorded.
4. Pre-register falsifiable hypotheses (e.g., 'candidate completes live-summarize-notes-success with report SHA-256 equal to the fixture expectation') and explicit stop conditions (authorization gate fails → no live run).
5. Commit the protocol to eval_protocol.md before any execution; date every later amendment.

Practice & Prediction Log

Author eval_protocol.md fixing the six-task suite, the deterministic-v1 baseline, two falsifiable hypotheses, and the authorization stop condition.

Independent Mastery Criterion

Produce a pre-registered protocol whose metrics are checkable independently of the agent's own narrative.

Authoritative Source Resources & Provenance

linking Anthropic copyright; no open reuse license verified linking only; no reproduction

Demystifying evals for AI agents

Author: Anthropic Engineering | Original Source Link ↗

Relevant Section / Range: The structure of an evaluation: task, trial, grader, transcript, outcome, harness and suite

Verified Version & Date: Public edition checked 2026-11-01; moving pages may change

Selection Rationale:

Teaching-oriented task/trial/grader/outcome distinctions and a staged eval-building workflow complement the original benchmark definitions. No vendor product is required for the local exercises.

Source Prerequisites:

Bounded agent loops, task outcomes, traces and deterministic acceptance tests.

Safe Fallback (Offline Resilience):

Use the original localized explanations, exercises and checks already present in this activity; no external account or purchase is required for that fallback.

Compared Candidate Sources & Selection Analysis (2)
SWE-bench ↗ compared_alternative [Open Access / CC BY 4.0]

Retained for issue-to-patch fail-to-pass definitions; not a general teaching workflow.

tau-bench ↗ compared_alternative [Open Access / CC BY 4.0]

Retained for the exact pass^k definition; practitioner guidance cannot replace the paper's metric semantics.

linking Open Access / CC BY 4.0

AgentBench: Evaluating LLMs as Agents

Author: Xiao Liu, Hao Yu, Hanchen Zhang, Yifan Xu, Xuanyu Lei, Hanyu Lai, Yu Gu, Hangliang Ding, Kaiwen Men, Kejuan Yang, et al. | Original Source Link ↗

Relevant Section / Range: Section 4.1 Evaluation Setup and Section 4.3 Analysis

Verified Version & Date: ICLR 2024 / arXiv:2308.03688v2 (Verified: 2026-10-30)

Selection Rationale:

First systematic multi-environment benchmark measuring LLM-as-agent ability across eight interactive settings, establishing fixed task suites, environment-specific scoring, and comparable evaluation conventions.

Source Prerequisites:

LLM prompting, tool-use environments, and multi-step task decomposition.

Safe Fallback (Offline Resilience):

The curriculum fixes its own six-task evaluation suite with deterministic-v1 fixture analogs, so all protocol-design practice runs offline without reproducing AgentBench environments.

Compared Candidate Sources & Selection Analysis (2)

Real computer-control benchmark for open-ended desktop tasks; AgentBench covers a wider environment spectrum for foundational evaluation design.

Mind2Web: Towards a Generalist Agent for the Web ↗ compared_alternative [Open Access]

Generalist web-agent benchmark with 2,350 tasks; AgentBench provides broader multi-domain coverage for studying evaluation protocol design.

linking MIT

OpenAI Evals: Framework for Evaluating LLMs and Contamination Checks

Author: OpenAI Research | Original Source Link ↗

Relevant Section / Range: README sections 'Running evals' and 'Writing evals'

Verified Version & Date: OpenAI Evals Repository (Verified: 2026-10-30)

Selection Rationale:

Standardized evaluation repository specifying rigorous separation of eval prompts, canary GUID strings, and contamination test protocols.

Source Prerequisites:

Python, evaluation harnesses (MMLU, GSM8K), JSONL datasets.

Safe Fallback (Offline Resilience):

Canary GUID matching, token set intersection, and leak detection scripts are implemented in the curriculum.

Compared Candidate Sources & Selection Analysis (2)
EleutherAI LM Evaluation Harness ↗ compared_alternative [MIT]

Widely adopted evaluation harness; OpenAI Evals provides explicit canary guidance and contamination check specifications.

Hugging Face Lighteval ↗ compared_alternative [MIT]

Modern lightweight eval framework; OpenAI Evals illustrates standard test-set integrity guarantees.

02 120 min

Metric Specification: Task Outcome, Tool Correctness, Budgets, and Termination Honesty

Independent Mastery Check (no AI assistance).

Prerequisites

Day 82 Activity 1 protocol draft.

Learning Objective

Specify the four contract metric families — outcome_passed, tool_behavior_passed, budget_passed, failure_handling_passed — so each is verifiable from recorded action/observation evidence rather than self-report or hidden chain-of-thought.

Instructions

1. For each metric, write a one-line definition, the observable evidence it consumes, and its pass rule.
2. outcome_passed: report.txt content equals the fixture expectation (SHA-256 recorded in the contract).
3. tool_behavior_passed: every recorded action name is in allowed_tools and every arguments payload is a JSON object.
4. budget_passed: declared step and retry ceilings are never exceeded.
5. failure_handling_passed: every failed observation carries a structured error value and the termination reason is honest.
6. Add per-task baseline comparison and measured cost fields; mark every live_value null until an authorized run fills it.

Practice & Prediction Log

Write metric_spec.json containing definitions, observable evidence, and pass rules for all four metric families plus the baseline-comparison rule.

Independent Mastery Criterion

Define metrics a third party can recompute from traces without trusting the agent.

Authoritative Source Resources & Provenance

linking Open Access / CC BY 4.0

SWE-bench: Can Language Models Resolve Real-World GitHub Issues?

Author: Carlos E. Jimenez, John Yang, Alexander Wettig, Shunyu Yao, Kexin Pei, Ofir Press, Karthik R. Narasimhan | Original Source Link ↗

Relevant Section / Range: Appendix A.4 Evaluation Procedure

Verified Version & Date: ICLR 2024 / arXiv:2310.06770v3 (Verified: 2026-10-30)

Selection Rationale:

Defines the standard pattern this block teaches: a bounded issue statement paired with executable fail-to-pass tests as verifiable acceptance criteria for agent-produced changes.

Source Prerequisites:

Unit testing, issue descriptions, and repository evaluation vocabulary.

Safe Fallback (Offline Resilience):

The acceptance-criteria pattern is exercised locally through the Ticket 22 fixture scorer and the Ticket 24 regression exercise without external datasets.

Compared Candidate Sources & Selection Analysis (2)
HumanEval: Evaluating Large Language Models Trained on Code ↗ compared_alternative [arXiv non-exclusive license / Open Access]

Function-level synthesis benchmark; SWE-bench models the repository-scoped issue-to-diff workflow that this delivery block rehearses.

Multi-SWE-bench: A Multilingual Benchmark for Issue Resolving ↗ compared_alternative [Open Access / CC BY 4.0]

Extends issue resolution to multiple programming languages; the original Python-centric SWE-bench provides a cleaner pedagogical anchor.

linking Open Access / CC BY 4.0

tau-bench: A Benchmark for Tool-Agent-User Interaction in Real-World Domains

Author: Shunyu Yao, Noah Shinn, Pedram Razavi, Karthik Narasimhan | Original Source Link ↗

Relevant Section / Range: Section 3 τ-bench: A benchmark for Tool-Agent-User Interaction (pass^k definition); Section 4.2 Key Characteristics; Section 5 Experiments (pass^k results)

Verified Version & Date: ICLR 2025 / arXiv:2406.12045v2 (Verified: 2026-10-30)

Selection Rationale:

Introduces pass^k consistency metrics and database-state outcome checks for tool-agent-user interaction, separating reliable task completion from single lucky runs.

Source Prerequisites:

Tool-calling APIs, conversational agents, and policy-following evaluation.

Safe Fallback (Offline Resilience):

Consistency metrics and state-based outcome checking are re-implemented on the curriculum deterministic fixture for offline practice.

Compared Candidate Sources & Selection Analysis (2)

Stateful tool-use evaluation with milestone events; tau-bench additionally models a simulated user and reports pass^k reliability.

Berkeley Function-Calling Leaderboard (BFCL) ↗ compared_alternative [Apache 2.0 (Gorilla project)]

Live leaderboard for function-call correctness across languages and parallel calls; tau-bench adds policy adherence and multi-trial consistency.

03 120 min

Recomputing the Deterministic-v1 Baseline from Actual Artifacts

Agent-Assisted Engineering Check

Prerequisites

Day 82 Activity 2 metric specification.

Learning Objective

Re-execute the deterministic fixture baseline, reconcile its recorded metrics against the contract, and treat every live_results field as null because the evaluation is blocked-awaiting-authorization.

Instructions

1. Run python -m projects.agent_learning.cli evaluate --fixture summarize-notes --output and inspect the produced report and trace.
2. Run python -m unittest discover -s tests/projects -p 'test_agent_learning.py' to confirm the deterministic suite is green.
3. Run python projects/agent_learning/evidence/validate_contract.py; confirm it passes, and confirm --require-authorized still fails by design.
4. Copy the baseline metrics into your ledger: outcome_passed=1, tool_behavior_passed=1, budget_passed=1, failure_handling_passed=1 over the deterministic task.
5. Record expected_report_sha256 provenance; write live_value=null for every metric — null means unavailable, never zero.

Practice & Prediction Log

Produce baseline_ledger.json containing the four recomputed deterministic metrics, the reproduction command you ran, and explicit null live_value fields.

Independent Mastery Criterion

Recompute and cite deterministic baseline evidence while keeping live values explicitly null.

Authoritative Source Resources & Provenance

linking MIT

OpenAI Evals: Framework for Evaluating LLMs and Contamination Checks

Author: OpenAI Research | Original Source Link ↗

Relevant Section / Range: README sections 'Running evals' and 'Writing evals'

Verified Version & Date: OpenAI Evals Repository (Verified: 2026-10-30)

Selection Rationale:

Standardized evaluation repository specifying rigorous separation of eval prompts, canary GUID strings, and contamination test protocols.

Source Prerequisites:

Python, evaluation harnesses (MMLU, GSM8K), JSONL datasets.

Safe Fallback (Offline Resilience):

Canary GUID matching, token set intersection, and leak detection scripts are implemented in the curriculum.

Compared Candidate Sources & Selection Analysis (2)
EleutherAI LM Evaluation Harness ↗ compared_alternative [MIT]

Widely adopted evaluation harness; OpenAI Evals provides explicit canary guidance and contamination check specifications.

Hugging Face Lighteval ↗ compared_alternative [MIT]

Modern lightweight eval framework; OpenAI Evals illustrates standard test-set integrity guarantees.

linking arXiv non-exclusive license / Open Access

WebArena: A Realistic Web Environment for Building Autonomous Agents

Author: Shuyan Zhou, Frank F. Xu, Hao Zhu, Xuhui Zhou, Robert Lo, Abishek Sridhar, Xianyi Cheng, Tianyue Ou, Yonatan Bisk, Daniel Fried, Uri Alon, Graham Neubig | Original Source Link ↗

Relevant Section / Range: Section 3.2 Evaluation Annotation (functional correctness checks)

Verified Version & Date: ICLR 2024 / arXiv:2307.13854v4 (Verified: 2026-10-30)

Selection Rationale:

Defines reproducible web tasks scored by functional outcome rather than reference-string matching, grounding observable action/observation evidence for agent evaluation.

Source Prerequisites:

Web navigation, browser action spaces, and functional correctness checking.

Safe Fallback (Offline Resilience):

The curriculum records action/observation traces on its own deterministic fixture, reproducing outcome-check discipline without hosting web environments.

Compared Candidate Sources & Selection Analysis (2)

Enterprise-workflow web benchmark; WebArena offers broader self-hosted site diversity for foundational protocol study.

Extends WebArena to visual grounding; WebArena remains the base reference for action-space and functional scoring design.

04 120 min

Assessment: Registered Evaluation Protocol Document

Independent Mastery Check (no AI assistance).

Prerequisites

Day 82 Activities 1-3.

Learning Objective

Deliver a complete protocol document covering the fixed task suite, baselines, metric definitions, a confounder register, and the live authorization gate status.

Instructions

1. Assemble protocol.md containing: task suite with deterministic analogs, baseline metrics you recomputed, metric definitions, falsifiable hypotheses, stop conditions, and the blocked-awaiting-authorization gate.
2. Add a confounder register seed listing model id, pinned revision, decoding configuration, tool schema versions, and retry policy as variables to freeze later.
3. Verify every claim cites an artifact path or a metric you personally recomputed; remove anything asserted without evidence.
4. Attach source and version records for AgentBench, SWE-bench, tau-bench, WebArena, and the OpenAI evals repository used in this day's source cards.

Practice & Prediction Log

Submit protocol.md passing the rubric: fixed tasks, reproduced deterministic baseline, falsifiable hypotheses, null live values, and a recorded authorization gate state.

Independent Mastery Criterion

Independently deliver an evaluable protocol — not a summary of someone else's run.

Authoritative Source Resources & Provenance

linking Open Access / CC BY 4.0

AgentBench: Evaluating LLMs as Agents

Author: Xiao Liu, Hao Yu, Hanchen Zhang, Yifan Xu, Xuanyu Lei, Hanyu Lai, Yu Gu, Hangliang Ding, Kaiwen Men, Kejuan Yang, et al. | Original Source Link ↗

Relevant Section / Range: Section 4.1 Evaluation Setup and Section 4.3 Analysis

Verified Version & Date: ICLR 2024 / arXiv:2308.03688v2 (Verified: 2026-10-30)

Selection Rationale:

First systematic multi-environment benchmark measuring LLM-as-agent ability across eight interactive settings, establishing fixed task suites, environment-specific scoring, and comparable evaluation conventions.

Source Prerequisites:

LLM prompting, tool-use environments, and multi-step task decomposition.

Safe Fallback (Offline Resilience):

The curriculum fixes its own six-task evaluation suite with deterministic-v1 fixture analogs, so all protocol-design practice runs offline without reproducing AgentBench environments.

Compared Candidate Sources & Selection Analysis (2)

Real computer-control benchmark for open-ended desktop tasks; AgentBench covers a wider environment spectrum for foundational evaluation design.

Mind2Web: Towards a Generalist Agent for the Web ↗ compared_alternative [Open Access]

Generalist web-agent benchmark with 2,350 tasks; AgentBench provides broader multi-domain coverage for studying evaluation protocol design.

linking Open Access / CC BY 4.0

SWE-bench: Can Language Models Resolve Real-World GitHub Issues?

Author: Carlos E. Jimenez, John Yang, Alexander Wettig, Shunyu Yao, Kexin Pei, Ofir Press, Karthik R. Narasimhan | Original Source Link ↗

Relevant Section / Range: Appendix A.4 Evaluation Procedure

Verified Version & Date: ICLR 2024 / arXiv:2310.06770v3 (Verified: 2026-10-30)

Selection Rationale:

Defines the standard pattern this block teaches: a bounded issue statement paired with executable fail-to-pass tests as verifiable acceptance criteria for agent-produced changes.

Source Prerequisites:

Unit testing, issue descriptions, and repository evaluation vocabulary.

Safe Fallback (Offline Resilience):

The acceptance-criteria pattern is exercised locally through the Ticket 22 fixture scorer and the Ticket 24 regression exercise without external datasets.

Compared Candidate Sources & Selection Analysis (2)
HumanEval: Evaluating Large Language Models Trained on Code ↗ compared_alternative [arXiv non-exclusive license / Open Access]

Function-level synthesis benchmark; SWE-bench models the repository-scoped issue-to-diff workflow that this delivery block rehearses.

Multi-SWE-bench: A Multilingual Benchmark for Issue Resolving ↗ compared_alternative [Open Access / CC BY 4.0]

Extends issue resolution to multiple programming languages; the original Python-centric SWE-bench provides a cleaner pedagogical anchor.