BureauzillaMulti-Agent Triage: Inbox to Case to Draft to Stamp
How agentic bureaucracy stacks work: specialist agents, shared case state, traces, and HITL before outbound for DE and US freelancers.
One mega-prompt that “handles all Behörden mail” fails the first contradictory letter. A multi-agent layout splits work the way a good Ops desk does.
Roles that earn their keep
- Inbox agent — classify sender (Finanzamt / IRS / KK / landlord), extract deadline, attach PDF.
- Vault agent — find matching receipts, prior Bescheide, 1099s.
- Draft agent — propose reply text with citations from the knowledge base.
- Compliance gate — refuse outbound without human stamp; log the refusal.
Shared state is the case, not a chat scrollback. Traces record which agent moved which field.
Why this beats a single chatbot
Chat forgets the Aktenzeichen. Cases do not. Chat invents “I already sent it.” Traces show whether the send happened after your stamp.
For US freelancers, quarterly estimated tax dates and notice response windows are easy to lose in email. IRS pay-as-you-go guidance still expects you to track due dates yourself — agents should surface them on the case, not bury them in a transcript. See Estimated taxes.
DE + US same skeleton
Geography changes forms (ELSTER vs 1040-ES; Krankenkasse vs Marketplace Form 1095-A). The agentic skeleton stays: intercept → surface → draft → stamp.
Design rules that keep multi-agent honest
- One write path to the case — agents propose field updates; the case is the source of truth.
- Citations or no claim — deadline and amount fields should point at a page in the PDF or a vault doc.
- Hard stop on send — compliance is a gate, not a suggestion.
- Human-readable traces — if you cannot explain who did what, you cannot defend the audit trail.