Public Domain Is Not a Permission Slip for AI Authors
Gary WhittakerAI Writing · Public Domain · Children’s Books · KDP · Shopify
```
A 5-part creator training series on rebuilding a public-domain-inspired children’s book with AI-assisted visuals, responsible documentation, KDP publishing, and Shopify sales planning.
```Public domain is a starting point, not a shortcut.
```Public-domain stories can open the door for new books, new artwork, new teaching tools, and new creator products. But public domain does not mean every version of a famous story is free to copy.
That is why I am building this series around one of the most useful examples for AI creators: the Oz world. L. Frank Baum’s original The Wonderful Wizard of Oz gives creators a public-domain foundation, but later films, stage versions, music, costumes, famous lines, brand signals, and modern retellings can create separate risks.
The purpose of this series is to show beginner authors how to work with public-domain inspiration without treating it like a blank check. The safer path is to document the source, separate later adaptations, add original expression, keep approval records, and prepare the book for real publishing standards.
```The pillar article
```The foundation for this series is my public-domain guide for AI creators:
Wizard of Oz Public Domain Guide for AI Creators
That article explains why the original source matters, why later adaptations need caution, and why creators should build from documented material instead of memory.
The working case study
The series uses an Oz-inspired children’s book being reviewed for a second edition as the working example.
This matters because real second-edition work is not only about improving images. It can involve author review, illustrator rights, previous publishing records, AI-assisted production, proof copies, platform rules, and a public product page.
Why this series matters now
```AI tools make it easier than ever to write, revise, illustrate, format, and sell a book. That is good news for beginner authors. It also creates a new problem: people can move so fast that they skip the records that protect the project.
A second edition should not begin with random image prompts. It should begin with a source record, a rights review, a clear visual direction, and a plan for how the book will be proofed before it is sold.
This is the difference between using AI as a shortcut and using AI as part of a documented creator workflow.
```What readers will learn
```By the end of the 5-part series, readers will understand how to:
Identify the public-domain work, what it allows, and what should be avoided.
Avoid accidentally pulling from films, stage versions, famous lines, modern costumes, or confusing brand signals.
Check author approval, illustrator rights, publisher records, source files, and future sales channels.
Use character sheets, style rules, scene maps, and prompt logs before generating the full book.
Understand ISBN choices, AI content disclosure, image quality, bleed, margins, proof copies, and file review.
Build a sales page, email path, digital companion options, and long-term creator-owned product system.
The 5-Part Series
```From public-domain source to second-edition launch
Each article focuses on one part of the rebuild process so beginner authors can follow the path without getting buried in publishing jargon.
```Article 1
```Public Domain Is the Starting Point, Not the Whole Permission Slip
This article explains why public-domain projects must begin with source discipline.
Readers will learn how to identify the exact source they are using, why the original Oz book matters, and why later adaptations should not be treated as part of the same free-to-use pool.
The case study shows why an Oz-inspired second edition should begin with a source record before any AI art, cover design, product page, or publishing decision is made.
Reader takeaway: Before you generate images, identify your source.
Article 2
```Rights Before Redesign: Author, Illustrator, Publisher, and AI Approval
This article explains why second-edition projects need rights review before visual updates begin.
Readers will learn how to identify who wrote the book, who illustrated it, who published it, who controls the files, and who must approve a new version.
The case study shows why AI-assisted illustration should not be treated as a magic reset button. If an existing illustrator is credited, their artwork should not be uploaded into an AI tool or used as a direct image reference unless the rights are clear in writing.
Reader takeaway: Do not start with prompts. Start with permission.
Article 3
```The Contamination Audit: Keeping Oz Book-Based and Original
This article explains how AI creators can accidentally mix public-domain source material with protected later adaptations.
Readers will learn how to separate source-safe elements from movie-only, stage-only, brand-specific, or confusing visual choices. The goal is not fear. The goal is discipline.
For Oz projects, this means checking details like shoes, costumes, famous lines, witch designs, cover composition, product language, and the way the story is marketed.
Reader takeaway: Do not prompt from what you remember. Prompt from what you can document.
Article 4
```Building the AI Visual System: Character Bible, Scene Map, and Leonardo Workflow
This article explains why children’s book visuals need a system before a full set of illustrations is generated.
Readers will learn how to create character sheets, style rules, scene prompts, image folders, prompt logs, and review steps for AI-assisted illustration.
The case study shows how an existing children’s book can become a scene map while the new edition develops its own visual identity. This is especially important when the old artwork has separate illustrator rights.
Reader takeaway: Do not generate the whole book first. Approve the visual system first.
Article 5
```Proof, Publish, and Sell: KDP First, Shopify Hub, Printify Companions
This article explains why publishing is more than uploading a file.
Readers will learn how to think through KDP, ISBN choices, AI content disclosure, image quality, bleed, margins, proof copies, Shopify product pages, and optional Printify companion products.
For the main book, KDP may be the simplest first publishing route. Shopify can become the author-owned sales and education hub. Printify may support companion products such as a coloring book, activity book, poster, or gift bundle after the main edition is proofed.
Reader takeaway: Uploading is not publishing. Publishing means proofing, approving, listing, selling, and supporting the book.
How the publishing path will be tested
```This series does not treat one platform as the answer for every author. Each platform has a different role.
| Platform | Best role in this workflow | What creators need to check |
|---|---|---|
| KDP | Main paperback or hardcover publishing path. | ISBN choice, AI disclosure, trim size, bleed, margins, image resolution, cover file, proof copy. |
| Shopify | Author-owned sales hub and case-study landing page. | Product page, fulfillment plan, digital downloads, tax settings, email capture, proof photos, customer support. |
| Printify | Optional companion products after the main edition is reviewed. | Book format limits, print quality, shipping cost, proof testing, and whether rights allow companion products. |
Careful language matters in public-domain projects
```One of the goals of this series is to help creators avoid careless claims. The right language matters because public-domain work can still sit beside modern copyright, trademark, publishing, and platform issues.
Instead of saying: “Oz is safe to use.”
Use: “The original public-domain source can be used as a foundation, but later adaptations, trademarks, trade dress, and confusing marketing still need review.”
Instead of saying: “AI art is automatically copyrightable.”
Use: “Human-authored contributions, creative selection, arrangement, and meaningful edits may matter. Pure AI output may need to be excluded from a copyright claim.”
Instead of saying: “The old illustrations can become AI references.”
Use: “The old book can guide the scene map, but using credited artwork as AI input requires written rights clearance.”
What makes this different from a normal AI book tutorial
```This is not a “type a prompt and publish a book” series.
The focus is the full creator workflow: source records, rights questions, public-domain separation, original visual design, AI-assisted production logs, KDP preparation, Shopify sales structure, and proof-copy review.
That is the point of the Second Edition Author System. It teaches authors to rebuild the process before rebuilding the book.
```Built around current platform and policy checks
```Because AI publishing rules and platform requirements can change, this series is being built around current source checks from official or primary sources wherever possible.
The series will refer to public-domain guidance, AI copyright guidance, KDP publishing rules, ISBN Canada, Shopify product setup, Printify book options, Leonardo AI workflow documentation, and trademark confusion guidance.
```Responsible creator note
```This series is educational. It is not legal, tax, or publishing-platform approval advice.
Authors should consult a qualified professional for contracts, copyright registration, trademark review, illustrator rights, publishing agreements, tax questions, and platform-risk decisions.
```Final Word
```Before you rebuild the book, rebuild the process.
Public domain can help you start. AI can help you produce. KDP can help you publish. Shopify can help you build the product system. But the creator still needs the record, the approval path, and the discipline to make the second edition stand on its own.
```