Agent Logs, Artifacts, and Result JSON: The Output Contract That Makes Agents Usable

How to separate debug logs, final JSON, and downloadable files so agent workflows can power real products.

Audience: Engineering leaders turning agent output into product behavior.

The problem

Raw agent transcripts are not an API response. Products need a small final result, debug logs for support, and artifacts for downloads.

Implementation path

Make the skill submit argo.result.v1, keep logs paginated or downloadable, and upload output files as artifacts with content type, size, and signed URL metadata.

Tradeoffs and failure modes

A strict result contract takes design work up front, but downstream systems become dramatically simpler.

Output shape

result: { schema_version, summary, body }
logs: paginated conversation and tool events
artifacts: [{ filename, content_type, size, url }]

Run this on Argo