KDP Publishing 02: Build a Rights, Account, and AI Ledger

A polished file still has to stop when one rights record is missing.

What You Will Produce

• Objective: Document rights and AI-use facts for the manuscript, translation, quotations, images, cover, and fonts without inference.
• Action: Find four risks in a sample project, write at least one ledger row, and record account readiness as PASS or FAIL.
• Evidence: A ledger containing source, permitted use, evidence location, AI-use fact, reviewer, and a secret-free account readiness status.

Rights Evidence Comes First

Ownership and permission are not the same thing. Record what each asset is, where it came from, what use is allowed, and where the supporting evidence can be found.

Separate AI Facts from Account Secrets

Record AI use separately for text, images, and translation, using the current KDP wording when disclosure decisions are made. Account evidence contains only PASS or FAIL. Passwords, cookies, tokens, tax identifiers, and bank identifiers never belong in the ledger.

Practice: Locate Four Risks

Review the sample project and mark unsupported rights, missing review responsibility, unclear AI-use facts, and unsafe account notes. Convert each issue into a ledger entry or a stop condition.

Where This Fits in the Series

Closing Principle

A guess is not evidence, and a secret is not proof of readiness.

References

• Amazon KDP Help

This article is for preparation and quality assurance. Never capture or record passwords, cookies, tokens, tax identifiers, bank identifiers, or private manuscript identifiers.

Series Navigation

Previous: KDP Publishing 01: Define the Scope Before You Build
Next: KDP Publishing 03: Freeze One Authoritative Source