Output destination

The durable system, path, queue, record, or channel where a workflow commits its result for downstream use.

A destination can be a database row, object store, file, draft, ticket, message queue, API, or user-facing notification. Storage and attention are different contracts: the authoritative record may live in a database while a notification tells someone it needs action. The destination should define identity, schema, ownership, permissions, retention, and duplicate behavior.

Builder example

Recurring ingestion should create durable product records rather than disappear into a transient summary or unread dashboard. Idempotent keys, provenance, timestamps, status, and error routing let the result power search, history, and later workflows whether or not a person opens it immediately.

Common confusion: A notification is not necessarily the source record, and a visually convenient folder is not necessarily an authoritative destination. Choose by downstream ownership and use, then add the right attention channel.