My supervisor-worker agent pattern fixed the dumbest bug in my automation stack at 1:13 AM

Описание и применение

Паттерн супервизора‑работника устранил ошибку с возвратом средств, улучшил трассировку и упрощённую архитектуру автоматизации.

Задача

A single, monolithic agent performed multiple tool calls in a chaotic order, causing a refund email to be drafted before Stripe eligibility checks completed, leading to failures and hard-to-debug sequencing bugs.

Результат

The supervisor-worker pattern eliminated the refund bug, improved traceability, and made the automation stack easier to reason about under pressure.

Рабочий процесс

• 1. Supervisor receives task and checks state
• 2. If not enriched, hand off to enrichment worker
• 3. Enrichment worker fetches Stripe/CRM data and marks state as enriched
• 4. Supervisor routes to validation worker
• 5. Validation worker checks refund policy, sets eligibility and approved_for_execution flags
• 6. Supervisor routes to drafting worker
• 7. Drafting worker generates email if eligible, else drafts explanation
• 8. Supervisor routes to execution worker
• 9. Execution worker sends email or updates CRM
• 10. Supervisor ends workflow

Доказательства

That change fixed more than the refund bug. It made the whole automation stack easier to reason about.

Источник

One giant tool‑calling agent works just long enough to feel smart.

Источник