A model call answers one question. Real work needs many steps: some in order, some at the same time, some waiting for a person, some repeated after a failure. This site starts from sequence, branch and loop and climbs, one idea at a time, to durable workflows with several agents and a human approval, asking one question at each step: who decides what runs next here, code or a model?
An underwriting quote needs intake, a roof assessment, retrieval of the policy, a recommendation and an underwriter's approval. Hand all of it to one agent loop and nobody can say why a step ran twice or never ran. Hard-code all of it and the flexible part of the work has nowhere to go. Orchestration is the design of that choice, step by step.
Sequence, branch and loop as primitives; DAGs, events and agent loops; one agent with tools against several specialized agents.
Supervisor, planner and executor, router, peer patterns; control plane against data plane; queues, fan-out and fan-in.
Human approval with suspend and resume, durable workflows with checkpoints and compensation, budgets, permissions and termination.
How failures propagate, breakers and fallback routes, trace propagation across agents, and tests that cover every state transition.