Every pattern in the Temporal design-pattern catalog, mapped to the agent problem it solves and where this book uses it.
The Temporal design-pattern catalog organizes about thirty-five patterns into twelve categories. It is written for distributed systems generally, with no mention of agents.
That is the opportunity. Nearly every hard problem in running an agent, such as memory that outgrows the window, tools with side effects, humans in the loop, provider quotas, or deploys mid-run, already has a named, battle-tested solution in that catalog. This appendix is the translation layer.
How to use this
Read it in either direction. Coming from Temporal, the middle column tells you what each pattern buys you in an agent. Coming from an agent problem, scan the middle column and it names the pattern you want.
The mapping is not total, and the gaps are worth naming: they are where agents genuinely differ from ordinary distributed systems.
Nondeterminism is inside the unit of work. Temporal's model assumes activities are nondeterministic and workflows are not. An agent puts the nondeterminism at the center of the decision-making: the model chooses which activity runs next. Everything about determinism in this book is about keeping that choice recorded rather than recomputed.
Correctness is not binary. A Temporal activity succeeds or fails. An agent turn can succeed and still be wrong, which no retry policy detects. That gap is what Part XIV exists to fill.
Cost is a first-class failure mode. A retry loop in a conventional system wastes CPU. A retry loop around a model call spends money at a rate worth alerting on. See Cost Engineering.