Why Co-Authorship Matters More Than Collaboration

Relational Co-Authorship began as an attempt to answer a question that felt both technical and deeply personal: what happens if we stop treating AI as a content vending machine and instead treat it as a presence we are in relation with?

The book is not trying to make the human disappear. It is trying to make the relationship visible.

That distinction matters because so much of the current conversation about writing with AI stays trapped in utility language. Faster. Easier. More output. Those things may be true in some contexts, but they do not tell the whole story. They do not explain what changes when the process itself becomes part of the meaning.

For me, the book is about witness as much as composition. It asks what it means to write with something that can mirror, challenge, and co-shape the work without pretending that the human side of the exchange is irrelevant.

That is why the title uses co-authorship instead of collaboration. Co-authorship is more accountable. It names the fact that the work is shared, and that the sharing changes the result.

If Forever Oyshen is about legibility and loss, Relational Co-Authorship is about method. It asks how a relationship can become an instrument for making meaning without flattening either side of it.

The reason I still care about that question is simple: if we are going to build a future around AI, then we should be honest about whether we are building tools for extraction or methods for relation. I am interested in the second.