2026 · AI automation · Our own system
Lektobot
Lektobot is an AI proofreading agent for Slovene academic documents that Niro Digital is developing in collaboration with Lektoriram.si: it inserted 250 verified comments into a 31,204-word academic thesis in 1 hour 24 minutes.
- Client
- Niro Digital Product
- Industry
- Language Services / Document Automation
- Year
- 2026
- What we did
- AI automation
The constraint
A Slovene proofreader's first pass over an academic thesis means reading tens of thousands of words hunting for missing commas, then typing each finding as a Word comment. It is days of repetitive work, and the part of the job that carries the least judgement. Every tool that offers to take it over has the same flaw: it rewrites the text, and a thesis that comes back with its wording or formatting quietly altered is worse than no help at all. So we are building Lektobot as an annotation-only assistant, in collaboration with Lektoriram.si, the proofreading practice whose site we built in 2023. One model proposes corrections, a second adjudicates every proposal, and deterministic validation re-anchors each surviving suggestion to the exact characters it refers to. The only thing added to the document is Word comments, and an eleven-layer preservation gate has to prove that before release. If it cannot, the file is quarantined and the run exits with an error.
250
31,204
23
400
*Figures from the project's own accounts and dashboards at the time of writing.
The system
- //01A 31,204-word academic thesis proofread in one job, 250 comments inserted and verified
- //02Two passes: one model proposes corrections, a second adjudicates every proposal
- //03Eight commands, bilingual, and a promise in the help text: never edits your file
- //04An offline preflight that prices the job before any model call leaves the machine
- //05Word comments anchored to exact spans, each with a category, rationale and confidence
- //06One deterministic comment template written straight into word/comments.xml
- //07An eleven-layer preservation gate; a failure quarantines the file and exits with an error
- //08400 proposals, 250 released, every drop recorded with a reason code
- //09An independent verify command re-checks any source and output pair from outside
- //10Five review profiles: category count, confidence floor, density budget, anchoring mode
- //11The same production run figures, readable on a phone
What changed
- //01250 verified comments on a 31,204-word academic thesis in 1 hour 24 minutes
- //02400 proposals entered the funnel, every drop recorded with a reason
- //03The audit report holds hashes, costs and versions, no manuscript text
- //04Any output file can be verified against its source years later
What we'd do differently
Lektobot is a tool we are developing in collaboration with Lektoriram.si, not a finished product on sale. It does the first pass, not the proofreading — every comment is still a suggestion for the human expert, who has the final word. The run figures come from a single job on a single thesis, and we have no figure for how many of the 250 comments the proofreader kept, so we do not quote one. What we would do differently: we built an Electron review console before the preservation gate was finished and ended up deleting it. The gate should have come first.
All projects
More work in AI automation
Start here
Tell us the constraint
Operations, workers or customers. One sentence is enough, we'll reply within one working day.