The answer depends on how the book was made
There is a meaningful difference between using AI to brainstorm, asking for a rough passage, and publishing an unreviewed output as a finished book. The production record, human contribution, and platform rules all matter.
Do not use a general answer as permission for a specific project. Check the current terms for every store and distributor you plan to use.
Audit the source before you edit the prose
Identify generated sections, borrowed research, quotations, images, translations, and client-owned material. Remove anything you cannot license or verify, and record what still needs an answer.
Awtter's Import, Research, Bookmarks, and Notepad tools help keep that audit beside the document instead of in a forgotten email.
Make the book better than its first output
Read for structure, continuity, voice, accuracy, and reader value. Add original examples and experience. Challenge generic claims. Have another person review important chapters.
Use the Binder to work section by section, Clean to remove mechanical residue, and Organize to find every place a term or fact appears.
Keep proof of the final decision
Save a snapshot before release, preserve the selected compile preset, and keep the final export package. If a platform asks a question later, you should be able to explain what you published and why.
Awtter's History and Publish views turn that final check into a repeatable release step.