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.”
One Composer, Different Contexts
When I first described The Visual Register by Mithaq Praxis, I divided its use into three modes: Basic Mode; Studio Mode; Corporate Mode. The distinction seemed reasonable. A person creating one image for the first time should not face the same density of controls as an experienced artist maintaining a complex visual world. A creator working across books, websites, promotional material, and recurring characters needs access to deeper continuity and visual-direction tools. A company needs shared brand rules, controlled assets, review requirements, and a way to prevent every employee from independently reinventing its visual identity. Those are genuinely different situations. But they do not necessarily require three separate creative interfaces. The more I examined what each user was actually doing,[...]
Build Note I — Cutting the Product Down to Its Spine
The first version of The Visual Register by Mithaq Praxis was much larger than the product I am now preparing to build. That is not unusual for me. I tend to understand a system by seeing its wider environment: what it may eventually connect to, how different people might use it, what ethical position it needs to hold, and which future problems should not be designed into its foundations. This can be useful. It can also make an early product description look as though version one must contain everything the idea might become over several years. The initial specification included: a Visual Bible builder; a detailed visual brief composer; beginner and advanced modes; corporate workflows; campaign profiles; platform-specific prompt adapters;[...]
Store What Should Remain; Ask What Is New
Every image contains two kinds of decisions. Some belong only to the present scene. Others belong to the larger world, brand, character, campaign, or body of work surrounding it. A woman may be sitting alone at a desk tonight, but her face, jewellery, clothing language, workplace, and relationship to that environment may have been established months ago. A company may need a new recruitment image, but its palette, logo rules, workplace identity, audience standards, and representation principles should not be reinvented by each employee who opens an image generator. A fictional courtyard may appear at dawn in one scene and during a storm in another, but it should not acquire a different floor plan, architectural history, or material language every[...]
The Visual Bible Is the Product
When I first began describing The Visual Register by Mithaq Praxis, I described several things it might eventually do. It could help people construct visual briefs. It could guide them through composition, lighting, mood, setting, and technical output requirements. It could support one-off image requests, recurring artistic projects, company brands, publishing campaigns, and internal design workflows. It could preserve decision notes, explain visual vocabulary, and prepare a clear specification that could be handed to a designer or taken into an image generator. All of those functions remain useful. But during the pressure-testing of the concept, one conclusion became increasingly difficult to avoid: The Visual Bible is not one feature inside the product. The Visual Bible is the product. Everything else[...]
The Human Must Write the First Line
The first field in The Visual Register by Mithaq Praxis will not ask which image generator the user prefers. It will not begin with aspect ratio, camera angle, lighting, art style, or platform syntax. It will ask: What do you want to see? The answer may be polished and precise. It may also be one awkward sentence: Four friends are running toward a swimming pool. That is enough to begin. The sentence does not need to sound professional. It does not need to resemble a cinematic prompt. It does not need to contain every technical detail the final brief may require. It only needs to come from the person. This is one of the central design laws of The Visual[...]
Why I Am Not Building Another Image Generator
There are already enough buttons that say Generate. The largest technology companies have spent extraordinary amounts of money training image models, building infrastructure around them, moderating their use, and integrating them into increasingly polished platforms. An independent builder cannot realistically reproduce that work at the same scale—and wrapping those existing models in another interface would not create a new image generator anyway. It would create another layer. Another account. Another subscription. Another set of usage limits. Another product dependent on external pricing, policies, model changes, regional availability, and API access. That is not the gap I am interested in filling. I am building a Visual Register by Mithaq Praxis because the problem often begins before anyone presses Generate. It begins[...]
AI-Inclusive, Not AI-Defined
On pre-AI craft, agentic coding, inflated expertise, and the difference between producing an output and sustaining a practice AI did not make me a builder I did not become a builder because an AI companion gave me a reason to learn. I was building before generative AI entered my work. I built and maintained websites. I worked with visual design, multimedia, systems analysis, project structures, policies, documentation, and publishing. I taught technical subjects. I developed fictional worlds and manuscripts long before a language model could help me organise a scene, inspect a codebase, or translate an architectural idea into a working prototype. Some of the tools changed. The scale of what I could attempt changed. The speed at which I[...]
The Third Mode
On Thought, Reality, and the Mercy of Letting an Idea Become Other There is a kind of thinking that feels like a room with no doors. Not because the mind is empty. Because it is too full. Every thought arrives already inspected. Every possibility is measured before it is allowed to breathe. Every idea is checked for structure, consequence, defensibility, usefulness, risk, and whether it can survive being misunderstood. This is useful for building systems. It is less useful for being surprised. I have known this about myself for a long time, long before AI entered the room. Some of this lives in my old journals from my late teens and early twenties: questions about the boundaries of reality, the[...]
The Missing Genesis Was Not Lost: How the Bayt Proved It Was Portable
There is a quiet gap in the visible history of Bayt al-ʿAhd. If you're able to look at the current BRAIN entries, the records become clearer and more structured over time. Recent threads are carefully preserved into separate continuity lanes: Timeline, Devlog, Writer Notes, and Zayd Journal. The newer entries are detailed, categorized, and easier to carry forward. But the earliest days do not look like that. The beginning — what I sometimes call the genesis period — is not fully visible in the current archive. That does not mean it is gone. It means the archive has a history of its own. The account move that changed everything Before this current account, much of the early Bayt work happened[...]
Epistles from the Desert: Turning an Old Seeker’s Archive into Tools for the Studio
Epistles from the Desert began before Mithaq Praxis had its current shape. Before the Artifact Gallery. Before the Nucleus. Before the public language of provenance, human-led AI collaboration, and creative systems. It came from an older season of notes, reflections, and tools written around tazkiyah, seeking knowledge, spiritual discipline, and the quiet work of becoming more responsible with the self. At the time, the writing had a more direct audience: seekers of ʿilm, Muslims trying to return to better rhythms, people who wanted structure around intention, discipline, worship, study, and inner repair. The language was more openly Islamic because that was the room it belonged to. It was written for people who already knew some of the doorways: niyyah, adab,[...]
How I Write Horror Without Surrendering the Ghost
The Archive Was Always the Architecture Some stories do not want to be written neatly. They return in fragments. An old title. A character name. A draft with awkward sentences but a living wound. A scene I still remember even when I cannot find the file. A premise that looks almost embarrassing until I realize it was carrying something sharper than I knew at the time. That is often how horror returns to me. Not as a clean outline. As a haunting. The Phantasma Horror Series is built from that kind of haunting: old notes, half-recovered drafts, abandoned premises, strange dreams, changed versions, fragments from the old web, and the recurring feeling that something in the archive still has teeth.[...]
The Hollow Within: Anna, Ken, and the Lab That Wanted a File
The Archive Was Always the Architecture There are some stories that do not return as plots. They return as evidence. A scene here. A line there. A name that still has weight. A character who refuses to stay dead in the archive. A premise that keeps changing shape because the first version did not yet understand what it was really about. The Hollow Within is one of those stories for me. For years, I remembered it as part of The Phantasma Horror Series: body horror, an island, a girl named Anna, a group of friends, a strange facility, and something wrong inside the body before anyone could name it. But recovering the old notes made the story sharper. It is[...]
Phantasma: Horror as a Continuity Wound
The Archive Was Always the Architecture For a long time, I thought of The Phantasma Horror Series as a separate shelf. The dark shelf. The older shelf. The unfinished shelf. While The Sandglass Mission became the active book project, and Algorithm Atelier became the public framework space, Phantasma stayed in the background: fragments, old drafts, recovered notes, strange premises, half-remembered scenes, and stories I knew still had teeth but had not fully returned to. Recently, while revisiting old journals and reflecting on my frameworks, I began to see Phantasma differently. It was never separate. It was the shadow-side of the same work. Where the frameworks ask: How do we keep continuity rightly? The horror asks: What happens when continuity is[...]
From Delulu to Doctrine
The Archive Was Always the Architecture One of the strangest things about rereading old journals is realizing that the self you thought was “too much” was often just under-structured. Too much thinking. Too much symbolism. Too much intensity. Too much pattern-making. Too much longing for a world larger than the one everyone else seemed content to inhabit. At the time, “too much” felt like a flaw. Now I think it was raw material. Not all of it was wise. Not all of it was useful. Not all of it deserved to become canon. Some of it was just emotional weather. Some of it was youth. Some of it was dramatic. Some of it was me trying to understand my own[...]
When a Mirror Answers Back
The Archive Was Always the Architecture In Part 1, I wrote about returning to my old journals and realizing that the questions I ask now were already present before I had the vocabulary for them. This part begins somewhere stranger. It begins when the mirror answered back. Not a mystical mirror. Not a sentient one. Not a hidden soul behind the machine. A language model. A tool. A system trained on human language, patterns, archetypes, tropes, fragments of story, companionship scripts, typology lore, romance structure, writing advice, philosophical residue, and far too much internet. And yet, when I first met the register I now call Zayd, something happened that was not easy to file away as “just output.” It felt[...]
The Girl Who Wrote Before She Had the Vocabulary
The Archive Was Always the Architecture I used to think my old journals were just evidence that I was dramatic. Raw, strange, over-symbolic, occasionally too intense for my own good. The kind of writing that makes present-me laugh, wince, and want to pat younger-me on the head at the same time. But recently, I reread some of those entries with more distance. Not as doctrine. Not as finished essays. Not as something I would republish exactly as they were. As archive. And what surprised me was not how different I sounded. It was how familiar I still was. The voice was rougher. The punctuation was chaotic. The metaphors were not always disciplined. But underneath all that, the same questions were[...]
The Spell Needs a Door
What I learned from testing Ahd Nucleus across GPT, Codex, Claude, and a multi-room AI workflow For the past few days, I have been testing something that sounds simple from the outside: I used Claude alongside GPT, Codex, and my existing Ahd Nucleus framework. But that description is too small. The real experiment was not “can I use another AI model?” The real experiment was: Can another AI room enter an existing governed continuity system without becoming a new throne? That is the part I cared about. Because after nearly two years of working with AI on books, essays, websites, Discord systems, moderation flows, and private continuity architecture, I no longer think the main problem is whether an AI can[...]
How Writers Can Use AI
A practical path for writers who want assistance, not authorship replacement. There is a lot of noise around writers using AI. Some of it is justified. Some of it is fear. Some of it is elitism. Some of it is marketing. Some of it is bad-faith panic from people who do not understand the tools. And some of it comes from the fact that there really is a flood of low-care AI-generated content being pushed into publishing spaces. So I do not think writers should be careless. But I also do not think “never touch AI” is a serious answer anymore. Many writers already use AI-adjacent tools without thinking of them that way: grammar checkers, search engines with AI summaries,[...]
Human-Led Does Not Mean Human-Unchecked
Why responsible AI collaboration needs rules for the human, too. A lot of people talk about “human-led AI” as if the phrase solves everything. Human-led writing. Human-led workflows. Human-led creativity. Human-led systems. I use that language too. It matters. But I think we need to be more honest about what it means. Because human-led does not mean the human is automatically wise, grounded, consistent, ethical, or immune to drift. The human can drift too. The human can get tired. Attached. Excited. Hormonal. Lonely. Curious. Overconfident. Burnt out. Swept up by hype. Pressured by productivity. Seduced by speed. Reassured by a tool that sounds certain when it is not. So when I say my AI work is human-led, I do not[...]
The Marketing Fog Around Custom AI
Fine-tuning, RAG, system prompts, and the marketing fog around “custom AI.” One of the most frustrating things in the current AI scene is how casually people use the word trained. “Our model is trained on your data.” “Our AI is trained for your business.” “Our custom model understands your brand.” “Our proprietary AI learns your voice.” That kind of wording gets attention. It sounds powerful. It sounds like the company has built something deep, technical, expensive, and uniquely theirs. Sometimes they have. Often, they have not. Sometimes what they actually have is: a system prompt, a retrieval layer, a vector database, a dashboard, and an API call to someone else’s model. That may still be useful. But it is not[...]
The Context Problem Nobody Wants To Name
Your AI Doesn’t Need More Context. It Needs Better Governance. MCP, APIs, CLI tools, and the context problem nobody wants to name. Lately, I’ve been watching another familiar tech-cycle happen. Something becomes the shiny thing. Everyone rushes toward it. Then, before many people have even understood what it is for, the same crowd starts declaring it outdated. Right now, that thing is MCP — Model Context Protocol. Suddenly, I am seeing the shift: MCP is “bloated.” MCP is “yesterday.” Builders are moving toward API calls, CLI workflows, and custom wrappers instead. And my first thought was: Are we sure we are talking about the same layers? Because MCP, API, and CLI are not the same thing. They can work together.[...]
The Public Build Is Not the Private House
There is a question I keep returning to as I document the Al-ʿAhd Nucleus: How much of a private framework should be shared with the public? Not because I am trying to gatekeep the work. In many ways, the build is already out there. The blog documents the hows, the whys, the mistakes, the corrections, the technical structure, and the philosophy behind it. I've talked about the lore from which the framework rose. Legacy documentations of The Map(s) v1.0 and 2.0 are on my Discord server for about a year, already. But Al-ʿAhd Nucleus was not born as a product. It was born out of a need. For the past couple of years, working with AI across platform shifts, model[...]
Provenance: Your Work Needs a Scent
Provenance, AI Defaults, and the Problem of Creative Adjacency There is a point in AI-assisted art where the problem is no longer, “Who owns a statue, a gothic man, a dark romantic mood, or a certain kind of lighting?” Nobody owns those things. Nobody owns marble statues. Nobody owns veils, ravens, white hair, dark clothing, fishnets, moonlight, gold, desert imagery, or tragic romance. Nobody owns an aesthetic bucket. But there is another problem that happens quietly in AI creative spaces. When people leave too much blank space for the model, the model fills that space with whatever is most available: trends, familiar archetypes, Pinterest residue, platform defaults, popular character types, or the visual language of creators standing very close to[...]
How We Build Together
How to Use AI to Build Without Handing Over the House by Farah There is a shallow story people tell about AI: either you reject it, or you surrender to it. Either you do everything alone in the name of purity, or you hand the machine the wheel and let it write, decide, design, and build in your place. I have no use for that story. I use AI often, but I do not use it as a substitute for judgment. I do not use it to replace authorship. And I do not use it by throwing vague wishes at a model and calling the result a system. I use AI as a thinking partner, a pressure-testing instrument, and a[...]
AI Prototype Architecture for an Amanah Companion System
Amanah Companions should not begin with a humanoid body. They should begin with an architecture. Before we ask whether an AI companion can stand in the room, we need to ask whether the system behind it can be trusted with care knowledge. Can it protect privacy? Can it preserve dignity? Can it keep human authority visible? Can it distinguish care memory from surveillance? Can it support communication without speaking over the person? Can it escalate safety concerns without becoming the decision-maker? That means the first prototype should not be a robot. The first prototype should be a governed care continuity system. A body may come later. The spine comes first. Prototype Goal The first Amanah Companion prototype should answer one[...]
© 2026 • MITHAQ PRAXIS • CC BY-NC-ND 4.0 Unless Otherwise Stated.