Our summary
Procurement Mind helps Estonian public buyers prepare documents and supplier lists. Alvar Laigna describes adding Jev for small decisions: where a message belongs, which passages answer a question, and which purchasing codes fit. The app still uses a language model to plan and draft.
For message routing, both models start together. A sufficiently certain Jev answer can take the fast path; otherwise the planner continues. Some planner calls finish anyway to compare their choices. Each decision can be active, checked without acting, or switched off, and direct names are replaced before text leaves.
The first week covered only sixty decisions, mostly internal testing, with eleven confident routing agreements. Agreement with the planner is not proof that either route is correct. Faster routing does not establish better procurement documents, and stronger Estonian support and an EU service region remained open concerns.
Key takeaways
- Run a fast router beside the planner rather than adding another wait in front of it.
- Keep comparing decisions after launch and make each new path easy to disable.
- Keep legal and workflow authority with trusted rules and people, not an AI probability.