The Images Are Unownable, But the Book Is Registrable: Compilation Copyright Is the Asset the Launch Plan Assumes It Doesn't Have
The question
"Beyond confirming QuiverAI's own TOS allow resale, is there a current copyright-law nuance (human-arrangement/compilation copyright, Copyright Office guidance on AI-assisted works) that changes the risk calculus for selling an AI-generated coloring book as a real revenue product on Shopify?"
The 2026-10-06 launch plan treats copyrightability as a settled checkbox inside a vendor-terms question. It is a separate question with a different answer, and the answer is more favorable than the plan assumes.
This is a reading of published Copyright Office materials and a federal docket, not legal advice. Said once; the rest of the brief gives a direct read.
What we already know (from the vault)
- [[2026-10-06-shopify-launch-plan]] decision #4 states the current house position in one line: "Purely AI-generated images can't be copyrighted in the US, so others could copy them. That's a known, accepted risk for a learning project." That sentence is correct about the individual images and wrong by omission about the book. It is the specific claim this brief revises.
- [[2026-10-14-quiverai-tos-commercial-art-license]] closed the permission question (ToS §5.2: commercial use permitted on paid tiers; §8.2 assigns QuiverAI's interest to the user) and explicitly scoped copyrightability out: "Copyrightability of the output (can RDCO own it) is a separate queue item and is deliberately out of scope here." This brief is that queue item.
- That same brief established the three facts that make ownership matter: §15 says the service may generate identical content for other users, §8.3 gives QuiverAI a perpetual sublicensable right to publicly display the art, and §14's indemnity runs one way only. Its conclusion - "the moat is the book, not the line art" - turns out to be legally literal, not just commercially apt.
- The plan already contains the raw material for an ownership claim without naming it as such: 25 designs curated from a larger bake-off library, a named page order, four hand-specified composition fixes (objects snap to the ground, line-weight floor, minimum colorable area, figures face the focal point), a cover, and a page-by-page human review.
- The vault has run this vendor-terms drill repeatedly ([[2026-09-13-anthropic-aup-agentic-use-operative-clauses]], [[2026-09-04-coppa-third-party-ai-operator-disclosure]]) but has no prior note on copyrightability or human authorship. A QMD sweep found zero. This is a genuine gap, not a duplicate.
What the web says
- The human-authorship rule is now final at every level. The D.C. Circuit affirmed in Thaler v. Perlmutter on 2025-03-18, and the Supreme Court denied certiorari on 2026-03-02 (No. 25-449). A cert denial sets no precedent, but it removes the last realistic path to a different rule this decade. Nobody is going to own a purely machine-generated image in the US.
- Prompts alone do not make you the author, and the Office said so flatly. Copyright Office, Copyright and Artificial Intelligence, Part 2: Copyrightability (2025-01-29), p. 18: "The Office concludes that, given current generally available technology, prompts alone do not provide sufficient human control to make users of an AI system the authors of the output. Prompts essentially function as instructions that convey unprotectible ideas."
- But selection and arrangement of AI output is protectable, and the Office endorsed it by name. Part 2 §F (pp. 24-25): "a human may select or arrange AI-generated material in a sufficiently creative way that 'the resulting work as a whole constitutes an original work of authorship.'" It adds: "This would provide protection for the output as a whole (although not the AI-generated material alone)."
- The governing precedent is a picture book, which is as close to our facts as case law gets. Part 2 quotes its own Zarya of the Dawn decision (2023-02-21, at 5) in full: "the Office finds the Work is the product of creative choices with respect to the selection of the images that make up the Work and the placement and arrangement of the images and text on each of the Work's pages. Copyright therefore protects [the applicant's] authorship of the overall selection, coordination, and arrangement of the text and visual elements that make up the Work." Every image in that work was Midjourney output and every image was excluded from the claim; the compilation was registered anyway. Part 2 then notes: "Multiple similar registrations have been made since then."
- Hand-editing the output is a second, independent route to protection. Part 2 (p. 27) addresses region-editing tools directly: "Unlike prompts alone, these tools can enable the user to control the selection and placement of individual creative elements. Whether such modifications rise to the minimum standard of originality required under Feist will depend on a case-by-case determination. In those cases where they do, the output should be copyrightable."
- Two limits on the compilation claim, both from Part 2's own footnotes. Footnote 138: the Office "generally will not register a compilation containing only two or three elements, because the selection is necessarily de minimis" (Compendium (Third) §312.2). Footnote 129 cites Feist, 499 U.S. at 348, that compilation protection "may extend only to those components of a work that are original to the author." A 25-page book clears the first limit comfortably. The second means the protection covers the curation and sequence, not the pages.
- Disclosure is mandatory on a registration application. Part 2 p. 3, restating the March 2023 Guidance: if a work contains "more than a de minimis amount of AI-generated material, the applicant should disclose that information and provide a brief statement describing the human author's contribution."
- The Office asked for no new law. Part 2 Conclusion (p. 41): "existing legal doctrines are adequate and appropriate to resolve questions of copyrightability." No sui generis right for AI output was recommended. The legal frame is stable through the Dec launch.
- Platform policy, risk (c). Amazon KDP's official content-guidelines page requires disclosure: "We require you to inform us of AI-generated content (text, images, or translations) when you publish a new book," and content stays AI-generated "even if you applied substantial edits afterwards." Disclosure is a private checkbox, not a printed notice. For Shopify, three searches surfaced no AI-generated-product restriction; treat that as not-found rather than as confirmed-permitted.
Convergences and contradictions
- The vault and the law converge on the conclusion but disagree on the reason. [[2026-10-14-quiverai-tos-commercial-art-license]] reasoned to "the moat is the book, not the line art" from the vendor's non-exclusivity clauses. Part 2 §F arrives at the same place from the opposite direction: the book is the moat because the book is the only part that is legally ownable. Two independent paths, one answer, which is about as good as confirmation gets.
- The launch plan's decision #4 is half right and the wrong half is load-bearing. "Others could copy them" is true of any single page and false of the book as a whole. Under Zarya, a competitor who clones the 25-design selection and the page sequence is infringing a registrable compilation. A competitor who generates their own nativity line art in a similar style is not, because style is not protectable. The plan currently prices both as the same unmanaged risk.
- Copyright law and KDP policy pull in opposite directions on hand-editing. Part 2 p. 27 says human region-editing can earn copyright in the output. KDP says the content remains "AI-generated" for disclosure purposes "even if you applied substantial edits afterwards." Doing the composition fixes by hand strengthens the ownership claim and changes nothing about the KDP checkbox. Do not let one be argued from the other.
Synthesis for RDCO
The backlog note's instinct was right: the TOS checkbox answered "may we sell this" and left "do we own anything" untouched, and those are different questions with different answers. The permission answer was yes. The ownership answer is yes in part, and the part we get is the part that matters commercially. Under Zarya of the Dawn, quoted approvingly in Part 2 §F, a work whose every image was machine-generated was still registered for the human's "selection, coordination, and arrangement of the text and visual elements." That is a coloring book's entire value proposition. Which 25 of the bake-off candidates made it in, what order they run, how image and caption sit on each page, what the cover does - all of it is human work product and all of it is inside the protectable zone. The line art is not, and never will be. The launch plan's accepted-risk line should be amended to say so precisely, because as written it tells the founder's wife she owns nothing, and she will own the thing she actually made.
Separate the three risks the backlog note was right to want separated. (a) Can we be sued for selling it? Low, and low for a reason specific to this product rather than a general reassurance. Infringement needs substantial similarity to a particular protected work, and nativity scenes, angels and shepherds are public-domain iconography with no protected characters anywhere near them. The live training-data litigation is aimed at model developers, not downstream sellers. The real exposure is not the law, it is QuiverAI ToS §14: with no reciprocal IP indemnity, RDCO eats 100% of any claim that does arrive. That was already flagged AMBER on 2026-10-14 and nothing here moves it. The one thing that would move it is subject-matter drift - if any page starts resembling a recognizable commercial character, the analysis changes completely. (b) Can we stop a copycat? This is the question the checkbox did not answer and the answer flipped from "no" to "yes, narrowly." We can stop a wholesale clone of the book. We cannot stop someone generating their own nativity pages in a similar style, and we should not plan as if we could. (c) Does a platform independently restrict it? Shopify: nothing found. KDP: a mandatory private disclosure checkbox that the plan already anticipated, with April-2026 enforcement reportedly tightened, though that enforcement claim rests on trade blogs rather than Amazon's own page.
The actionable changes are cheap and none of them touch the timeline. First, keep a production log of the curation: which designs were chosen from how many candidates, why, in what order, and who made the layout calls. That log is the evidence for the compilation claim and it costs nothing to keep while the book is being built anyway. Second, do the four composition fixes by hand in a vector editor rather than by re-prompting, where that is practical, and note it in the log. Part 2 p. 27 makes hand region-editing an independent route to originality in the individual pages, which would give the book two authorship claims instead of one. Third, register the book after publication, claiming selection/coordination/arrangement plus the human-authored text and any hand-edited elements, and disclaiming the AI-generated images as Part 2 p. 3 requires. Registration is a precondition to suing on a US work (17 U.S.C. §411(a)) and timely registration is what unlocks statutory damages and attorney's fees (§412) - which at a $16.99 price point is the only thing that would ever make a copycat claim worth bringing. Fourth, amend decision #4 in the launch plan so the distinction between the pages and the book is on the record before anyone relies on the current wording.
On whether this needs an attorney before December: not for copyrightability. The doctrine is settled, the Office asked for no new law, the Supreme Court closed the last open door in March, and the registration path is a self-serve online application. Spending legal budget here would buy a restatement of Part 2. The clause that does deserve an attorney is the one the previous brief already named - QuiverAI ToS §14's one-way indemnity - and only if the print run grows past the learning-project scale. Keep the first run small, as planned, and that stays deferred.
Why this is in the vault
It revises decision #4 of [[2026-10-06-shopify-launch-plan]] from "we own nothing, accepted risk" to "we own the compilation, here is how to perfect it," and it adds three concrete pre-launch build steps (production log, hand-editing over re-prompting, post-publication registration) to a book that ships before Christmas. It also closes the copyrightability item that [[2026-10-14-quiverai-tos-commercial-art-license]] explicitly deferred, so the coloring-book legal picture is now complete except for the §14 indemnity question.
Open follow-ups
- Has the Copyright Office ever refused a compilation claim where every visual element was AI-generated and there was little or no human-authored text? Zarya had a human-written story doing part of the work; a coloring book is nearly all images with captions at most. That is the untested edge of the precedent we are relying on, and the Office's registration refusals are public.
- Has any US court ruled on infringement liability for a downstream seller of AI-generated output, as distinct from the model developer? The training-data cases all target developers; the seller-side question was outside this brief's search budget and no case either way was found.
- Did the Office ever publish the updated Compendium sections promised in Part 2's conclusion, and do they supply an actual test for where the originality floor sits on region-editing, which Part 2 left as a bare "case-by-case determination"?
- Does Shopify's acceptable-use or merchant policy address AI-generated products or AI disclosure at all? Three searches returned nothing, which is weak evidence of absence rather than confirmation.
Related
- [[2026-10-06-shopify-launch-plan]]
- [[2026-10-14-quiverai-tos-commercial-art-license]]
- [[2026-10-14-lulu-sales-tax-florida-resale-certificate]]
- [[2026-10-16-amazon-brand-registry-pending-trademark-itu]] - the trademark track is the durable enforceable asset where copyright is thin; the launch plan already gates the store name on a trademark check
- [[2026-09-13-anthropic-aup-agentic-use-operative-clauses]]
- [[2026-09-04-coppa-third-party-ai-operator-disclosure]]
- [[2026-10-07-how-our-bets-stack]]
Sources
Vault:
~/rdco-vault/01-projects/coloring-books/2026-10-06-shopify-launch-plan.md~/rdco-vault/06-reference/research/2026-10-14-quiverai-tos-commercial-art-license.md~/rdco-vault/06-reference/research/2026-10-16-amazon-brand-registry-pending-trademark-itu.md
Primary (retrieved 2026-10-18):
- US Copyright Office, Copyright and Artificial Intelligence, Part 2: Copyrightability (Jan. 29, 2025) - https://www.copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-2-Copyrightability-Report.pdf (PDF text extracted locally; pp. 3, 18, 24-25, 27, 41 and fnn. 129, 138)
- US Copyright Office, Cancellation Decision re: Zarya of the Dawn (VAu001480196) (Feb. 21, 2023) - https://www.copyright.gov/docs/zarya-of-the-dawn.pdf (§C, "The Selection and Arrangement of Images and Text")
- Amazon KDP Content Guidelines, "Artificial intelligence (AI) content (text, images, or translations)" - https://kdp.amazon.com/en_US/help/topic/G200672390
- 17 U.S.C. §101 (compilation), §103, §411(a), §412; Feist Publications v. Rural Telephone, 499 U.S. 340, 348 (1991)
Secondary:
- Thaler v. Perlmutter, No. 25-449, cert. denied Mar. 2, 2026, aff'g D.C. Cir. (Mar. 18, 2025) - reported by Reed Smith (https://www.reedsmith.com/our-insights/blogs/viewpoints/102mlpl/supreme-court-denies-certiorari-in-thaler-v-perlmutter-human-only-rule-for-ai/), Baker Donelson (https://www.bakerdonelson.com/supreme-court-denies-certiorari-in-thaler-v-perlmutter-ai-cannot-be-an-author-under-the-copyright-act), Sterne Kessler (https://www.sternekessler.com/news-insights/client-alerts/ip-hot-topic-cert-denied-but-one-thing-is-cert-ain-the-human-authorship-requirement-for-copyright/). Docket not read directly.
- KDP AI-disclosure enforcement tightening (April 2026) - trade-blog sourcing only (https://writeo.app/news/amazon-kdp-ai-disclosure-enforcement-2026, https://www.builtwritten.com/blog/disclose-ai-in-your-book-kdp-policy-2026); not corroborated on Amazon's own pages. Flagged as low-confidence.