Writing the novel.
Keeping the story behind it.

A manuscript was only part of the work.

As a new novelist developing Sovereign Mercy for TheInnocenceProtocol.com, Rob Wescott needed more than a place to keep the latest chapter. The work also included earlier drafts, author comments, research and reference material, editorial suggestions, and decisions about what belonged in the story.

When a passage changed, its history still mattered. Had a comment already been addressed? Which version had the reader seen? Where had a story fact come from? Which suggestions had Rob accepted, revised or left unresolved?

Rob built PennedCanon around those questions. His aim was to develop the manuscript while retaining a record of how it took shape—particularly if he later needed to explain his process to a publisher or provide information relevant to a copyright review.

01 · Saved provenance

Keep the revision and the reason.

For this project, provenance means being able to trace saved work back to the material and decisions behind it. Earlier manuscript versions, comments and revision evidence remain useful even after the current text moves on.

The reconciliation workflow compared comments with revised prose rather than assuming every old comment still required a change. Proposed edits were brought back to Rob for approval. After an approved revision was saved, its supporting review record could point to the relevant version.

This distinction matters: a suggestion, an author’s decision and the resulting prose are different parts of the process. Keeping them connected makes it possible to revisit a change without relying entirely on memory.

PennedCanon’s Authorship Evidence Package is designed to gather available records for a selected saved version. The value is in making those records understandable, including known gaps; it is not a claim that every step outside the system has been captured.

02 · Apple Books annotations

Read like a reader. Return with an editor’s notes.

Rob wanted the familiar experience of reading in Apple Books on his iPhone: highlight a passage when something feels wrong, add a note, and keep reading.

For Sovereign Mercy, those annotations became inputs to the revision process. Notes were brought into PennedCanon, checked against the manuscript and reviewed before changes were applied. An annotation that did not match cleanly needed attention rather than being silently discarded.

One concrete example involved clothing continuity across Chapters 1 and 2. The review coordinated the references to a coat left at security and the clothing worn afterward. The notes were then linked to the saved revisions that addressed them.

Apple Books is an optional EPUB workflow. In the tested workflow, importing a revised EPUB created a separate book; annotations did not automatically move to the new edition. PennedCanon retains the imported feedback and revision links. Its web reader provides an alternative for reviewing one current manuscript with version-linked notes.

A result that can be traced.

The practical benefit was a connection between reading and revision: a concern raised while reading could become a reviewed change, while the earlier note and its evidence remained part of the project’s history.

Records to explain the work.

PennedCanon was built to help retain and organize the history of a writing process. Saved records can support an explanation of sources, revisions, recorded assistance and author decisions.

They do not independently establish originality, prove authorship or ownership, determine copyrightability, or guarantee registration or publication. Imported history may be incomplete, and missing records do not establish that no outside assistance was used.