Articles on Tetrak OCR

Armenian OCR: the engines, the numbers, and our first training run

Sun, 30 Aug 2026 00:00:00 +0000

Tetrak’s central idea is that you should not have to pick an OCR engine. The pipeline fans a document out across every local engine eligible to read it, scores the transcripts against each other without a reference, and keeps the best one. On our English corpus of Los Angeles stage and picture-palace ephemera that works: different engines win on different documents, and routing beats any single choice. The research is the measured version of that argument.

What we will be writing about

Sat, 29 Aug 2026 00:00:00 +0000

The documentation on this site answers the questions a person has once they have decided to try Tetrak. What it installs, what the flags do, what the engines are, what the benchmark measured. It is deliberately static: the research pages are regenerated from the harness, so the figures on them cannot drift away from the data, and the reference pages describe a surface that only changes when the code does.

None of that is a good home for an argument, or for a note about something that did not work. This section is.