When the problem described by “beginner EPUB workflow” becomes confusing, return to this decision: record status, authoritative source, and next action for every deliverable. The controlled case is a four-chapter collection with two inline images and one cover. A pass must demonstrate this outcome: reach a finished EPUB with each deliverable marked pending, active, or verified. The excluded range is stated separately: direct package repair and retailer-page setup are outside the roadmap.
Decision: Record status, authoritative source, and next action for every deliverable
Make the authoritative input and its state visible before work spreads across copies. The register must still identify body and reader check when the next session begins.
The article-specific evidence card has these fields: body, images, reading order, metadata, generated package, reader check. Do not count the following excluded range as evidence: direct package repair and retailer-page setup are outside the roadmap.
What the controlled material must reveal
Use a four-chapter collection with two inline images and one cover. The decisive fields are body, images, reading order, metadata, generated package, reader check; keep the three stop conditions visible throughout the run.
This case addresses the failure behind the search: tracking manuscript, images, navigation, and metadata only from memory. 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.
A reproducible first pass
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. List six deliverables. Attach the observed body evidence to this step.
- 2. Assign one authoritative path to each. Attach the observed images evidence to this step.
- 3. Separate unverified from verified. Attach the observed reading order evidence to this step.
- 4. Return package inspection results to the list. Attach the observed metadata evidence to this step.
- 5. Resume next day from the list alone. Attach the observed generated package evidence to this step.
Pass, revision, or not tested
Do not infer one row from another. Record pass, revision, or not tested beside the actual target, date, output path or artifact ID.
- Body — expected state: written before the run; hold the row if an image exists but is not referenced.
- Images — expected state: written before the run; hold the row if navigation and reading order share an ambiguous field.
- Reading order — expected state: written before the run; hold the row if an untested reader is marked as passed.
- Metadata — expected state: written before the run; hold the row if an image exists but is not referenced.
- Generated package — expected state: written before the run; hold the row if navigation and reading order share an ambiguous field.
- Reader check — expected state: written before the run; hold the row if an untested reader is marked as passed.
Failures that need separate returns
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. An image exists but is not referenced; preserve the failed artifact.
- 2. Navigation and reading order share an ambiguous field; change only the responsible condition.
- 3. An untested reader is marked as passed; return to the named source.
A product check without a performance claim
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 a four-chapter collection with two inline images and one cover passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you record status, authoritative source, and next action for every deliverable. Use another tool or destination check for the excluded range stated here: direct package repair and retailer-page setup are outside the roadmap.
Next action
For the search phrase “beginner EPUB workflow,” the conclusion is to record status, authoritative source, and next action for every deliverable. The result is accepted only when the record establishes this outcome: reach a finished EPUB with each deliverable marked pending, active, or verified.
Begin here: create one sheet with the state and source of all six deliverables. If an image exists but is not referenced, 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.
