Rights Before Redesign for AI Children’s Book Second Editions
Gary WhittakerThe Second Edition Author System · Article 2 of 5
Rights Before Redesign
Author, Illustrator, Publisher, and AI Approval Before You Rebuild a Children’s Book
A second edition should not begin with new AI images. It should begin with a clear record of who owns the story, who owns the artwork, who controls the files, and who can approve the new version.
Series Navigation
The Second Edition Author System
This is Article 2 of 5. Start with Article 1 if you have not yet built the public-domain source record. Use this article when the next question is author approval, illustrator rights, publisher files, AI inputs, and second-edition permission.
Article 1
Public Domain Is Not a Permission Slip
Use this first to document the source foundation and avoid treating public domain like a blank check.
Read Article 1Article 2
Rights Before Redesign
Current article. This part checks who can approve the second edition before new AI visuals or production files are created.
You Are HereFollow Articles 3–5
AI Writing Hub
Use the AI Writing hub for the contamination audit, visual-system workflow, and proof/publish/sell parts when their final URLs are live.
Follow the SeriesThe first question is not “Can AI make this look better?”
The first question is:
Who has the right to approve the second edition?
This is where many beginner authors and AI creators move too fast. They see an older book, a public-domain story world, or an existing illustrated draft and immediately think about better art, stronger colors, a new cover, and a fresh KDP upload.
Those steps may come later. But if the book already exists, the creator needs to slow down and identify the rights chain before production begins.
Quick recap from Article 1
In Article 1, we started with the public-domain source record.
The core lesson was simple: public domain can give you a source foundation, but it does not give you permission to use every later adaptation, movie design, stage version, logo, famous line, or branded visual identity connected to that story world.
Article 2 builds on that same idea. Even when the public-domain source is clear, a modern second edition may include modern rights that are not public domain.
That includes the author’s manuscript, the illustrator’s artwork, the first edition layout, the publisher’s files, the ISBN record, and any new AI-assisted production work.
Need the source foundation first?
Read Article 1 and the Oz guide before continuing if the public-domain source record is still unclear.
The case study: why this step matters
This series uses a real Oz-inspired children’s book rebuild as the working case study.
The project already has the main parts beginner authors often overlook: a completed story, interior illustrations, a cover direction, author credit, illustrator credit, and prior publishing language.
That makes it a useful teaching example because a second edition is not the same as starting from a blank page. A second edition asks:
- Who wrote the original text?
- Who illustrated the first version?
- Who prepared or controlled the original files?
- Who published the first edition?
- Who can approve a new edition?
- Who can approve AI-assisted visual production?
- Who can approve the book being sold through KDP, Shopify, or companion products?
If those answers are unclear, the project is not ready for final production.
Public domain does not erase modern rights
This is the key lesson of Article 2.
The original Oz source may be public domain, but a modern Oz-inspired children’s book can still contain protected modern work.
For example, the author’s original story choices may be protected. The illustrator’s drawings may be protected. The book layout may have its own production rights. The first publisher may have records, files, or distribution terms connected to the earlier edition.
Public domain helps with the source foundation. It does not automatically clear the modern book built on top of that foundation.
The four rights layers to check before redesign
A practical second-edition review should separate the project into four layers.
| Rights Layer | What to Check | Why It Matters |
|---|---|---|
| Story rights | Who wrote the manuscript, who owns it, and who can approve edits. | The author’s text is the foundation of the second edition. |
| Illustration rights | Who created the original artwork, what the agreement allowed, and whether the art can be reused, modified, replaced, or used as AI reference. | Artwork rights do not disappear just because new AI tools exist. |
| Publishing rights | Who published the first edition, who controls the files, whether an ISBN was used, and whether any platform or service agreement affects the next version. | The second edition may need new files, new metadata, new publishing records, and a clean release path. |
| AI input and output rights | What images, prompts, documents, sketches, or reference material will be uploaded to AI tools, and whether the creator has permission to use those inputs. | AI platforms can help produce new work, but they do not grant rights to inputs the creator did not control. |
The illustrator question: scene map or AI reference?
This is one of the most important parts of a second-edition rebuild.
If an earlier edition has credited illustrations, those images should not automatically be treated as free training material, style references, image-to-image inputs, or remix material.
There is a major difference between using an old book as a scene map and using old artwork as an AI image reference.
| Use | What It Means | Risk Level |
|---|---|---|
| Scene map | Using the old book to identify story beats, page order, characters, and moments that need illustration. | Lower, if no artwork is copied or uploaded into the AI system. |
| Visual inspiration | Looking at the old art to understand general story context while creating a new visual direction. | Needs caution. Avoid copying composition, style, character design, or distinctive choices. |
| AI reference input | Uploading old illustrations into Leonardo AI or another tool as image guidance, style reference, character reference, or image-to-image input. | Higher. Do this only if the rights are clear in writing. |
For beginner authors, the cleaner teaching path is usually to use the old book as a scene map and build a new visual system from scratch.
Three possible art paths for a second edition
Before creating new images, choose which art path the second edition will follow.
Path 1
Clean Replacement
The old book is used as a story and scene map. The new edition uses a fresh visual style, new character designs, and new production files.
Best beginner path when illustrator rights are unclear.
Path 2
Approved Refresh
The original illustrator or rights holder approves reuse, modification, or AI reference use in writing.
Possible, but only with clear written permission.
Path 3
Preserve Original Art
The second edition keeps the original illustrations and focuses on layout, formatting, cover cleanup, proofreading, and publishing records.
Works only if the existing art and file rights support the new edition.
For the case study in this series, the cleanest public teaching approach is to show how a second edition can create a new visual system while respecting the fact that prior illustrations may have separate rights.
The Second-Edition Rights Checklist
This checklist is not a legal contract. It is a working review tool for beginner authors before they begin production.
Save this in the project folder before making new art, uploading files, publishing to KDP, or selling through Shopify.
1. Author and manuscript
- Who wrote the book?
- Who owns the manuscript?
- Can the manuscript be republished?
- Can the text be edited?
- Can the title include “Second Edition” or similar edition language?
- Who gives final approval before launch?
2. Illustrator and artwork
- Who created the original illustrations?
- Was there a written illustration agreement?
- Who owns the artwork?
- Can the artwork be reused?
- Can the artwork be modified?
- Can the artwork be replaced?
- Can the artwork be uploaded to AI tools as reference?
- Are moral rights, credit, and integrity concerns addressed?
3. Publisher, files, and edition control
- Who published the first edition?
- Who controls the print-ready files?
- Was an ISBN assigned?
- Are there existing listings or distribution records?
- Does the prior publisher have any continuing rights?
- Can a new edition be published through KDP, Shopify, or another path?
4. AI workflow
- Which AI tools will be used?
- Will AI generate new images, edit images, or only assist with planning?
- Will any old artwork be uploaded as AI input?
- Will the final book require AI-generated content disclosure on KDP?
- Who reviews the selected images?
- Who approves the final cover and interior?
- Where will prompts, outputs, selected images, rejected images, and edits be documented?
Need a broader rights-tracking route?
Use AI Rights 101 when the issue is source records, human contribution, AI-use documentation, project folders, proof notes, or publishing-readiness tracking.
Open AI Rights 101What written approval should cover
Written approval does not need to be complicated at the planning stage, but it should be clear enough that everyone understands what is being explored.
Before production begins, the approval record should answer:
- Is this a second edition, revised edition, new edition, or test rebuild?
- Who is the author?
- Who is producing the new files?
- Will the old illustrations be reused, replaced, or only used as a scene guide?
- Will AI tools be used to create new images?
- Where can the book be sold?
- Can the book be used as a public case study?
- Can companion products be created?
- Who must approve the proof before launch?
Plain-language planning statement
“We are exploring a second edition of this children’s book. The goal is to preserve the author’s story while reviewing rights, updating the production files, creating a new visual direction if approved, documenting AI-assisted work, and preparing the book for a proofed publishing path.”
Special note for older authors and family projects
Many second-edition projects begin because an older author, parent, grandparent, teacher, pastor, local storyteller, or family member has a book that deserves a cleaner modern release.
The best way to support that author is not to overwhelm them with every technical detail. Give them a simple review packet.
A good review packet should include:
- A one-page summary of the second-edition goal.
- A list of what will stay the same.
- A list of what may change.
- A clear statement about AI-assisted visuals.
- A note about illustrator or publisher rights that still need confirmation.
- One sample visual direction before full production.
- A simple approve / revise / pause response option.
The goal is informed approval, not technical overload.
If the family project needs a clearer writing route, start with Voice.
Find Your Voice is the better route when the book idea, author notes, review packet, public explanation, or product page needs clearer wording before production.
Open Find Your VoiceAI-generated, AI-assisted, and why the difference matters
When AI tools become part of a second-edition workflow, creators need to separate three things:
| Term | Simple Meaning | Why It Matters |
|---|---|---|
| Human-authored | The creator writes, draws, edits, arranges, or designs the material through human creative choices. | Human contribution is central to copyright and authorship records. |
| AI-assisted | AI helps with editing, planning, refinement, error checking, or idea development while the final creative content is made by the human. | The use may still need documentation, especially for internal proof records and future clarity. |
| AI-generated | AI creates actual text, images, translations, cover art, or interior illustrations used in the book. | Platform disclosure and copyright-claim limits may apply. |
For this series, the best practice is to document the workflow even when disclosure is not required by a platform. Documentation protects the project from confusion later.
What to save in the project folder before redesign
Before creating the new visual system, create a folder for approval and rights records.
The public-domain source, what it supports, and what later adaptations must be avoided.
The author’s approval to explore, revise, redesign, produce, proof, and publish the second edition.
Any agreement, permission, limitation, credit requirement, or decision to avoid using old art as AI input.
Prior publisher, ISBN, distribution, files, listings, and any terms connected to the first edition.
Tools used, prompts, references, selected outputs, rejected outputs, edits, and review status.
Final review of physical proof, cover, interior pages, credits, product copy, and launch permission.
What to do before moving to Article 3
Before beginning the contamination audit, complete this rights pass.
- Confirm who wrote the book and who owns the manuscript.
- Confirm whether the author approves a second-edition exploration.
- Identify the illustrator and any existing art agreement.
- Do not upload prior illustrations into AI tools unless written rights allow it.
- Confirm whether a prior publisher controls files, ISBN, layout, or distribution.
- Decide whether the second edition will preserve, refresh, or replace the original artwork.
- Write down who must approve the visual direction before full production.
- Save the rights checklist in the project folder before generating final images.
Coming next: the contamination audit
Article 1 created the public-domain source record.
Article 2 created the rights review.
Article 3 goes deeper into adaptation contamination: how AI creators can accidentally mix public-domain source material with later movies, stage versions, famous lines, costumes, logos, and brand signals.
That article will show how to build a simple Safe Source / Original Additions / Do Not Use table before writing prompts or creating new visuals.
Series Route
Article 3 should be linked only when its final URL is live.
Until then, use Article 1, this Article 2, the Oz guide, and the AI Writing hub to keep the reader path clean.
Responsible creator note
This article is educational. It is not legal, tax, or publishing-platform approval advice.
If your project involves a known story world, an existing illustrator, a prior publisher, an existing ISBN, a trademark question, a publishing contract, AI-generated artwork, or copyright registration, speak with a qualified professional before you publish or sell the new edition.
Source links for readers
These are starting points for creators who want to check the source and platform rules behind this article.
Continue From Here
Choose the next step after the rights review.
This article slows the project down before redesign. Use the routes below based on the next blocker: source discipline, AI rights records, voice and author notes, series navigation, or general starting direction.
Need the source foundation?
Read Article 1 before touching new art, prompts, KDP files, or product pages.
Read Article 1Need public-domain context?
Use the Oz guide for the public-domain foundation, later-adaptation caution, and creator-safe source thinking.
Open the Oz GuideNeed records and tracking?
Use AI Rights 101 for documentation, human contribution records, source notes, and AI workflow tracking.
Open AI Rights 101Need clearer author notes?
Use Find Your Voice when the project needs author notes, story explanations, product copy, review packets, or public messaging.
Open Find Your VoiceFollowing the series?
Use the AI Writing hub for Article 3 and later parts when their final URLs are live.
Follow the SeriesStill not sure where this fits?
Use the Creator Roadmap to choose the right starting direction before buying or rebuilding more assets.
Open Creator RoadmapFinal Word
Before you redesign the book, confirm who can approve the redesign.
Public domain can help you build from an older source. AI can help you create new visuals. KDP and Shopify can help you publish and sell. But none of that replaces the need to respect the author, the illustrator, the prior publisher, the files, the artwork, and the approval path.
Final reader route: confirm the source, confirm the rights chain, document the workflow, then move to contamination audit and visual-system planning only when the approval path is clear.
Article 1 · Article 2 · AI Writing Hub · Oz Guide · AI Rights 101 · Find Your Voice · FAQ