Chapter 9 — Build a Body of Work, Not a Content Feed

A published Work shouldn’t vanish into the stream that announced it. In a feed the newest item sits at the top, and yesterday’s work becomes context for today’s post before it sinks under tomorrow’s. A body of work is organized by relationship and endurance instead. Works refer to one another, questions deepen, and each finished Work changes what you can make next.

You can use feeds. The trouble comes when the feed becomes your model of authorship, so that every idea gets judged for immediate publication and fragments gather audience approval that makes them hard to transform later. You end up responsible for staying visible instead of for building something durable. Kept below the body of work, the feed can serve it. A newsletter may develop an idea or keep up a relationship between releases, and an interview can carry the Works to a new audience.

A completed book leaves more than sales behind. It may leave a research library, characters capable of further stories, source and permissions records, and lessons about structure, production, and release. Left scattered, these force the next Work to begin by reconstructing the last. Connected, they let it begin from a higher level, and that is how authorship compounds.

In fiction a location cut from one book may become the center of another, and research into a historical period may feed several stories. In nonfiction a definition tested in one Work can become the foundation for the next, and reader objections can show where another book is needed. A body of work can also change genre, subject or form radically, with the continuity lying in your standards or way of seeing and no shared topic at all.

Keeping it together takes preservation: usable source files, recorded rights, canonical metadata, edition history, research stored with provenance. Keep your public identity separate from platform-specific handles, since platforms change and a body of work should outlast the tool that currently shows it.

It takes curation, too, because an archive stops being usable when everything in it is equally important. Separate canonical work from active material and supporting research, and decide what should be deleted. Deletion can protect the body of work by removing false options and privacy risk. An author page, bibliography or series order then lets a reader come to the work on purpose.

A follower count is something a platform observed, whereas a reader relationship is evidence that someone chose to receive, buy, read, or return to the Work. It carries permission and expectation, so treat it as a mutual boundary in which you offer work and communication under stated terms and the reader chooses their attention and access.

A body of work takes longer to build than a feed and can look less active while it forms, but you stop starting from zero with each release. That is why The Inkagai Way ends with the long term.

Reflection

• Which durable assets did your last Work create?
• What will you need to reconstruct before beginning the next?
• Which platform currently owns access to your readers?
• Does your public activity serve the body of work, or has the body of work become material for the feed?