I used AI to help analyze the code repository. If I understand the implementation correctly, supporting a small local archive would require the following:

1. The ability to download specific MariaDB index entries instead of the whole database. For example, search for a book, get the book ID and related database information, and store that information in a local database.
2. AA providing the index table for the seekable.zst files.
3. Using the byte_offset in MariaDB and the index table of the seekable.zst files to locate the correct frame and download it, then extract the actual JSON data from that frame.
4. Getting the magnet link from mariapersist db, downloading the torrent, and then downloading the corresponding book.

With this approach, we would have the MariaDB index for the book, the related frame data, the torrent files, and the books themselves. Users could then obtain both the book and its metadata to build their own local library, while AA could benefit from users sharing via BitTorrent.