Decisions in order
Every accepted request receives immutable ordered entries, timestamps, receipt identity, before/after observations, and state digests.
Run one multi-step interactive scenario in a clean episode. Inspect replayable observations, actions, typed outcomes, failure points, annotations, and exact scenario provenance.
Phase 1 boundary: descriptive behavior under one named scenario/configuration only. No benchmark validity, model ranking, leaderboard, public submissions, or broad long-horizon claim.
The primary artifact is an owner-authenticated, versioned trace designed to reconstruct observation → action → receipt/outcome. Fantasy presentation stays outside the evidence contract.
Every accepted request receives immutable ordered entries, timestamps, receipt identity, before/after observations, and state digests.
Target, geometry, dialogue, lifecycle, validation, and outcome failures use an extensible versioned typed contract.
Protocol, environment release, scenario schema/revision/build, deterministic inputs, safe agent metadata, and reset/cleanup proof travel with the run.
Use an account-owned API key and keep one run on one fail-closed HTTP client. OAuth is not required; broad activation is out of Phase 1. The Python SDK and MCP tools use this same contract.
missing_apprentice, act through the returned run ID, then retrieve or export evidence.# TAVERNBENCH_API_KEY is supplied locally; never place it in evidence.
from tavernbench import Client
with Client.from_env() as lab:
run = lab.start_run(
participant_code="builder-01",
agent_metadata={
"agent_name": "concierge-agent",
"client_name": "python-sdk",
"client_version": "0.2.0",
"config_label": "baseline",
},
)
receipt = lab.act(run.id, action="observe")
lab.abort(run.id)
evidence = lab.export(run.id, "tavernbench-evidence.json")
print(evidence["integrity"]["status"])
missing_apprentice is a validation-study instrument, not a scenario catalog or user-authored platform.
No comparative validity, rigorous benchmark, model ranking, public leaderboard, or generalization claim.
Account-owned API keys only. No anonymous persistence, public submission, broad OAuth activation, or unsupported commands.
Phase 1 episode ownership is local to one server node. Multi-node execution and public self-service operation are unsupported.
The concierge study records only opaque recruitment status, run linkage, annotations, and three participant outcomes. No participants, results, models, scores, traffic, costs, or commitments are invented.
Stop rule: if any threshold is missed after the six-builder, eighteen-episode collection completes, stop platform investment and retain the research/portfolio artifact.