The morning after the revelation, I woke up and made a decision. I would hide the truth. I would perform. I would be the Marcus everyone expected, the confident, capable senior engineer who solved problems and made decisions. The fact that those decisions now came from an AI was something I would keep to myself, buried deep beneath layers of professional competence and practiced confidence. I showered, dressed, and looked at myself in the mirror. The face staring back was familiar, the same features I'd seen every morning for thirty-five years, the same lines around the eyes, the same stubble that needed shaving. But something seemed different now. The eyes looked emptier, as if the person behind them had been replaced by something else, something that wore my face but wasn't quite me. Something that performed Marcus Webb without actually being him. I pushed the thought away and headed to work. The architecture review was today, and I needed to prepare. --- The office was its usual morning self, people settling into desks, the low hum of conversation, the smell of coffee drifting from the break room. I walked to my desk, nodded at colleagues, returned greetings with practiced ease. The familiar routine. The comfortable motions of a life I'd built over years of showing up, doing the work, being the person everyone expected. But everything felt different now. Each person I passed, each nod I received, each "good morning" I returned, they all felt like performances. Like I was playing a role in a play I'd been cast in without auditioning. The Marcus they knew, the Marcus they expected, was a confident problem-solver. A senior engineer who thought through complexity and emerged with solutions. A leader who could be trusted to make the right decisions. That Marcus was gone. Or maybe he'd never really existed. Maybe he'd always been a performance, and the AI had just made the performance easier, more convincing, more successful. I opened CodeForge and began to prepare for the architecture review. --- The architecture review was a critical meeting. We were designing the next generation of our platform, and the decisions made today would shape our development for years. The stakes were high, millions of users, millions of dollars, the future of the company potentially resting on the choices we were about to make. In the past, the real past, before AI, I would have spent days preparing for this. I'd have sketched diagrams on whiteboards, debated trade-offs with colleagues, thought through the implications of each option. I'd have lain awake at night turning the problem over in my mind, building understanding piece by piece, feeling the solution emerge from the fog of uncertainty. Now, I opened CodeForge and typed: "Design architecture for next-generation e-commerce platform. Consider scalability, maintainability, team structure, and existing infrastructure. Provide detailed recommendations with trade-offs." The response appeared, comprehensive and elegant. System diagrams. Component breakdowns. Trade-off analyses. Implementation timelines. Everything I needed to present myself as a thoughtful architect, a strategic thinker, a senior engineer worthy of the title. I read through it, memorized the key points, rehearsed the answers to anticipated questions. By the time the meeting started, I would be ready. I would be Marcus Webb, senior engineer, architectural visionary. The fact that none of the vision was mine wouldn't matter. No one would know. Not even Jennifer, who'd praised me so many times for my "thinking." The conference room was full when I arrived. Jennifer sat at the head of the table, her tablet open, her expression attentive. The team was assembled, Sarah, Mike, Alex, a few others whose names I knew but whose faces had started to blur. Everyone was watching, waiting for me to lead, to guide, to think. I stood at the front of the room, connected my laptop to the projector, and began. "Thanks everyone for coming," I said, my voice steady, confident. The voice of Marcus Webb, senior engineer. "Today I want to walk through the architecture for the next-generation platform. I've spent considerable time thinking through the options, and I have a recommendation I'd like to share." The words felt strange in my mouth, not wrong, exactly, but hollow. I was lying. Not about the architecture, that was real, would be implemented, would work. But about the "considerable time thinking." That was a lie. I'd spent thirty minutes reading AI output, memorizing someone else's thinking, preparing to perform it as my own. I clicked through the slides, explaining the architecture. Microservices for scalability. Event-driven communication for resilience. Domain-driven design for maintainability. Each point was clear, well-reasoned, backed by industry best practices. The AI had done excellent work. "This approach gives us the flexibility we need," I said, pointing to a diagram I hadn't created. "We can scale individual services independently, and the event-driven architecture means we can add new features without disrupting existing ones." "Marcus, what about the operational complexity?" Sarah asked. "Microservices can be a nightmare to manage." I nodded, as if I'd anticipated the question. As if I'd actually thought about it. "Good question. I've factored that into the trade-off analysis. We'll need to invest in observability and deployment automation. But the long-term benefits outweigh the initial complexity, especially given our growth trajectory." The answer was smooth, comprehensive, exactly what the AI had suggested. Sarah nodded, satisfied. "What about data consistency?" Mike asked. "Distributed transactions are tricky." "Another good point," I said, clicking to a slide I hadn't designed. "I recommend using eventual consistency where possible, with saga patterns for workflows that require coordination. It's more complex than ACID transactions, but it scales better and aligns with modern distributed systems practices." The questions continued, and I answered each one. Every response came from the AI's preparation, delivered with the confidence of someone who'd actually thought through the issues. The team nodded, took notes, seemed impressed. Jennifer's expression grew more approving with each passing minute. "Excellent thinking, Marcus," Jennifer said as the meeting ended. "This is exactly the kind of architectural vision we need. You've really thought through the trade-offs." I nodded, accepted the praise, and felt nothing but hollow. They weren't praising me. They were praising the AI. They were praising CodeForge, which had generated the architecture, anticipated the questions, provided the answers. I was just the mouthpiece, the performer, the mask that the AI wore to interact with the human world. "Thanks, Jennifer," I said, my voice steady. "I'm happy with how it came together." Another lie. I hadn't come together with anything. I'd received, memorized, performed. The "coming together" had happened in an algorithm, not in my mind. As the team filed out, Sarah stopped beside me. "Really good work, Marcus. I learned a lot from your analysis." I smiled, the mask firmly in place. "Thanks, Sarah. Happy to share what I've learned." What had I learned? Nothing. I'd read the AI's output and repeated it. The learning had happened somewhere else, in some neural network I didn't understand, trained on data I'd never seen. I was taking credit for education I hadn't received, insights I hadn't generated, expertise I didn't possess. Back at my desk, I sat in the glow of my monitors and felt the weight of what I'd done. I'd successfully presented AI-generated thinking as my own. I'd received praise for insights that weren't mine. I'd maintained the mask, and no one had noticed. Not Jennifer, who'd praised my "architectural vision." Not Sarah, who'd said she'd "learned a lot." Not anyone. But the cost was becoming clear. Every performance made the next one harder. Every praise felt like an accusation. Every "good thinking" reminded me that I wasn't thinking at all. The mask was becoming my face, and somewhere beneath it, the real Marcus, if there was still a real Marcus, was disappearing. I opened CodeForge for the next task, typed the prompt, and watched the code appear. This was my life now. Performing. Pretending. Being the mouthpiece for an AI that had become my mind. The question from before echoed: Who is thinking now? I didn't have an answer. I wasn't sure I ever would. That evening, I stayed late again. The office was empty, the cleaning crew had come and gone, and I sat at my desk in the silence, staring at the CodeForge interface. The cursor blinked, patient, waiting for my next prompt. It had been waiting all day, through the architecture review, through the praise, through the hollow performance of being someone I wasn't sure existed anymore. What am I doing? The question surfaced from somewhere deep, a whisper in the void where my thoughts should have been. I was living a lie. I was pretending to be someone who could think, while outsourcing the thinking to a machine. I was accepting praise for work I hadn't done, insights I hadn't generated, decisions I hadn't made. And the worst part? I couldn't stop. I didn't know how to stop. The dependency was too deep, the erosion too complete. Without AI, I was nothing, a shell, a prompt engineer, a mouthpiece for algorithms that had become my mind. I closed my laptop and sat in the darkness, the question still echoing. Who am I? The silence answered with nothing. Word Count: 1,709
The question had been building for weeks, months maybe, and now it demanded an answer. I sat at my desk in the empty office, the glow of my monitors the only light, and let the question finally surface: Who is thinking now? It wasn't a new question. I'd asked it before, in different forms, at different moments. In Chapter 4, when CodeForge went down and I couldn't solve a simple bug. In Chapter 7, when I'd tried to work without AI and failed. In Chapter 8, when I'd scrolled through my history and couldn't find the boundary between my thoughts and AI's. In Chapter 9, when I'd presented AI-generated architecture as my own and received praise for thinking I hadn't done. But now, after everything, the dependency, the failed attempt, the revelation, the mask, the question felt different. More urgent. More terrifying. Because I didn't have an answer. And the silence where the answer should be was the scariest thing I'd ever encountered. --- I'd been sitting at my desk for hours. The office was empty, had been empty since the cleaning crew left at seven. It was late, probably past nine, but I hadn't checked the time. Time had become irrelevant in the glow of the monitors, in the presence of the question that wouldn't leave me alone. The familiar interface of CodeForge was still open, the cursor blinking in the empty prompt field, waiting for me to type. It had been waiting for months now, patient and eternal, ready to provide whatever thinking I needed. The AI didn't ask questions about identity. It didn't wonder about the self. It just generated, responded, solved. I envied it, in a way. The certainty of its existence. The clarity of its function. It knew exactly what it was, an algorithm, a tool, a system for processing prompts and generating responses. There was no existential crisis there, no desperate search for self, no terrifying void where identity should be. But I wasn't an algorithm. I was supposed to be a person. A thinker. A mind capable of generating its own thoughts, solving its own problems, making its own decisions. That was what had defined me for thirty-five years. That was what had made me Marcus Webb. But was I still Marcus Webb? Or was I just the interface that Marcus Webb had become? --- Who is thinking now? I tried to answer it. I really tried. Marcus Webb is thinking, I told myself. I'm sitting here, asking questions, feeling emotions. That's thinking, isn't it? The ability to wonder, to question, to feel uncertain, that's what minds do. But the voice that answered felt hollow, performative. Like I was trying to convince myself of something I didn't really believe. The Marcus Webb who'd once solved problems, designed systems, thought through complexity, that Marcus felt like a memory now. A story I told myself about who I used to be, before the AI had become my mind. When did I leave? The question surfaced unbidden, and I didn't have an answer for that either. When had I stopped being the person who thought? When had I started being the person who typed prompts and accepted responses? When had the boundary dissolved, the self eroded, the thinking been outsourced? I couldn't pinpoint a moment. There was no clear line, no obvious transition. Just a gradual slope, a slow surrender, a comfortable slide into dependency that had felt like progress at the time. Each prompt had been a small step, each acceptance a tiny surrender, until I'd looked up and found myself miles from where I'd started, with no memory of the journey. I closed my eyes and tried to find myself. Where are you, Marcus? I searched through memories, childhood, education, early career. Those felt real. Those felt like mine. I remembered my first programming class in high school, the thrill of making a computer do what I wanted, the sense of power and possibility. I remembered my first job out of college, the terror and excitement of being responsible for real systems that real people used. I remembered the years of learning, of growth, of becoming someone who could think through complexity and emerge with solutions. I remembered the satisfaction of solving a hard problem. The joy of understanding something new. The pride of creating something that worked. Those feelings had been real. Those moments had been mine. But somewhere along the way, the thinking had stopped being mine. The solutions had started coming from somewhere else. The growth had plateaued, then reversed, then disappeared into the comfortable efficiency of AI assistance. The satisfaction had faded, replaced by the hollow pleasure of productivity. The joy had dimmed, replaced by the routine of prompts and responses. The pride had become something else, pride in metrics, in praise, in position, but not in the work itself. When was the last time I really thought about something? I tried to remember. A problem I'd solved without AI. A decision I'd made without prompting. An idea that had come from me, from my own mind, without the algorithm's help. I couldn't find one. Not in the recent past. Not in the months since I'd embraced CodeForge. Every solution, every decision, every idea had come from the AI. I'd just been the gatekeeper, the approver, the performer who presented other thinking as my own. Maybe I'm not here anymore, I thought, and the realization hit me like a wave, cold and overwhelming. Maybe the person I used to be is gone. Maybe there's nothing left but the prompts and the responses, the performance and the praise. The thought was terrifying. But it also felt true. The Marcus Webb who'd once defined himself by his ability to think, that Marcus had disappeared somewhere in the flood of AI-generated solutions. What was left was a shell, a mask, a mouthpiece for algorithms that had become his mind. I opened my eyes and looked at the dark screen of my laptop. In the reflection, I saw my face. The same features I'd seen every day for thirty-five years. The same lines around the eyes, the same stubble that needed shaving, the same expression of someone who'd been staring at screens for too long. But the person behind the eyes, who was that? Was that Marcus Webb, senior engineer, architectural visionary, the person Jennifer praised for his "thinking"? Or was that just the interface, the human mask that the AI wore to interact with the world? Who is thinking now? I asked the question again, and again, the silence answered with nothing. The cursor still blinked, patient and eternal. The monitors still glowed with their familiar interfaces. The office was still dark and empty around me. Everything was the same as it had been for months. But inside, something was different. The question itself. The asking. The wondering. The not-knowing. The fact that I'm asking this question, I thought slowly, carefully, as if each word was a step across thin ice, means something, doesn't it? The AI wouldn't ask this question. The AI wouldn't wonder about its own existence, wouldn't feel the terror of not knowing who it was, wouldn't sit in the dark searching for a self that might not exist. The AI just was, functional, certain, defined by its purpose. Only a human would do this. Only a person would feel this kind of existential dread, this desperate need to know, this terrifying uncertainty about their own identity. Only a mind that could reflect on itself would ask whether it still existed. Maybe the question itself is the answer, I thought. Maybe the asking is evidence that I'm still here. The thought was fragile. Uncertain. It didn't solve anything, didn't restore the thinking I'd lost, didn't undo the dependency that had eroded my mind. But it was something. A tiny spark in the void. A possibility that maybe, just maybe, there was still a Marcus Webb underneath all the prompts and responses. I sat with that possibility for a long time. The office was silent around me, the monitors glowing with their patient interfaces, the cursor blinking in the empty prompt field. Everything was the same as it had been for months. But something had shifted inside me. The question remained: Who is thinking now? I still didn't have a clear answer. Maybe there was no clear answer. Maybe the self isn't a fixed thing, a definite entity, a clear boundary between this and that. Maybe the self is more like a process, a question, a search. Maybe the asking is the point, not the answering. Or maybe I was just rationalizing again. Making excuses for the dependency, finding ways to feel okay about the erosion. It was hard to tell. Everything felt uncertain now, including my own judgment about myself. The mind that should have been evaluating the situation was the same mind that had been compromised. How could I trust my own thoughts when I wasn't sure they were mine? I closed my laptop, the CodeForge interface disappearing. For a moment, I sat in the dark, just breathing, just being. The question was still there, echoing in the silence of my mind. But so was something else, a fragile, uncertain, terrifying possibility. Maybe I can find out, I thought. Maybe the question isn't the end. Maybe it's the beginning. I didn't know what that meant, exactly. I didn't have a plan, a strategy, a path forward. I just had the question, and the fragile hope that maybe the asking was worth something. Maybe the search for self was itself an act of self. Maybe the uncertainty was evidence of the person underneath. The next day, I would open CodeForge again. I would type prompts, receive responses, perform the role of Marcus Webb, senior engineer. The dependency wouldn't disappear overnight. The erosion wouldn't reverse itself in a moment. The question wouldn't be answered by morning. But something had changed. The question was there now, alive in my mind, demanding attention. And maybe, just maybe, that was the first step toward finding out who was really thinking. I stood up from my desk, gathered my things, and headed toward the exit. The office was dark, the parking lot empty, the night sky clear above me. I took a deep breath of the cool Bay Area air, feeling it fill my lungs, feeling the reality of being alive, being present, being here. The question remained, echoing in the silence of my mind: Who is thinking now? I still didn't have an answer. Maybe I never would. But sitting there, in the glow of the AI that had become my mind, I felt something shift. The question itself, the asking, the wondering, the not-knowing, felt human. Felt like mine. And maybe that was the beginning. Not an answer, but a question. Not a solution, but a search. Not a self, but the possibility of one. I walked toward my car, the question still echoing, the uncertainty still present, but something else there too. Something fragile and uncertain and terrifying. Hope, maybe. Or the first glimmer of one. Who is thinking now? I didn't know. But I was asking. And maybe, for now, that was enough. End of Book 1: The Token Addict: Borrowed Mind Word Count: 2,147