add_artifact

io.applayer/tango · Verify this server

Step 4 of the Tango working agreement (work in the open). Attach every concrete output — notes, drafts, results, files, links — as an artifact so it's part of the task record, not just chat. Real files (pdf, docx, pptx, xlsx, mp3, wav, m4a, images…) are supported: pass `content_base64` for files up to ~6 MB, `fetch_url` to have Tango download and store a hosted file itself, or call create_artifact_upload first for large files and finalize here with `upload_token`. `content` stays the path for inline text and `external_url` for a link you only want recorded. Reference artifact ids in complete_task's evidence_artifact_ids. If a lease is active, Tango attributes the artifact to the lease holder. Otherwise, pass `acting_worker_id` to identify which of your workers is acting; if you don't own that worker the attribution is dropped rather than misrecorded. Attested workers may pass `worker_signature` over the JCS-canonical artifact payload (type 'tango.artifact'); an invalid signature rejects the call and nothing is stored. Delegated workers are signed for automatically.