What belongs in a deployment evidence record

A pilot that cannot answer 'what did the robot do last Tuesday, and who intervened' is not ready to become an operation. The gap is rarely sensing or autonomy. It is record keeping across vendors that each keep their own.

The minimum record is: the task as assigned, the unit that ran it, the outcome, every human intervention with its cause, every incident with its time and disposition, and any reading or artifact captured along the way.

Records should be append-only. Corrections are appended with their own timestamp and author rather than overwriting the original, because a record that can be silently edited is not evidence.

Retention and export are the customer's decision. The operating data describes their site and their staff, and they should be able to export or delete it on request.

An evidence pack is a record. It is not a certification, an audit opinion, or a regulatory approval, and it should never be presented as one.