A repeatable answer to “EPUB generate workflow” depends on this choice: verify command status and artifact inspection in separate acceptance rows. The controlled case is a two-chapter input with a recorded SHA and fixed build timestamp. A pass must demonstrate this outcome: complete the article-specific sample with separate evidence for input SHA, exit status, artifact path, EPUB validity, regeneration difference. The excluded range is stated separately: GUI interaction feel, KDP acceptance, and Japanese vertical layout.
Decision: Verify command status and artifact inspection in separate acceptance rows
Close one checkpoint only when its input and result can be named. Reaching a build screen does not prove input SHA, regeneration difference, or the stages between them.
The article-specific evidence card has these fields: input SHA, exit status, artifact path, EPUB validity, regeneration difference. Do not count the following excluded range as evidence: GUI interaction feel, KDP acceptance, and Japanese vertical layout.
The acceptance case for this search
Record the SHA of a two-chapter input, run generation with a fixed timestamp, and preserve exit code and output path. Inspect validity and chapter order, then change one sentence and generate under a new artifact ID. A success response without an artifact, inspection of an old file, or an untraceable second input/output pair does not pass.
This case addresses the failure behind the search: losing the authoritative input or acceptance evidence while trying to verify command status and artifact inspection in separate acceptance rows. 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 the input SHA. Attach the observed input SHA evidence to this step.
- 2. Generate with a fixed timestamp. Attach the observed exit status evidence to this step.
- 3. Preserve status and artifact path. Attach the observed artifact path evidence to this step.
- 4. Inspect validity and order. Attach the observed EPUB validity evidence to this step.
- 5. Change one sentence and build under a new ID. Attach the observed regeneration difference 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.
- Input SHA — expected state: written before the run; hold the row if success is reported without an artifact.
- Exit status — expected state: written before the run; hold the row if an old artifact is inspected.
- Artifact path — expected state: written before the run; hold the row if build two cannot be linked to its input SHA.
- EPUB validity — expected state: written before the run; hold the row if success is reported without an artifact.
- Regeneration difference — expected state: written before the run; hold the row if an old artifact is inspected.
Stop conditions and repair routes
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. Success is reported without an artifact; return to the named source.
- 2. An old artifact is inspected; preserve the failed artifact.
- 3. Build two cannot be linked to its input SHA; change only the responsible condition.
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 two-chapter input with a recorded SHA and fixed build timestamp passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you verify command status and artifact inspection in separate acceptance rows. Use another tool or destination check for the excluded range stated here: GUI interaction feel, KDP acceptance, and Japanese vertical layout.
Conclusion
For the search phrase “EPUB generate workflow,” the conclusion is to verify command status and artifact inspection in separate acceptance rows. The result is accepted only when the record establishes this outcome: complete the article-specific sample with separate evidence for input SHA, exit status, artifact path, EPUB validity, regeneration difference.
Begin here: prepare one record for SHA, status, path, validity, and diff. If success is reported without an artifact, 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.
