OTO
deployment · from ARCHITECTURE.md at v0.6.1

Dependencies, on purpose

compile and servethe standard library only: no model, no package, nothing to keep alive
intakeoptional parsers for PDF, Word, slides, spreadsheets, HTML
draft · bench · neo4joptional extras: one model call, an embedding baseline, a driver
The build path needs nothing. Everything else is an extra you choose.

The compile and serve paths use the standard library only, and CI asserts that a bare install pulls in nothing. Document parsers live in the intake extra, the embedding baseline in bench, and the Anthropic SDK in draft, used by oto draft alone.

The engine must never need a model to answer a question; a test asserts the SDK is not imported by anything but the drafter.