Agent patterns look new because the model is new. Architecturally, many of them inherit
older software ideas: caches, queues, pipes, workflow engines, event logs, RBAC, sagas,
bulkheads, observability and MapReduce. Hover over a pattern to see the bridge.
Full mapping
Pattern → engineering ancestor → original engineering problem
Canonical distributed patterns and their Agent descendants
GoF assumed a single process. The distributed era replaced that with a different operating assumption:
failure is the default, not the exception. The patterns below are the ones that made it into
production handbooks, vendor APIs and platform engineering. Each one has at least one Agent-era
descendant — sometimes a direct port, sometimes a reframing.
More
Ancestor catalog
This is the larger vocabulary behind the hover cards. The point is not to claim one-to-one
inheritance. The point is to help an Agent architect ask: which old engineering problem is this
new Agent problem secretly replaying?