Why the engine stays Python
Decision. Every check the site shows will be computed by the citecheck
Python package, called through a thin FastAPI service. The site will never
re-implement a check in TypeScript.
Why. The accuracy numbers the site publishes will be measured on the
Python package. If the site ran a TypeScript port, those numbers would
describe different code. Pinning the package version in api/pyproject.toml, and
showing that version in the site footer, makes the link checkable.
What I rejected.
- A browser-only build. It would keep keys entirely in the browser and need no backend. It would also mean a second implementation of citation parsing, quote matching and the support check, with no benchmark behind it.
- Calling Anthropic directly from the browser for the support check only. It splits one pipeline across two languages for a privacy gain I can state honestly another way (see "Where your key goes").
Cost. Keys pass through a server function. Request bodies are capped at 4.5 MB, so PDFs are read in the browser and only text is sent.