Redirect a paid order

Maya asks to ship a paid order to her office instead of home.

Illustrative reference scenario, not a live run. Named people, results, scores and durations are teaching examples. 38 live handoffs in this variant, including additional dialogue or repeated work; omitted branches remain inspectable.

1 / 41 frames

Live task · pass 1

UserInteraction

task arrives on a channel

Maya messages support: “Can you ship my order to my office instead?” She has already paid.

Runtime planeTrust planeExecution planeKnowledge plane

Knowledge plane

Execution plane

Trust plane

Runtime plane

All exchanges and omitted work

Record what can be verified.

Preserve supplied inputs, applied policies, tool actions, approval records and state changes. A useful audit trail reconstructs the operation; it does not expose private chain-of-thought.

Recovery has three different jobs.

Stop future actions; restore a compatible release; compensate for external effects where possible. Restoring software cannot unsend an email or undo every transaction.

Inspect the release bundle ↗

In the canonical reference, messages 16 and 17 are one reasoning request/response pair crossing the model core—not two invocations. Other scenarios may add intent calls, repeat the reasoning loop or omit it. Follow this exchange and its AML mapping in Journey ↗