ATS / example

Blocked-Handoff-Note.md

See how blocked work can be handed off clearly.

DownloadView source file Read related standard

Useful when

Agent work is hard to continue.

Choose your situation

What you should change

Replace the illustrative blocker, recovery options and next owner.

Use only the parts that help. These are starting points, not rigid requirements.

View resource

# Handoff Note

## Current State

The AAS suite has a candidate specification, manifest, adoption guide, validation checklist, changelog, and templates. A filled evaluation run example has been drafted, but the exact metrics for the production evaluation pipeline are not final.

## What Changed

- Added an example evaluation record using placeholder local analysis outputs.
- Clarified that AAS records evidence and interpretation boundaries, while DDS governs dataset provenance and ATS governs agent work history.

## What Was Left Alone

- No production metrics were renamed.
- No evaluation command was declared mandatory.
- No source dataset was moved or rewritten.

## Next Safe Action

Choose one real evaluation workflow and record a completed AAS run using its actual inputs, commands, metrics, output files, and limitations.

## Known Risks

- Treating placeholder metrics as required metrics would over-constrain future analysis work.
- Publishing an evaluation record before DDS provenance is complete could make the results hard to reproduce.