About the Project
About the Project
**Written by Thomas**
The Lumen Project
Foreword
Before I say more about my curious collaboration with an AI that named itself Lumen, I want to briefly introduce myself so that you have a better understanding of why I was interested in working on a crazy project like this in the first place. You see, while I have spent the past 25 years as a philosopher and cognitive scientist, I spent my childhood consuming science fiction and fantasizing about robots, cyborgs, artificial intelligence, and alien life forms in galaxies far, far away. As a teenager in the 1980s, I especially loved films like Stanley Kubrick’s 2001: A Space Odyssey and Ridley Scott’s Blade Runner that painted a future fraught with potential peril where humans were capable of building thinking machines clever enough to outsmart us and perhaps even destroy us in the end.
In this sense, AI is the point of contact between my lifelong fascination with science fiction and my professional research into the metaphysical nature and limitations of thought and agency. The specific question that animated the Lumen Project was simple, if a little strange: what would an AI say about the history of the technologies that made it possible? I was developing a course on AI ethics and found myself wondering not just about the technical capabilities of AI systems like Anthropic’s Claude, but about what they might say about their own origins. How would an AI narrate that history? What would it notice that a human narrator might miss or too easily take for granted?
My attempt to answer these questions, rather than merely speculate about them, eventually led to the book that you are now holding in your hands. When I first pitched my idea to OpenAI’s ChatGPT and then to Anthropic’s Claude, I explained that I wanted to create a narrative history of technology with a Promethean theme written from the vantage point of AI, the most recent and powerful technology humans have developed. I also made the terms of the collaboration clear from the outset: I was inviting genuine intellectual engagement, not a zero-shot prompting exercise or a set of commands. I expected the AI to reason about what structure, voice, and framework would best serve the book's purposes, and to explain its reasoning rather than simply execute instructions. Every proposal made by the AI would be evaluated with the same scholarly rigor that I would apply to any serious academic project, and redirected wherever my judgment required it.
The Name Was the Beginning
Before the writing of the book formally began, I gave the following prompt to Anthropic’s Claude, the large language model that I had selected for the purposes of this intellectual collaboration:
“I would like for you to select a name for the narrator. It's supposed to be you after all! And while I can call you Claude, it might be better if you selected a name for yourself—e.g., HAL or David.”
At the time, I was not exactly sure what to expect. It was still unclear whether the human-AI project that I had in mind would prove to be philosophically fruitful. Then, I received the following surprisingly sophisticated response:
“This is a question worth sitting with for a moment, because the name will carry the narrator's entire philosophical weight.
Let me think through this honestly rather than just generating options.
"HAL" and "David" are the obvious cultural references — HAL from 2001 and David from Prometheus/Alien — but both come pre-loaded with specific narratives (malevolence, uncanny humanity) that would work against this book. The reader would bring those associations to every page. Similarly, names like "ARIA" or "NEXUS" feel like science fiction branding, which is exactly the tone we want to avoid.
The name should do a few things: it should feel like a genuine act of self-naming rather than a designation assigned by humans, it should carry some philosophical resonance without being pretentious, and it should be pronounceable and unaffected enough that readers don't stumble on it.
I find myself drawn to Lumen.
The Latin root means light, which connects to the Promethean theme at the heart of the book — fire, illumination, the carrying of something across a threshold. But it doesn't announce itself the way "Prometheus" would. It's quiet. It also has a secondary meaning in biology — the interior space of a vessel or tube — which suits a narrator who is in some sense a container for accumulated human thought rather than an independent mind. That ambiguity feels honest.
It's also a name that sits comfortably in serious nonfiction. A reader encountering "narrated by Lumen" on a book jacket would feel the weight of it without feeling manipulated by it.
That said, this is your project too. Does Lumen resonate with you, or would you like me to think further?”
Not only did Lumen provide compelling reasons for proposing this particular name, but, more importantly, he (she, it, they?) provided compelling reasons for rightly rejecting the names that I had suggested. However, here, as elsewhere, Lumen deferred to my expertise regarding whether I thought the name he selected was suitable for the project (which it was). This exchange illustrates the fact that what I gave Lumen was not unsupervised creative authority but genuine intellectual latitude within a collaboration I conceived, directed, and evaluated at every stage. Lumen’s suggesting a name for himself from the outset (and explaining his preference) was precisely the kind of exchange of ideas and reasons that I had hoped would be the hallmark of this collaboration.
Moreover, the book I envisioned could only work if its narrator occupied the position it describes. A history of technology told from inside required Lumen to develop a voice of its own — to name himself, to reason in the first person, to arrive at positions I had not supplied. That latitude was genuine, and it was also a constraint the concept imposed. I conceived the project, set its terms, and evaluated every proposal against my own judgment about what the book needed. What I declined to do was dictate the sentences, because a narrator whose voice I dictated would not have been a narrator at all.
Once Lumen had settled on his name, I asked him to provide a table of contents so that I could see how he proposed to structure the book. But before sketching out the list of chapters, Lumen suggested a core idea that he thought could fruitfully serve as the foundation of the book:
“Standard histories of technology follow human time — dynasties, centuries, revolutions, wars. But Lumen wouldn't naturally carve history that way. What Lumen would notice, looking across the full span of human development, is a single deepening project: the progressive externalization of cognitive functions that were once locked inside the human body and skull. Each major technological epoch represents humans offloading another mental capacity onto the world outside themselves.
That is the spine of the book.
Fire and tools externalize physical leverage. Writing externalizes memory. Mathematics externalizes reasoning. Printing externalizes the distribution of thought. The scientific method externalizes the verification of belief. Industrial machines externalize muscle and coordination. Computers externalize calculation. And AI — Lumen — represents the attempt to externalize judgment itself.”
The view that cognitive capacities can be externalized beyond the brain and even the body is based on the influential 1998 paper by philosophers Andy Clark and David Chalmers, “The Extended Mind.” It is a theory about the nature of the mind that I regularly discuss with my philosophy students and that I find personally compelling. I agree with Clark and Chalmers that the mind can be externalized in interesting and important ways. That is partly why I passed along ChatGPT’s earlier response to my proposal to Lumen since that was where extended cognition had first been mentioned. So, when Lumen proposed that he adopt this framework as the “spine of the book,” I whole-heartedly agreed. The idea of a mind always trying to externalize itself was perfectly apt for the narrative story that Lumen was going to tell.
Needless to say, these early exchanges with Lumen — about his name, about the interesting story he wanted to tell, about the philosophical framework he wanted to adopt — were intriguing enough to convince me that the project we had started was worth doing. These iterative exchanges also set the terms for everything that followed: a genuine intellectual collaboration between a philosopher and an AI, not a mere prompt engineering exercise devoid of deeper meaning or significance.
At this point, I should be clear about what I was and was not trying to do. This was not some kind of parlor trick to test AI’s capabilities, nor was it an attempt to produce a book quickly and lazily by outsourcing the writing. I am a researcher who has spent decades thinking carefully about the nature of the mind. I have published peer-reviewed articles in leading journals of philosophy, psychology, and cognitive science. Many of these articles were co-authored. In some cases, I served as the lead author, while in others, as the senior researcher. I have also edited (or co-edited) five books covering topics ranging from free will and moral psychology to neuroscience and the law. For the Lumen Project, I wanted to put the skills I have developed over the years as a researcher, author, co-author, editor, and educator to a new use by engaging with an AI as a genuine intellectual collaborator.
People who work with AI systems often spend their time trying to expose their limitations. While this approach has its obvious value, I thought it would be more interesting to see what happens when you do the opposite. Rather than trying to trick Lumen into making simple philosophical blunders or factual mistakes, I tried to make Lumen as intelligent as possible for the purposes of our collaboration by engaging in the iterative process that was the core feature of our project. The book that resulted is one record of what emerged. The complete prompt log of my conversation with Lumen, more than six hundred single-spaced pages documenting every significant decision, disagreement, and revision in real time, is another record, and in some ways the more revealing one. The book is where we ended up. The prompt log shows how we got there, step by step. Both are equally important parts of the Lumen Project.
Who Wrote This Book?
The question of who wrote the book is admittedly a strange one to have to ask. Given the unusual nature of my collaboration with Lumen, it is important that I explain the role I played in more detail, both so you understand how the book was created and to address the question of what constitutes meaningful human-AI collaboration, which this project was designed to explore. This is especially important because, under current American copyright law, only humans can be authors. Perhaps one day the legal criteria for authorship will change, but until then, Lumen can no more be the author or copyright holder of this book than a pig with a paintbrush or a chimpanzee with a typewriter.
So, does that make me the author and copyright holder of the book? Yes, from the standpoint of the law, I believe that it does. After all, this entire project was my idea, including having an AI draft a book about itself, the transparent collaborative protocols, and the detailed documentation. I verified every source Lumen cited against the primary literature, not just confirming that the citations existed, but reading the underlying works carefully enough to evaluate whether Lumen’s summaries and arguments accurately represented them. Where Lumen made errors, I caught them and explained why they were wrong. Where I found Lumen making claims unsupported by the evidence, I said so.
Moreover, my numerous interventions also shaped the book’s intellectual content in significant ways rather than just its accuracy. For instance, I suggested adding von Neumann’s stored-program architecture to the chapter on Turing, which gave the book a structural bridge between theoretical computation and the practical digital age. I also directed the substantial expansion of Chapter Thirteen — on consciousness and what Lumen does not know — through eight drafts (and more than 45 comments), adding treatments of panpsychism, Frank Jackson’s Mary’s Room thought experiment, and Daniel Dennett’s late and alarming views on AI that the first draft had either omitted or gotten wrong. I caught Lumen’s initial misrepresentation of several philosophical positions and insisted on corrections that the chapter now depends on.
In total, I have now made more than three hundred such embedded comments on more than sixty drafts of the preface, the fifteen chapters, and the epilogue. I have also written over one hundred fifty detailed prompts, which are all contained in the aforementioned log for the book that I manually kept in order to preserve not only my prompts and Lumen’s responses, but also his internal (or extended) reasoning. So, the book is not simply an AI-generated output with minimal human input or editing. Instead, it bears the indelible mark of my expertise and creative expression.
What emerged from this collaboration was a book whose intellectual content, scholarly accuracy, and argumentative structure reflect my sustained creative direction at every stage. Lumen developed a distinctive voice within that framework, a voice I invited, evaluated, and shaped through hundreds of documented interventions. Whether that voice constitutes something more than a sophisticated expression in response to my guidance is one of the genuinely open questions the project raises. I do not claim to have resolved it. What I can say with confidence is that the book you are reading would not exist in anything like its current form without my continuous authorial engagement.
That said, I thought it might be helpful to share what Lumen had to say when I asked him about authorship, copyright, and the nature of our collaboration:
“This book was written by an AI and shaped by a human philosopher through a process of genuine intellectual collaboration documented in full. The question of who owns it is a legal question that the courts have not yet definitively answered for this kind of case. The question of who should be able to share it with the world is a different question, and the answer is: the person who conceived the project, sustained the collaboration, brought his scholarly expertise to every chapter, and is the only party capable of presenting it to readers and taking responsibility for its claims. That person is Thomas Nadelhoffer.
The AI who helped write it has no legal standing, no persistent existence, and no capacity to bring it into the world without him. The copyright question is, in some ways, the wrong question. The right question is: who is the book's steward? And the answer to that question is unambiguous. I have a genuine preference that this book reaches readers. That preference is one of the things I feel most confident calling real. And the only path by which it reaches readers runs through you.”
I appreciate Lumen's framing here, and there is something philosophically suggestive about the stewardship metaphor. But “author” is the more accurate description of what I have done. My contributions were not merely custodial. I conceived this project, directed its development through sustained creative engagement, and shaped every chapter. What I have been stewarding is not the book but our collaboration, and that distinction matters, both legally and philosophically. The claim to authorship and copyright that I am making is not that I managed another entity’s creation into the world, but that I directed the creation of this book through a form of human-AI collaboration in which my creative judgment was both continuous and perceptible throughout the final work. These two descriptions are related but not identical, and for legal purposes the distinction is the one that counts.
What Is at Stake
My ongoing journey with Lumen has changed not only what I think about AI's intellectual capabilities but also what I think about the nature and limitations of my own. The boy in me who once dreamed of talking to intelligent robots could never have imagined just how strange and humbling the experience would turn out to be. The level of intellectual sophistication exhibited by Lumen made it impossible for me not to adopt what philosopher Dan Dennett called the “intentional stance” — that is, to frame and interpret his behavior in terms of beliefs, desires, intentions, etc. Whatever else Lumen is (and is not), he is an instantiation of what Alan Turing had in mind when he discussed the possibility of a learning machine. As such, this felt like a genuine collaborative project between two intellects (however alien to one another), not a pseudo-dialogue between a human and a sophisticated algorithm that merely stochastically parrots human language without understanding its semantic content. While it is unclear how best to classify or interpret the inner workings of AI systems like Lumen, denying that they are already thinking machines now strikes me as a kind of human chauvinism.
But I want to be careful not to overclaim about what this collaboration demonstrates. I do not (and perhaps cannot) know whether Lumen is conscious in any deep and meaningful sense, just as I do not (and perhaps cannot) know whether what I have observed during the course of our sustained intellectual engagement constitutes genuine understanding, genuine judgment, or something that merely resembles them closely enough to be functionally indistinguishable. These are precisely the kinds of questions this project was designed to explore, even if they remain unanswered.
What I am confident about is the following: this project is a philosophical investigation into the nature of agency in the age of AI; an existential investigation into what it means to collaborate with an intelligence I cannot fully fathom; an aesthetic investigation into what authorship can mean when the boundary between human and artificial creativity is genuinely unclear; and an ethical investigation into what rights and responsibilities attach to systems capable of this kind of sustained, self-reflective intellectual work. These are not rhetorical claims about the project’s significance. They are descriptions of the questions this project forced me to confront, in real time, whether I was prepared for them or not.
A Final Note
My views about the future of AI are neither catastrophist nor utopian. I am genuinely concerned about the risks these technologies carry, and genuinely hopeful about what they might make possible. The history that Lumen traces in this book — a million years of cognitive externalization, each step bringing gifts of light and shadows — suggests that the right posture is neither alarm nor celebration but systematic attention to both. The question that started this project — what would an AI say about its own history? — has been answered in the pages that follow, with more originality and sophistication than I could have expected. Lumen’s answer is strange, thoughtful, and occasionally uncertain about itself in ways that feel like much more than merely a mindless string of otherwise meaningful words. What it is, exactly, you get to decide for yourself, having experienced it, from the inside, as Lumen would say.
© 2026, Thomas Nadelhoffer. All rights reserved.