Design for someone who was not there
An engineer investigating a run today may remember the environment and know the operator. A reviewer opening an export months later has neither advantage. An evidence packet needs enough context to identify the execution, interpret its sequence, and understand the boundaries of the capture.
Start with the reason for sharing it. An internal reliability review may need different fields from a customer’s question about which system an agent touched. Collecting every available field is not the same as making the record useful.
Identify the source and the relationships
Include stable execution identity, the capture source and version, the actor identifiers relevant to the question, and the relationship between steps. Use parent or handoff relationships when there are several agents. A list sorted by upload time can misrepresent work that ran concurrently.
Explain whether the source is runtime instrumentation or assistant self-report. That choice changes what a reviewer can infer. Self-reported checkpoints may be helpful notes, but they should not acquire stronger provenance simply because they are exported in the same format as observed events.
Keep interpretation alongside the artifact
An export should explain the meaning of its timestamps, outcomes, and unknown values. If a duration is unavailable, say so. If a financial event represents only an attempted transaction, do not label it as settled. Preserve failed attempts when a later retry succeeds.
Where integrity checking is supported, include the format and verification instructions actually used. An unexplained digest is not enough. The reviewer needs to know the trusted reference and what a successful check establishes. Keep derived charts distinguishable from the source record.
Share deliberately
Execution data can contain secrets or personal information accidentally introduced by prompts and tools. Review the packet before distributing it. Remove fields unnecessary for the purpose and document any redaction so it is not mistaken for complete capture.
Agree who can access the packet and how long it should be retained. A downloaded copy may outlive the original workspace. Deleting the hosted record does not automatically retrieve copies already held by another reviewer. That practical boundary belongs in the handling plan.
Use the packet to support a claim, not every claim
A record showing an approval checkpoint can support a focused question about the workflow. It does not by itself establish the approver’s legal authority or the safety of the change. State the question answered, the evidence used, and the questions left open.
UpTrain’s current downloadable example illustrates this structure with fictional data. It is not a production evidence format or a certified artifact.