BureauzillaGrounding Bureaucracy Agents on a Knowledge Base
How retrieval-grounded agents avoid inventing Fristen: cite the notice, cite the KB article, refuse when evidence is missing.
Un-grounded agents invent deadlines. Grounded agents retrieve, then draft. For freelancer bureaucracy, that means two corpora:
- Your vault — this year’s Bescheide, 1099s, receipts, KK letters.
- Product knowledge — playbooks for DE/US letter types, estimated tax calendars, HITL rules.
The citation rule
If the draft claims a Zahlungsfrist or a balance due, it must point at:
- a page in the attached notice PDF, or
- a vault document the vault agent matched, or
- a knowledge-base chunk with a stable id
No citation → no claim. The compliance gate should block stamp-ready status until evidence exists.
What retrieval is for (and not for)
| Use retrieval for | Do not use retrieval for | | --- | --- | | Matching letter type to a playbook | Choosing tax elections | | Surfacing “what docs usually belong on this case” | Computing penalties you cannot prove | | Linking IRS/Finanzamt process articles | Pretending to be your Steuerberater / CPA |
Official process pages still win over blog memory. Example: IRS Understanding your IRS notice or letter.
Product shape
Bureauzilla’s knowledge base is built for search-and-cite inside the agent loop — not as a second chatbot. Cases stay primary. KB chunks are evidence.