Chapter 3 — Protect the Unfinished

Open a draft halfway through and you will find a character carrying functions they will later shed, claims running ahead of the evidence, a scene that exists only to discover a relationship and will disappear. A contradiction may be an error, or it may be the pressure that shows you the Work’s center.

An unfinished Work is a different kind of object from a finished one with pages missing. Its meaning may still be unstable, and it needs the freedom to be wrong in private, because a system that treats every state as public, searchable or permanent changes what you can safely attempt inside it.

Share early and you often get answers to a version you haven’t chosen yet. Praise sticks to material that may have to go, and public commitment makes reversing course feel like embarrassment. Early sharing can still be worth it if you chose it. A trusted reader may show you where curiosity drops, or a subject expert knock out a false assumption.

Protection means boundaries that fit how mature and sensitive the Work is, and they cover more than who can open a file. A manuscript can be technically private while its content is copied into third-party tools, kept in chat histories or visible to platform operators. Interface privacy and architectural privacy are different things, and you should know which one you have:

• Where does the plaintext exist?
• What is stored after the action ends?
• Is content used for training or secondary purposes?
• Which metadata remains visible even when content is encrypted?

Every tool leaves some risk behind. A browser, a collaborator, a screenshot or an authorized processing session can expose content, so honest privacy is a clear account of boundaries and limits rather than an absolute promise.

Authors also get encouraged to narrate the process in public, announcing the project, sharing daily counts and making the road to completion into content. That can build community and accountability. It can also make the performance a second work with demands of its own, in which quiet, difficult stretches look unproductive because they produce nothing to show and a change of direction becomes a branding problem. Protecting the unfinished may then mean declining to announce a title, keeping your word count to yourself, or inviting three readers instead of three thousand followers.

Protection also makes courage possible. A novelist can write the cruel version of a scene to understand a character without committing to publish it. A memoirist can set down an angry memory before deciding what is fair.

It matters more when the Work concerns other people. You own your expression; you do not own every consequence of disclosing it. Your private notes may hold allegations, medical details or material entrusted to you under a different expectation. Sort out what should never enter a casual tool, what needs consent and what may need legal or ethical review before publication.

Scope collaborative access as well. An editor may need a chapter and can leave the research archive alone. A beta reader may need a watermarked edition and a clear request rather than permanent workspace membership. The more complete the system, the easier it is to overshare by granting access to the container instead of the material someone needs.

Disclosure is a decision you author. A Work moves from private exploration through selected collaboration and a review edition to a public edition, and each transition should be explicit. Publication makes a public artifact from selected, reviewed material. It should never happen because a permission setting on the same object was flipped by accident.

Reflection

• Who can currently see this Work?
• Which tools receive plaintext from it?
• What are you sharing to improve the Work, and what are you sharing to reassure yourself that the Work exists?
• What should a collaborator receive, and what should remain outside their scope?