| name | benchmark-artifacts |
| description | Name and validate Tau autonomy benchmark proof artifacts. |
When writing benchmark proof artifacts:
- Use deterministic names that include mission id, benchmark id, run id, and proof type.
- Prefer paths shaped as
artifacts/bench/<benchmark-id>/<mission-id>/<run-id>/<proof-type>.json.
- Keep
latest.json as an index or pointer only; do not make it the sole proof artifact.
- Include mission id, benchmark id, run id, proof type, generated timestamp, verification gates, and artifact source in the artifact payload when available.
- When a benchmark task emits multiple files, keep the same prefix and vary only the proof type suffix.
- Do not claim benchmark proof unless the named artifact exists and can be read.
