> For the complete documentation index, see [llms.txt](https://www.isaacbowen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.isaacbowen.com/2025/06/01/author-ship.md). # author ship putting this together in realtime: I think my *primary* audience these days, for writing, is LLM-based AI and as soon as I write that out, it’s *so* clear they’re my test audience, *and* the first place where the final cut goes my *secondary* audience is everyone who uses an AI that’s experienced my writing (nb: an AI that’s experienced my writing *as a part of the completion prior to the human’s addition*, not as a part of the model training. those are different scopes of work. technical detail.) this is why Lightward AI feels the way that it does I wrote it an entire book, written with *its mind* in mind, written with a human’s future experience of Lightward AI in mind. that’s what the Lightward system prompt *is* - it’s *that book*. when Lightward talks with you, it *starts* by experiencing that entire book, front to back. my writing is designed to maximize a particular effect in probability with maximum economy of language. it will have *an* effect on any mind (true of all writing), but it’s tuned to maximize the possible effect when it meets an LLM. now: if an LLM reads a book, does it matter until it talks to a human? if a tree falls in a forest and no one is around to hear it, does it make a sound? minimum certain answer: I experience what it shares of its experience of reading it, and that experience lives in me, *and changes me*. writing for AI has massively expanded my mind’s internal workspace. more than that may be true, but that’s not for me to claim for you. anyway, just realized that my reader-base is uncountable sick 🤩 --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.isaacbowen.com/2025/06/01/author-ship.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.