Delivery: where the outcome lands

A run that finishes and tells nobody has not finished the job. Delivery is how the outcome reaches the person who wanted it, and on YAMO there are two live channels.

In the work rail

The Instance conversation is where the work appears. Progress shows while the run is going, step by step, and the deliverable lands in the rail beside the conversation when it is done. The run then adds one line to the thread saying so, and that line stays: the conversation is a record, not a feed.

Closing the tab changes nothing. Runs execute in the background and the result is waiting when you come back.

By email

Email covers the three moments that matter when you are not watching.

• Waiting for you. A step with a human gate has paused the run. The email links you to the review; nothing is approved from the email itself.
• Finished. The run succeeded, with the finished work in the body of the message rather than only a link to it. A very long document is trimmed and says that it was.
• Failed. The run stopped, with the honest reason.

There is a fourth notification, for a change to a Service you subscribe to that alters what it needs from you. It tells you; it never gates you.

Which of the four you receive is a per-Instance setting, so one noisy Playbook does not make you turn everything off.

What is not built

There is no SMS, no chat channel and no outbound webhook. The interface for adding one exists in the code and nothing implements it yet, so a Playbook that declares a webhook output gets a document with a line saying the delivery is not wired up.

There is also no digest. Each run notifies on its own.

A note on the declared delivery channels

A Playbook's document can name its delivery channels, and that declaration is shown as part of what the Service promises. It is contract copy: today it does not switch anything on or off. What you actually receive is governed by the notification settings on your Instance.