Trace Analyzer¶
trace_analyzer converts method-neutral rollout cases into bounded evidence for
meta_agent. It is optional, but recipes that need structured observations
should configure it explicitly.
rollout/cases.json
→ trace_analyzer
→ trace_analyzer/evidence/
→ feedback/evidence/selected.md
→ meta_agent
Contract¶
The result contains a summary and artifact paths.
Variants¶
| Variant | Selected evidence |
|---|---|
failure_patterns |
aggregate metrics, verifier-grounded failure clusters, representatives, and passing behavior |
failed_traces |
metrics plus detailed failed and agent-error executions |
trace_browser |
compact metrics and filesystem instructions for retained raw traces |
trajectory_only |
A-Evolve behavior-only proxy judgments without evaluator labels or task text |
execution_records |
complete per-case execution, tool, verifier, and history records |
utility_metrics |
per-task downstream utility with less trajectory emphasis |
ahe |
per-task debugger analysis for Agentic Harness Engineering |
gepa |
component-oriented reflective examples and datasets |
Configuration¶
operators:
rollout:
variant: harbor
budget_tasks: 8
trace_analyzer:
variant: failure_patterns
max_chars: 30000
timeout_s: 600
Common bounds include max_chars, max_cases, max_tasks, field_limit,
history depth, concurrency, retry count, and per-task timeout. Variant-specific
keys should be copied from the closest supported recipe.
Inputs and artifacts¶
Most deterministic variants write an auditable evidence bundle:
runs/gen-N/trace_analyzer/evidence/raw_traces.jsonl
runs/gen-N/trace_analyzer/evidence/failure_records.json
runs/gen-N/trace_analyzer/evidence/failure_patterns.json
runs/gen-N/trace_analyzer/evidence/passing_behaviors.json
runs/gen-N/trace_analyzer/evidence/reflective_records.jsonl
runs/gen-N/trace_analyzer/evidence/metrics.json
runs/gen-N/trace_analyzer/evidence/manifest.json
runs/gen-N/trace_analyzer/evidence/selected.md
selected.md is copied to feedback/evidence/selected.md and included in the
meta-agent prompt.
gepa additionally writes reflective datasets and per-component reflection.
ahe writes debugger-oriented case analysis.
Fidelity boundary¶
All variants except trajectory_only deterministically parse, filter, cluster,
serialize, and truncate existing rollout facts.
trajectory_only adds an isolated behavior-only model judge. Its evidence
directory intentionally omits reward, verifier output, task input, and raw-case
paths. The A-Evolve Harbor bundle also omits archive and run history so those
labels cannot be recovered by filesystem inspection.
The variant selects an evidence shape; it does not by itself reproduce every search or optimization capability of the method that motivated it.