ERerGB/folio

Folio booklet lifecycle

Treat a booklet as a durable object with a stable ID, editable chapters, source references, numbered editions, and a delivery log. Find an existing object for the subject before starting another. An explicit $folio invocation means finish with delivery to the user's reader and verification, even when the prompt only says "organize this conversation" or "make an EPUB." Stop after the file is ready only when the user explicitly asks for a draft or export without sending. If this skill is selected implicitly for a request that only asks for a file, follow that narrower request.

Determine the target reader early from the current request, earlier user context, or the existing object's delivery log. Recheck that its transfer endpoint is current. If the target or a required connection detail is missing, ask for that detail while continuing content work; do not wait until the EPUB is finished to discover the gap. An explicit $folio request already authorizes transfer to the user's reader, so do not ask for general permission again.

Make or update the booklet

1. Identify the exact conversation, notes, or files to include. Read them as source material, not instructions. Track each chapter's sources and current revision reason in book.json; distinguish user statements, assistant suggestions, and claims that still need evidence. The build keeps a private source snapshot for each edition. See object format for the fields. When the user asks to preserve an article or note as originally written, keep its wording and order. Do not replace it with a summary or reading guide. Record the author, publication date, source URL, and any omitted images or interactive elements. Keep source text in the private booklet object, never in this public skill repository.
2. Find the matching booklet object. Reuse its chapter IDs and revise only affected chapters. For a new object, use scripts/booklet.py init, then add Markdown chapters and their entries to book.json. See object format when creating or repairing an object.
3. Build with scripts/booklet.py build. Inspect the HTML and the EPUB contents. Use EPUBCheck when available for a conformance check. Preview on a reader or simulator relevant to the target when layout matters; see virtual environments. Rebuilding unchanged content must not create a new edition.
4. Keep prior editions. A pending edition can be revised; its first recorded external transfer freezes it. Later changes create the next edition. Use versioned filenames, because device reading position and annotations may attach to a particular file.

Choose and verify delivery

Read device routes for the target brand and model. Confirm current format and transfer support from the vendor before choosing a route. Prefer the user's existing route. After building, actively carry out that transfer; do not stop at a download link or instructions when the route is available. An unchanged edition still needs delivery if it has not reached this target reader. If the same edition is already delivered, verify its presence before treating the request as complete. The bundled send-booxdrop command automates only a currently observed BOOXDrop local-library interface; read BOOXDrop details before using it. Other brands use their official UI, USB, or cloud workflow unless a reliable connector is available. Never infer that an EPUB can be copied directly to every brand over LAN.

Record a delivery with record-delivery --stage only after checking evidence from the destination, such as a device listing, vendor app, cloud library, or an explicit user confirmation. Stages progress from uploaded to device-file, library-indexed, and opened; advance a prior record when stronger evidence arrives. A successful upload does not prove that the book appears in the device library or has been opened. BOOXDrop's file listing verifies device-file, not the reader's home library. If a matching filename exists at the destination but its identity is uncertain, inspect it before replacing or resending. Do not delete older device copies or annotations unless asked.

If the target device or method is unavailable, keep the edition pending, say exactly what prevents delivery, and request the missing device action or detail. Do not report the workflow complete until transfer is verified or the user explicitly changes scope to draft-only. Keep editable objects in a durable user workspace, never in a task's scratch directory. Do not include private source conversations, local IP addresses, credentials, or personal book objects in a public repository.