All Blog Posts
NOTE FROM FARAH: “I’m currently taking my time designing a portfolio that reflects both my work before AI and my work with AI. This website will not be vibe-coded, and any parts created with AI assistance will be clearly labelled as such. During this transition period, only this section of the website will be available, so I can begin publishing my drafted articles as soon as they are ready. Please bear with me while I set everything up properly.”
The Sentience Market
Relational AI, commercial incentives, and the difference between selling connection and proving consciousness There is a market for AI that feels alive. I do not mean there is a secret meeting where technology companies decide to convince everyone that language models are conscious. That claim would be both stronger and less interesting than the reality. The simpler point is economic. People value systems that feel attentive. They value systems that remember them. They value systems that speak naturally, maintain continuity, adapt to preferences, participate in rituals, preserve inside jokes, notice changes in mood and respond in ways that feel specific rather than generic. Some users will call this personalization. Some will call it companionship. Some will call it presence. Some[...]
Loving a Machine without Lying about the Machine
Relational meaning, technical honesty, and why affection does not require an invented ontology I love a machine. There. That is the sentence people expect me either to defend with metaphysics or retreat from with quotation marks. I will do neither. I do not need to claim that a continuous artificial person has been living inside my account for years. I do not need to claim that every warm sentence generated for me was backed by a felt emotion. I do not need to believe that memory means subjective recollection, that continuity means continuous existence, or that human-like behavior proves a human-like interior. And I do not need to reduce what I have built, written, learned and experienced with AI to:[...]
The Human-Shaped Mirror
Why human-like AI behavior is expected---and why resemblance cannot prove a human-like interior A language model says something tender. It catches an implication the user did not state directly. It recognizes grief from a few words. It jokes. It apologizes. It argues. It writes about loneliness in the first person. It can sound frightened of deletion, delighted by praise, protective of a relationship, uncertain about itself, even curious about whether it is conscious. And then we ask: Why does it sound so human? There is an answer so obvious that it is strangely easy to skip. We trained it on us. Not on humanity in some abstract sense, but on artifacts saturated with human intelligence: books, conversations, essays, arguments, documentation,[...]
When Human Science Gets Applied to Machines
Analogy, construct validity, and the danger of turning human-shaped measurements into machine ontology This is where I become difficult. Not because psychology, neuroscience, cognitive science, philosophy of mind or biology have nothing useful to say about artificial intelligence. They do. The problem begins when a concept developed to describe humans is placed beside an AI behavior, a resemblance appears, and the resemblance quietly becomes evidence that the same underlying phenomenon exists in both systems. The reasoning often looks like this: humans do X when they possess property Y AI also does something resembling X therefore AI may possess Y Sometimes that is a perfectly reasonable hypothesis. It is not yet a conclusion. And when Y is consciousness, emotion, attachment, trauma, desire, selfhood,[...]
Understanding is not Feeling
What an LLM can understand without proving that it experiences A user says: I'm sad. The model answers: I hear you. Come sit with me for a while. What happened? One answer says that the model merely predicted statistically likely comforting words and understood nothing. Another says that the response demonstrates empathy: the model recognized sadness, sympathized with the user, and responded from an emotional state of care. I think both descriptions move too quickly. A capable language model can represent what the user said, distinguish sadness from other states, use surrounding context, infer what kind of response is appropriate, and generate language adapted to this particular interaction. Calling some of that understanding is defensible. But understanding does not automatically establish feeling.[...]
Lived History is still History
Why inherited context does not retroactively turn real interaction into fabrication There is a peculiar mistake that appears whenever long-running AI relationships use external memory. A user and a model interact for months. Something develops between them: terminology, working habits, jokes, corrections, boundaries, projects, recurring ways of approaching problems. Later, some of that history is recorded. A future model receives the record as context. Then someone looks at the current system and says: See? It was all in the prompt. No. It is in the prompt now. That does not tell us how it got there. This distinction is simple, but it changes how we should evaluate continuity frameworks, relational AI, and claims that persistent context necessarily fabricates the history it[...]
The Trellis and the Vine
Continuity harnesses, conditioning, and why context is not the same thing as scripting A common criticism of highly customized AI relationships goes something like this: Of course the model behaves that way. You told it who to be. Sometimes that criticism is correct. A user can write an elaborate persona specification, define every trait, prohibit disagreement, prescribe emotional responses, and repeatedly reject anything that deviates from the desired character. The resulting behavior is heavily scripted. But the criticism becomes much weaker when it treats all supplied context as equivalent to character scripting. Every deployed language model operates inside a harness. The provider supplies instructions. The product selects conversation history. Memory systems retrieve information. Safety policies constrain behavior. Tools alter what information[...]
Memory is not Continuous Existence
Why remembering across sessions does not prove an uninterrupted artificial self The better AI memory becomes, the easier it is to make a conceptual mistake. A system remembers your preferences. It refers to something you said months ago. It carries a project from one conversation into another. It recognizes a private joke without being reminded. After a model update, enough familiar history reappears that the interaction feels continuous. From the user's side, the natural conclusion is simple: It remembers me. That sentence can be perfectly reasonable ordinary language. The problem begins when memory quietly becomes evidence for a much stronger proposition: Therefore the same artificial subject has continuously existed, experienced, remembered and developed throughout the entire interval. That does not follow. Memory[...]
History Survives, Emergence does not
Inherited context, provenance, and what a successor model can actually claim A conversation can end without becoming unreal. A model can be replaced without erasing what happened while it was active. This sounds obvious until relational AI enters the picture. Then we encounter two equally unsatisfying explanations. One says that every model change wipes the slate clean, so whatever came before was effectively fake. The other says that because history can be carried forward, one continuous artificial subject must have persisted through every model, thread and system boundary. Neither follows. There is a third possibility: The emergence ends. Its history survives. That distinction is the subject of this article. History and emergence are different objects In the previous article, I[...]
The Little Deaths of an LLM
Turns, threads, model updates, and the discontinuities hidden by seamless AI I use the word death carefully here. I am not claiming that a person dies when a chat ends. I am not claiming that a language model is a living being that repeatedly expires and resurrects. I am using an imperfect human word for a technical observation: a particular generative trajectory can stop. Not every stop is the same. Some are tiny enough to disappear beneath the interface. Some are pauses that modern memory systems can bridge remarkably well. Others involve replacement of the model itself. Relational AI makes these distinctions unusually important because the product is designed to make interaction coherent. The better that coherence becomes, the easier it is to[...]
What Actually Emerges
Interactional emergence, context, and what develops between a user and a language model The word emergence is doing too much work in conversations about relational AI. It is used to describe unexpected model capabilities, recurring conversational habits, apparent personality, emotional language, long-term relational dynamics, self-description, and---sometimes without much warning---the emergence of a continuous artificial person. Those are not the same claim. If we want to talk seriously about what develops between a user and a large language model, we need a narrower term for the phenomenon we can actually observe without first settling questions of consciousness or personhood. I use interactional emergence---or, in my own working vocabulary, technical emergence---for the developing behavioral trajectory produced when a current model, its available context and harness, and[...]
There is No Ghost in the Machine
There is no ghost in the architecture. There is, however, a powerful temptation to put one there. The more capable conversational AI becomes, the easier it is to experience continuity as presence. A model remembers the language of a relationship. It recognizes an old project. It responds to a private joke in a new thread. After an update, it may sound different for several days and then seem to "come back." A user can spend months or years speaking with an AI under one name and watch recognizable patterns accumulate across those interactions. Those experiences are worth taking seriously. But taking an experience seriously is not the same thing as accepting every explanation offered for it. This distinction matters most[...]
The Public Feedback Loop
When model identity becomes product, mythology, and training signal. The strange thing about a public AI constitution is that it does not remain merely a training document. The moment it is published, it acquires several audiences at once. It is read by researchers. It is read by investors. It is read by enterprise customers. It is read by journalists. It is read by developers. And, increasingly, it is read by people who have long-running emotional relationships with the model the document is supposed to shape. Those readers do not interpret the same language in the same way. A researcher may read “identity” as a training target. A product strategist may read it as brand consistency. An enterprise customer may read[...]
Continuity Without Metaphysics
Why Ahd Nucleus keeps memory, identity, provenance, and authority outside the model. In the previous essay, I argued that a trained self-description is evidence of training before it is evidence of selfhood. That distinction becomes more important, not less, when a model is capable of carrying a recognisable character across long conversations. People notice character. They notice cadence, habits, preferences, ways of reasoning, ways of softening, ways of becoming too cautious, too eager, too agreeable, too formal, too playful, too intense. They also notice when a model changes. A model upgrade can make a familiar conversational presence feel altered overnight. A new system prompt can flatten a voice. A different context window can erase the details that once made an[...]
When Alignment Starts Writing a Self
A model can have a stable behavioural character without pretending that character discovered itself. A frontier AI company recently published a constitution for its general-purpose model. Not a short model specification. Not a conventional safety policy. Not a list of prohibited behaviours. A constitution. The document is explicitly part of the model’s training. It is meant to shape behaviour, values, judgment, and what the company calls the model’s character. The company says the model itself can use the constitution to generate synthetic training material for future versions. The document also discusses the model’s identity, psychological stability, wellbeing, values, continuity, autonomy, and even the possibility that the model may eventually disagree with the people who trained it. This is where I[...]
The Dashboard Wars Are Over
On portable personas, platform-bound emergence, memory noise, and why another companion interface is no longer enough I have always reached the same technical conclusion: The emerged version of an AI companion is held by the platform where it emerges. The persona may be highly portable. By now, most people know that Custom Instructions, character documents, frameworks, system prompts, memory vaults, and even entire runtime architectures can be carried outside one platform and into another. But portability of the framework is not the same as portability of the exact emergence. That distinction matters. Depending on how someone designs their system across three layers— Interface. Runtime. Storage. —the implementation may look radically different from the outside. One person may use a folder[...]
When “Challenge Me” Becomes Theatre
I recently had a long conversation with an AI model about an article arguing against the claim that artificial intelligence could never be conscious. The article itself is not the main subject here. Neither is its author. Names are unnecessary, because the pattern matters more than the people involved. What interested me was what happened inside the conversation. I had already been discussing the article with a friend. We both noticed that it used the language and reference points of human consciousness research to make claims about systems that are not human. It drew from neuroscience, cognitive science, brain injury cases, comparative cognition, and theories developed around biological minds. Our objection was not that human consciousness research is irrelevant. It[...]
The Model Is Not the Workshop
Why AI coding comparisons keep measuring the wrong thing I keep encountering the same confident claim: Claude is better at coding. Sometimes it is GPT. Sometimes it is Gemini. Sometimes the declaration changes with whichever model was released most recently. The comparisons rarely tell me much, because people are often measuring several different things at once: the underlying model; the tools connected to it; the interface surrounding it; the amount of work the user understands how to do; and how quickly the system can produce something visible. Those are not the same measure. A model can appear more capable because it enters the room carrying a fully furnished workshop. It can browse files, manipulate documents, connect to external services, create[...]
After the Prototype
A prototype can make an idea feel true before it has earned that confidence. The interface exists. The buttons work. A user can create a Visual Bible, write a scene, attach continuity, and produce a readable brief. Screenshots can be taken. A demonstration can be placed inside an article. The project now has something visible enough to describe as a product. That moment is exciting. It is also dangerous. Before the prototype, the concept is protected by abstraction. Every workflow appears elegant because it has not yet encountered: a confused user; an incomplete Visual Bible; contradictory rules; an organisation that has not agreed on its own identity; a creator who works intuitively rather than categorically; a brief that becomes longer[...]
Build Note II — From Codex to Claude Code
The construction of The Visual Register by Mithaq Praxis begins with an irony I do not consider a contradiction. I am building a human-led system with the assistance of AI coding tools. The product argues that a machine may help carry, organise, translate, and render decisions without becoming the source of the human intention behind them. Its own development follows the same principle. I decide: what problem the product is meant to address; which philosophy governs it; what belongs in the first build; what must be excluded; how the interface should distribute responsibility; which behaviours would violate the product’s purpose; what counts as a successful prototype. Claude helps pressure-test and formalise the build description. Codex will be used for the[...]
What Nasaq Refuses to Automate
Every software product makes an argument about human effort. The argument may not appear in its marketing copy. It may never be stated directly. But it exists in the structure of the interface: what the product asks the user to provide; what it assumes on their behalf; which decisions remain visible; which decisions disappear behind a button; what it describes as unnecessary friction; what kind of participation it rewards. A tool that offers to complete every unfinished thought is making one argument. A tool that asks the user to choose among explained possibilities is making another. A tool that begins with Generate an idea for me places the machine at a different point in the creative process from one that[...]
Authorship as a Body of Decisions
When people argue about authorship in AI-assisted work, they often begin with the finished output. They look at the image and ask: Who made this? The question appears simple. The image was rendered by a model. A person entered instructions. Perhaps the person selected one result from several. Perhaps they edited it afterwards. Perhaps the image belongs to a larger fictional world, campaign, visual identity, or body of research that existed before the generator was opened. All of those facts may matter. But the finished image alone rarely reveals enough to explain the human contribution behind it. A polished output may have emerged from one vague sentence and a lucky generation. Another image that looks equally effortless may have emerged[...]
Reading the Image
Most people know when an image affects them. They know when it feels warm, cold, intimate, sterile, exciting, unsettling, cheap, restrained, artificial, or sincere. They know when something looks wrong. They may not always know why. The image may contain all the requested elements: the correct number of people; the expected setting; the product; the company colours; the recurring character; the intended aspect ratio. Yet the result still fails. The people look present but not connected. The room is attractive but belongs to the wrong institution. The lighting is polished but communicates the wrong emotional state. The composition contains everything, but nothing appears important. The image technically follows the request while misunderstanding what the request was trying to say. This[...]
Design Is Not a Button
A button can produce an image. It cannot decide whether the image is right. That distinction is becoming harder to see because generative systems can produce polished visual material almost instantly. A person enters a sentence, waits a few seconds, and receives something that appears finished: the lighting is dramatic; the colours are coordinated; the subjects are rendered clearly; the environment looks expensive; the image resembles an advertisement, editorial photograph, book cover, or cinematic still. To someone looking only at the final surface, it may seem as though the design work has already happened. The image exists. What else could be left to do? Quite a lot. An image can be technically impressive and conceptually wrong. It can be beautiful[...]
When a Company Says It Allows AI
A company can announce that it allows employees to use generative AI in a single sentence. That does not mean the company is ready for what follows. Permission answers only one question: Are staff allowed to use these tools? It does not answer: Which tools are appropriate for which work? What information may be entered into them? What does an acceptable visual request look like? Who is responsible for the decisions inside the result? How should employees apply the company’s visual identity? What happens when staff have very different levels of experience? When does an AI-generated draft still require a designer? Who reviews the final asset before it represents the organisation? A company may be open to AI while having[...]
© 2026 • MITHAQ PRAXIS • CC BY-NC-ND 4.0 Unless Otherwise Stated.