Managed runs write execution evidence directly into Agent-owned attempt directories. Suites contain scheduling state and checked references. There is no completion-time archive conversion, and new writes never unpack an archive.
results/
suites/<suite-id>/
plan.json
events.json scheduling journal and result references
gt.json references to Agent-owned GT results
agents/<agent-id>/
agent.json
records/<sha256>.json immutable results referenced by Suite events
preparations/<id>/ generation diagnostics and SDK recovery state
cases/<storage-id>/
case.json published prepared Case
attempts/<id>/
run.json host execution, cleanup, trace acceptance and trajectory status
trajectory.json derived step sequence (abb.agent-trajectory.v1)
manifest.json SDK execution summary and step index
case.json exact SDK-loaded Case with execution identities
process.json execution configuration/provenance
steps/0001/
input.json SDK Input contract
request.json Agent invocation contract
result.json native Agent result
submission.json SDK-committed submission and evidence
otel-status.json capture validation; other capture metadata stays here
spans.jsonl step traces, alongside OTel/live traces when present
otel-payloads/ ordinary file paths sharing immutable blob bytes
blobs/<sha256> content-addressed payload storage
judge/
context.json checked references to Case, Inputs and submissions
report.json
judge-task.json durable host Judge task state
logs/ network, SDK, host and controller timing streams
sdk-repo/ SDK-native repository/ledgers, where required
judge-state/ SDK-native host Judge recovery state, where required
recovery/ recovery records, when present
gt/<suite-id>/ GT calls and evaluations for this Agent
SDK-specific private files are retained under their native names. Optional workspace/replay evidence and diagnostics are retained when produced. Input, invocation, native output and committed submission are separate contracts: they must not be collapsed just because some fields coincide.
- Allocate the Agent Case slot and attempt, then persist host status.
- Write each step directly under
steps/<ordinal>as it runs. Publish JSON atomically; append trace streams while execution is active. - Name immutable OTel payloads by their redacted content hash. When collecting a response, publish an attempt blob and hard-link step payload paths to it. Filesystems without hard links retain ordinary copies. Mutable event streams remain separate while the producer is running.
- Save Judge context as path-and-SHA-256 references to the already committed Case, Inputs and submissions. The Judge verifies and expands those references in memory. SDK request ledgers remain in place for cancellation and retry.
- Stop containers and validate host trace evidence. Then derive
trajectory.jsonfrom the committed records and record its status inrun.json; a derivation failure writes the file withstatus: failed. Only then remove temporarychannel,agent-requestandagent-outputcommunication directories. Failed cleanup or unaccepted traces retain transport files for diagnosis. No execution artifact is moved or repacked at completion.
trajectory.json is self-contained: every step keeps the full model input and
output and its tool logs, and sources records the digests of the files it was
derived from. Historical attempts without the file are derived on read by the
viewer and evaluation API, or persistently with
agentbench trajectory build DIR --write. See
agentbench/trajectory/README.md.
Running, failed, completed and resumed attempts use the same paths. A Judge retry updates its task/report and native ledger without copying the execution history. Execution, Judge, evidence and cleanup status remain distinct.
Case storage IDs are scoped to a Suite and slot, so equal Case indexes in separate
Suites cannot overwrite each other. Every execution receives a new attempt.
The published Case and execution Case have different identity/lifecycle roles.
Suite events.json remains a JSON array; large outcome fields reference immutable
Agent records by relative path and digest. Source GT is independent of generated
GT evaluations. Default GT evaluation reads saved evidence without rerunning the
Agent.
observe/artifact_paths.py accepts both current paths and historical
evaluation/inputs paths. Historical results are not automatically migrated,
and packed abb.trajectory.v1 archives are no longer readable.