Start the task described by “manuscript text editor chapter management” by controlling the sample: make the chapter register—not filenames—the authority for status and recovery. The controlled case is twelve chapters C01–C12 in draft, revision, and accepted states. A pass must demonstrate this outcome: complete the article-specific sample with separate evidence for chapter ID, status, authoritative path, next action, next-day recovery. The excluded range is stated separately: plot design, collaborative editing, other layout modes, and EPUB output.
Decision: Make the chapter register—not filenames—the authority for status and recovery
Make the authoritative input and its state visible before work spreads across copies. The register must still identify chapter ID and next-day recovery when the next session begins.
The article-specific evidence card has these fields: chapter ID, status, authoritative path, next action, next-day recovery. Do not count the following excluded range as evidence: plot design, collaborative editing, other layout modes, and EPUB output.
The exact sample and its return path
Give twelve chapter files stable IDs C01–C12 and keep status, authoritative path, and next action in a chapter register. Open only the three chapters scheduled today, update their states at shutdown, and restore the same three from the register tomorrow. Filenames alone, two authoritative copies, or a missing next action fails recovery.
This case addresses the failure behind the search: losing the authoritative input or acceptance evidence while trying to make the chapter register—not filenames—the authority for status and recovery. 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 stable IDs to twelve chapters. Attach the observed chapter ID evidence to this step.
- 2. Record status and path. Attach the observed status evidence to this step.
- 3. Open only today's three chapters. Attach the observed authoritative path evidence to this step.
- 4. Update status and next action at shutdown. Attach the observed next action evidence to this step.
- 5. Restore the same three from the register next day. Attach the observed next-day recovery 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 filenames alone express status.
- Status — expected state: written before the run; hold the row if two copies claim authority.
- Authoritative path — expected state: written before the run; hold the row if the next action is missing next day.
- Next action — expected state: written before the run; hold the row if filenames alone express status.
- Next-day recovery — expected state: written before the run; hold the row if two copies claim authority.
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. Filenames alone express status; preserve the failed artifact.
- 2. Two copies claim authority; change only the responsible condition.
- 3. The next action is missing next day; return to the named source.
A product check without a performance claim
Current product documentation covers capabilities relevant when you need to assign manuscript and reference roles across workspace tabs, panes, and saved layouts. That scope can justify a trial, but it does not show that twelve chapters C01–C12 in draft, revision, and accepted states passed this article's acceptance card.
Rune Studio is a plausible candidate when fewer source, setting, or reference handoffs help you make the chapter register—not filenames—the authority for status and recovery. Use another tool or destination check for the excluded range stated here: plot design, collaborative editing, other layout modes, and EPUB output.
First task
For the search phrase “manuscript text editor chapter management,” the conclusion is to make the chapter register—not filenames—the authority for status and recovery. The result is accepted only when the record establishes this outcome: complete the article-specific sample with separate evidence for chapter ID, status, authoritative path, next action, next-day recovery.
Begin here: add status and next action to a C01–C12 register. If filenames alone express status, 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.
