The deciding move behind the search “beginner EPUB creation method” is not another feature: add a second regeneration pass to the six-step beginner workflow. The controlled case is a two-chapter sample with one input-and-settings record. A pass must demonstrate this outcome: complete the article-specific sample with separate evidence for input record, chapter order, metadata, first build, one-character revision, second-build match. The excluded range is stated separately: cover production, KDP submission, and other layout modes.
Decision: Add a second regeneration pass to the six-step beginner workflow
Close one checkpoint only when its input and result can be named. Reaching a build screen does not prove input record, second-build match, or the stages between them.
The article-specific evidence card has these fields: input record, chapter order, metadata, first build, one-character revision, second-build match. Do not count the following excluded range as evidence: cover production, KDP submission, and other layout modes.
Keep this case tied to its source
Record the input and settings for a two-chapter beginner sample, freeze chapter order, and inspect the first EPUB. Change one character in the source, regenerate from the same settings, and compare the two builds. Missing settings, confusing an old file with the second build, or unrelated changes to metadata or order prevents acceptance.
This case addresses the failure behind the search: losing the authoritative input or acceptance evidence while trying to add a second regeneration pass to the six-step beginner workflow. 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.
Operation order
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. Record input and settings on one card. Attach the observed input record evidence to this step.
- 2. Freeze the two-chapter order. Attach the observed chapter order evidence to this step.
- 3. Generate and inspect build one. Attach the observed metadata evidence to this step.
- 4. Change one character in source. Attach the observed first build evidence to this step.
- 5. Rebuild from the same settings and compare. Attach the observed one-character revision evidence to this step.
What each row must prove
Do not infer one row from another. Record pass, revision, or not tested beside the actual target, date, output path or artifact ID.
- Input record — expected state: written before the run; hold the row if settings are not recorded.
- Chapter order — expected state: written before the run; hold the row if an old EPUB is mistaken for build two.
- Metadata — expected state: written before the run; hold the row if metadata or order changes with the character edit.
- First build — expected state: written before the run; hold the row if settings are not recorded.
- One-character revision — expected state: written before the run; hold the row if an old EPUB is mistaken for build two.
- Second-build match — expected state: written before the run; hold the row if metadata or order changes with the character edit.
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. Settings are not recorded; preserve the failed artifact.
- 2. An old EPUB is mistaken for build two; change only the responsible condition.
- 3. Metadata or order changes with the character edit; return to the named source.
Where Rune Studio may reduce handoffs
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 two-chapter sample with one input-and-settings record passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you add a second regeneration pass to the six-step beginner workflow. Use another tool or destination check for the excluded range stated here: cover production, KDP submission, and other layout modes.
Next action
For the search phrase “beginner EPUB creation method,” the conclusion is to add a second regeneration pass to the six-step beginner workflow. The result is accepted only when the record establishes this outcome: complete the article-specific sample with separate evidence for input record, chapter order, metadata, first build, one-character revision, second-build match.
Begin here: prepare a two-chapter sample and two build-ID fields. If settings are not recorded, 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.
