Reference

The detail behind the research: the corpus itself, what each engine does and does not do, how routing decides, and the command line.

• The corpus — nine items of Los Angeles stage and picture-palace ephemera, with provenance and rights for every one.
• The engines — each backend’s measured strengths, constraints and honest failure cases, including multi-page TIFF handling.
• Routing — the fan-out decision table, the auto-configuration bands, the quality score and the triage gate.
• Command line — every command and flag.
• Python API — generated from the package’s own docstrings.
• Licensing — the MIT/CC-BY split covering the code and the corpus.