When the problem described by “build EPUB novel” becomes confusing, return to this decision: record filenames separately from reading order. The controlled case is eight items: a title page, preface, four body chapters, afterword, and colophon. A pass must demonstrate this outcome: complete the article-specific sample with separate evidence for role ID, filename, spine order, navigation inclusion, regeneration. The excluded range is stated separately: novel-writing technique, Japanese vertical layout, and sales.
Decision: Record filenames separately from reading order
Make the authoritative input and its state visible before work spreads across copies. The register must still identify role ID and regeneration when the next session begins.
The article-specific evidence card has these fields: role ID, filename, spine order, navigation inclusion, regeneration. Do not count the following excluded range as evidence: novel-writing technique, Japanese vertical layout, and sales.
The acceptance case for this search
Assign role IDs to eight items—a title page, preface, four body chapters, afterword, and colophon—while keeping filenames separate from reading order. Choose navigation inclusion, compare nav with spine, move the preface in the order record, and regenerate. Alphabetical filename order, an accidental colophon entry in navigation, or direct package reordering is a failure.
This case addresses the failure behind the search: losing the authoritative input or acceptance evidence while trying to record filenames separately from reading order. Name the source, working copy, and delivered or reopened result so that another editor can locate each one without relying on a filename such as final.
Run order and evidence
Use the following product-independent sequence on the named sample. It is an acceptance method, not a claim that Rune Studio has already completed this particular case.
- 1. Assign role IDs to eight content roles. Attach the observed role ID evidence to this step.
- 2. Separate filenames from reading order. Attach the observed filename evidence to this step.
- 3. Choose navigation entries. Attach the observed spine order evidence to this step.
- 4. Compare EPUB nav with spine. Attach the observed navigation inclusion evidence to this step.
- 5. Move the preface in the order record and rebuild. Attach the observed regeneration evidence to this step.
The result card
Do not infer one row from another. Record pass, revision, or not tested beside the actual target, date, output path or artifact ID.
- Role ID — expected state: written before the run; hold the row if alphabetical filenames decide order.
- Filename — expected state: written before the run; hold the row if the colophon enters navigation accidentally.
- Spine order — expected state: written before the run; hold the row if order is changed directly in the package.
- Navigation inclusion — expected state: written before the run; hold the row if alphabetical filenames decide order.
- Regeneration — expected state: written before the run; hold the row if the colophon enters navigation accidentally.
Second-pass rejection rules
A second pass is meaningful only when its source and changed condition remain identifiable. Keep the earlier result and append the retest instead of replacing the failed row.
- 1. Alphabetical filenames decide order; change only the responsible condition.
- 2. The colophon enters navigation accidentally; return to the named source.
- 3. Order is changed directly in the package; preserve the failed artifact.
Separate product scope from your result
Current product documentation covers capabilities relevant when you need to preserve manuscript order and metadata, generate EPUB 3, and inspect the resulting structure. That scope can justify a trial, but it does not show that eight items: a title page, preface, four body chapters, afterword, and colophon passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you record filenames separately from reading order. Use another tool or destination check for the excluded range stated here: novel-writing technique, Japanese vertical layout, and sales.
What to do today
For the search phrase “build EPUB novel,” the conclusion is to record filenames separately from reading order. The result is accepted only when the record establishes this outcome: complete the article-specific sample with separate evidence for role ID, filename, spine order, navigation inclusion, regeneration.
Begin here: create a role-ID and reading-order table. If alphabetical filenames decide order, stop at that row and return to its source. Check the Rune Studio product page for the current Mac feature scope before applying the same acceptance card to a product trial.
