ZaimuTomo
A personal accounting application and a practical testbed for LLM-assisted document workflows.
The invoice pipeline converts source documents into text, extracts structured accounting data, and runs a separate model-based verification pass against the source. Deterministic rules handle formats and accounting constraints. Unsupported, contradicted, or ambiguous fields are routed to human review.
The question: how do you make uncertainty an explicit part of the workflow instead of hiding it behind a confident model response?
- Elixir / Phoenix
- PostgreSQL
- LLM evaluation
- Langfuse