Status
Tracer does not keep mutable status in config.yaml. The config has only
meta_info and runtime_info; it is copied into each job and run archive to
record what was launched.
Sources of truth
| State | Source |
|---|---|
| Archived run history | artifacts/index.yaml |
| One run's immutable metadata | artifacts/archives/run_NNN/metadata.yaml |
| Harbor job progress and aggregate results | artifacts/jobs/<job>/result.json |
| Per-task outcome and trajectory | artifacts/jobs/<job>/<task>/ |
| Launch/proxy output | artifacts/logs/tracer_*.log |
| Processed-task protection | artifacts/processed_tasks.yaml |
| Combined visual view | Dashboard |
scripts/start.sh installs an EXIT trap. On success, failure, SIGINT, or
SIGTERM, it stops its LiteLLM proxy, snapshots the config and scripts under
artifacts/archives/run_NNN/, and appends a
completed | failed | interrupted entry to artifacts/index.yaml.
During a run
Monitor the active artifacts/jobs/<job>/ directory, the launch log, or the
dashboard. Do not edit config.yaml to record progress: it represents the
profile used to construct the command. After the job, the tracer run procedure
inspects task outcomes and updates processed_tasks.yaml.
Time convention
Archive timestamps are written in UTC. Job directory names are generated with the launch host's local clock, so their timestamp may use a different timezone while still identifying the correct on-disk job.