Before opening a tool for the task behind “self publish ebook novel,” settle one point: pair chapter IDs, manuscript revisions, setting revisions, and build IDs. The controlled case is five chapters moving from draft v01 through submission candidate v03, with settings and EPUB build IDs recorded at each accepted stage. A pass must demonstrate this outcome: complete the article-specific sample with separate evidence for chapter ID, manuscript revision, settings revision, build ID, revision history. The excluded range is stated separately: novel-writing technique, cover design, and retailer submission.
Decision: Pair chapter IDs, manuscript revisions, setting revisions, and build IDs
Make the authoritative input and its state visible before work spreads across copies. The register must still identify chapter ID and revision history when the next session begins.
The article-specific evidence card has these fields: chapter ID, manuscript revision, settings revision, build ID, revision history. Do not count the following excluded range as evidence: novel-writing technique, cover design, and retailer submission.
The exact sample and its return path
Give five chapters fixed IDs, carry the manuscript from draft v01 through submission candidate v03, pair each accepted manuscript state with its settings revision, and give every EPUB a build ID. Change one chapter through v02 to v03, regenerate under a new build ID, and verify the history. Reject any workflow that leaves several files named final, cannot trace a build to its source revision, or inspects an old EPUB after the revision.
This case addresses the failure behind the search: losing the authoritative input or acceptance evidence while trying to pair chapter IDs, manuscript revisions, setting revisions, and build IDs. 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.
From controlled input to second check
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 stable IDs to five chapters. Attach the observed chapter ID evidence to this step.
- 2. Copy the draft as v01. Attach the observed manuscript revision evidence to this step.
- 3. Build with settings s01. Attach the observed settings revision evidence to this step.
- 4. Revise one chapter through v02 to candidate v03. Attach the observed build ID evidence to this step.
- 5. Regenerate under a new build ID and trace the history. Attach the observed revision history evidence to this step.
Acceptance fields
Do not infer one row from another. Record pass, revision, or not tested beside the actual target, date, output path or artifact ID.
- Chapter ID — expected state: written before the run; hold the row if several files are called final.
- Manuscript revision — expected state: written before the run; hold the row if a build cannot be traced to its manuscript.
- Settings revision — expected state: written before the run; hold the row if QA inspects the old EPUB after revision.
- Build ID — expected state: written before the run; hold the row if several files are called final.
- Revision history — expected state: written before the run; hold the row if a build cannot be traced to its manuscript.
Three failures that invalidate the run
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. Several files are called final; preserve the failed artifact.
- 2. A build cannot be traced to its manuscript; change only the responsible condition.
- 3. QA inspects the old EPUB after revision; return to the named source.
Separate product scope from your result
Current product documentation covers capabilities relevant when you need to keep manuscript, order, metadata, navigation, cover, and colophon in one production record. That scope can justify a trial, but it does not show that five chapters moving from draft v01 through submission candidate v03, with settings and EPUB build IDs recorded at each accepted stage passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you pair chapter IDs, manuscript revisions, setting revisions, and build IDs. Use another tool or destination check for the excluded range stated here: novel-writing technique, cover design, and retailer submission.
First task
For the search phrase “self publish ebook novel,” the conclusion is to pair chapter IDs, manuscript revisions, setting revisions, and build IDs. The result is accepted only when the record establishes this outcome: complete the article-specific sample with separate evidence for chapter ID, manuscript revision, settings revision, build ID, revision history.
Begin here: create one four-part ID for source, settings, chapter, and build. If several files are called final, 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.
