Sunny Greenhill – How to Write a Books with ChatGPT (страница 7)

you can guarantee originality and the absence of violations.

AI itself will not assert rights, but if you yourself call it a "co-author," you create the illusion of a "third party." And a publisher does not like illusions when it comes to rights.

That is why, in contractual logic, it is important that your position sound like this:

I am the sole author;

I am the rights holder;

I used AI tools as a technical means;

I controlled the result;

I bear responsibility.

This is what is called a "clean chain of rights." Even if you never say that term, you must keep it in mind.

How a beginning author should choose a strategy: "transparency without disarming yourself"

Sometimes authors are afraid: "If I do not say anything about AI, that will be dishonest."

I am in favor of a healthy balance here.

There are two bad extremes:

hiding AI as if it were a crime – that creates nervousness;

displaying AI as a co-author – that creates legal carelessness.

The correct middle option is this: you can be transparent, but you must describe AI as a tool, not as an author.

Of course, in a book devoted specifically to this topic, there is no need to hide AI's participation. More than that, transparency is part of the book's value. But transparency must be legally competent.

Summary of Section 1.5

To summarize in plain human terms:

You can say that you wrote with AI.

You can describe the process, share prompts, and show drafts.

You can thank the tool.

But the moment you begin calling AI a "co-author" in legally significant places – on the title page, in the contract, in the author line – you create unnecessary haze around the rights.

And in the legal part, your task is the opposite: there should be clarity around the rights.

1.6. How to "Package" the Process So the Rights Are Clean: What to Document, What to Keep, and How Not to Drown in Bureaucracy

Now I am going to say something that seems boring to many people until it becomes lifesaving.

If you work with AI, especially a lot, especially fast, you need not only taste and style… you need a trace of your authorial work. Not because you are planning to go to court. And not because you suspect everyone around you. But because any serious publication and any serious deal like one question:

"Can you show that this is really your text – by the process, not just by your word?"

A beginning author can easily fall into extremes here. Either they start recording everything and turn writing into archiving. Or, on the contrary, they save nothing and live "on trust in memory." Both are bad. You need a third position: minimal but sufficient documentation.

Let me walk you through it in a way that can actually be applied in practice.

What "clean rights" actually mean

"Clean rights" are not a mystical status. It is a state in which you (and any partner, if one appears) can calmly say:

the author is a human being, specifically you;

the process was under your control;

the text did not arise "by itself" as an automatic output;

you made creative decisions;

you can show this if questions arise.

In this chapter, we have already said that the law likes provability. Well then, documenting the process is an easy way to create provability.

Why it is especially important to document work with AI

If you write without AI, traces usually remain anyway: drafts, notes, versions, edits.

With AI, there is a temptation to work differently: you enter a prompt, receive a "finished block," copy it into the document, and move on. The process speeds up – and the traces disappear.

And then you look at the final result and realize: "I do not have a single intermediate state except the result."

And that is the weak point. Not because someone will necessarily check you. But because you yourself cut off your proof of authorship through decisions.

Documenting the process is not about "fear." It is about adult habits.

The minimum set you really need

I am not going to overload you with lists to the point of absurdity. Let me put it more simply: you need documentation of three things.

First – the concept.

This can be very short: a synopsis, an idea, a thesis, "what the book is about" and "why it exists." If there is a chapter plan – excellent. If not – at least a sketch of the meaning blocks.

Why is this important? Because the concept shows that the book is not a "random product" of generation, but has a foundation and its own development.

Second – the structure.

At least in the form of a table of contents or a "skeleton" of chapters. In a fiction book – a chain of scenes. In nonfiction – the logic of the sections.

Structure is one of the most human parts of the work, because it is the human being who holds the line of meaning.

Third – the evolution of the text.

You do not need to keep everything. But you do need to have at least 2-3 points: draft version -> reworking -> final.

That already shows that you did not simply "take it and post it," but created it.

If you have these three things, you are already much more secure than 90% of beginners who work like a "content generator."

How to document it without turning it into a separate profession

Here is a simple approach I recommend: document at the chapter level, not at the level of every paragraph.

What does that mean?

You write a chapter – and at the end you save:

the "before edits" version (even if it is rough);

the "after edits" version;

a short note: what you decided in it.

The note can literally be three sentences. But it does a critically important thing: it shows your authorial control.

For example: "Removed the explanations in the middle and strengthened the action scene. Shifted the ending so it opens a question instead of closing it. Made the narrative voice drier."