Technical reports

Omegi · Lab

Technical reports

We build an agentic system that reads classic novels into a library of story parts and that plans and writes long audio serials. We publish what we learn as technical reports. Each report asks one question. It gives its method at a fixed commit, its results with their scope and the results that failed. Before we publish a report, a fresh copy of the code at that commit must give the same numbers. Two referees read it first. We aim for one report each month.

Reports

Our first report is in preparation for November 2026.

Each report uses only novels from before 1931 and our own pages. A correction is a new version. We keep each version at its own address.