Freshservice triage can receive a source-qualified attachment manifest in its signed ticket payload. Ordered ingestion and preparation nodes retain originals, process eligible images and voicemail, and carry explicit incomplete-evidence outcomes into triage. Video is retained without analysis. Initial policy permits 20 attachments, 100 MiB per original, and 250 MiB total retained originals; media processing has smaller independent limits.The Freshservice client downloads by stable attachment ID with measured byte limits and content digests. File Hosting reports actual provider guarantees, refuses automatic duplicate uploads after an unknown result, and propagates existing run/debug retention to unshared file evidence. Consumer runs retain declared file inputs through their own lifecycle. A bounded historical-input migration must complete before destructive cleanup is enabled. No new storage provider is required.Image and voicemail inference use normal budget and usage accounting before derived text is released. Audio duration, rate and cost provenance are recorded separately from token usage; duration-only cost estimates are explicit.Deploy the compatible receiver before installing the sender ZIP. Tenant attachment IDs, download behavior, secure source templates, and approved media routes require qualification before activation. Packaging and fixture tests do not establish a live installation.
Weekly entries
2026-11-07 — Forge updates
Signed attachment manifests, bounded downloads, governed media evidence, and File Hosting transfer and retention safeguards. The guarded ownership checkpoint now pins the latest approved version history.

