Practice — Agent Design Patterns: From Workflows to Autonomous Agents (10 questions)
Advanced
Open
Free
Diagnosing the Right Workflow Pattern for a Document-Intake Pipeline Permalink →
A team is building a pipeline that ingests incoming legal documents and needs to: (1) determine which of four document types it is (contract, NDA, invoice, other), (2) run type-specific extraction appropriate to whichever type was found, and (3) have a second LLM call double-check the extracted fields against the source document before anything is written to the database.
- Name the workflow pattern(s) present in this pipeline, stage by stage, and justify each with the distinguishing question for that pattern.
- A colleague argues stage 2 should be "orchestrator-worker" because "a worker handles each type." Explain precisely why that's the wrong name for what's described, and what it would take to actually make it orchestrator-worker.
- Is this pipeline, as a whole, an agent? Justify using the agency-levels framing.
Share this question
Advanced
Open
Pro
Choosing Between Reflexion and ReWOO for a Failing Data-Extraction Agent
Unlock this question →
Advanced
Open
Pro
Is This Evaluator-Optimizer, or Does It Need to Be an Agent?
Unlock this question →
Advanced
Open
Pro
Picking a Pattern for a Meeting-Notes-to-Action-Items Feature
Unlock this question →
Advanced
Open
Pro
ReWOO's Call Arithmetic, and What Its Work Phase Does With an Ambiguous Lookup
Unlock this question →
Advanced
Open
Pro
When Does a Second Round Turn Orchestrator-Worker Into an Agent?
Unlock this question →
Advanced
Open
Pro
Tree Search Over Actions When Some Actions Have Side Effects
Unlock this question →
Advanced
Open
Pro