DEV Community: A. F. Sadek

DOXASCOPE: In The Next Place; The Mist Does Not Judge.

A. F. Sadek — Sat, 18 Apr 2026 18:38:48 +0000

DOXASCOPE

المكان التالي | The Next Place

SPOILERS AHEAD!

I am building DOXASCOPE, a bilingual transmedia universe.

It begins as a novel. It expands through an interactive website, scene films, audio, visual fragments, and eventually a game.
But the core is not the format.

The core is a question:

What if something of you remained after death?

Not your memory as a clean archive.

Something stranger: the pattern of you.

Your beliefs. Your contradictions. Your unfinished logic. Your private assumptions about what is real.

In The Next Place, death does not place you in a moral courtroom. It does not simply reward, punish, or explain.

It places you in the Mist.

And the Mist does not judge what you believe.

It responds to how coherent you are.

Like physics.

Not like morality.

The Mist

The Mist is not only a setting. It is the operating environment of the story.

In ordinary fiction, a character can believe one thing, say another, and do a third. That can create drama.

In the Mist, that contradiction has weight.

Identity is a high-resolution file. In the Mist, most are just thumbnails.

Some people become clearer. Some fracture. Some drift. Some cling to systems. Some join structures larger than themselves. Some try to measure the impossible.

The Mist does not answer every question.

It asks better ones.

Four Ways to Survive

The world forms around four major paths.

Each one is a way of surviving truth.

The Fortress

Order through doctrine.

The Fortress believes reality must be held together by structure, obedience, and inherited certainty.

The Drift

Freedom through solitude.

The Drift resists systems. It trusts experience, motion, and the refusal to be pinned down.

The Weave

Strength through unity.

The Weave treats identity as something shared, merged, and carried through collective meaning.

The Network

Truth through measurement.

The Network approaches the Mist like a hostile unknown system: observe, test, map, repeat.

None of these paths is simply correct.

Each one reveals something.

Each one costs something.

Three Doors

At the edge of the journey are three outcomes:

Transcendence.

Transformation.

Annihilation.

These are not just endings. They are consequences.

The story is interested in what kind of person, system, or civilization reaches each door, and what they had to become to get there.

Six Eras

The universe is structured across six eras.

Era Zero begins before time.

The First Era brings matter, stars, and the physical universe.

The Second Era brings life, consciousness, and civilization.

The Third Era is where the Mist begins to take shape.

The Fourth Era is Adam's journey through the novel.

The Fifth and Sixth Eras move into the game and the wider leak of the Mist into other layers of reality.

I do not want the world to feel like lore attached to a story.

I want the story to feel like a visible slice of a larger system.

One Universe, Several Forms

DOXASCOPE is being built through several forms because each one can ask the central question differently.

The novel follows Adam as he wakes in the Mist without memory and tries to understand where he is, what he was, and what the doors mean.

The website is a revelation engine. It does not dump the world at once. It unlocks pieces in controlled layers: novel text, audio, visual fragments, leaks, and eventually wiki reveals.

The scene films turn selected moments into bilingual cinematic fragments.

The game will not be a simple adaptation. It will be another instrument for the same question: how do your beliefs behave when a world starts measuring them?

Why Build It This Way?

Because the idea only works if the form obeys the same law as the world.

The novel is about coherence.

So the project has to be coherent too.

The website cannot reveal everything too early.

The videos cannot explain everything.

The wiki cannot behave like a normal encyclopedia.

The game cannot simply reward "good" answers.

The whole structure has to move like the Mist itself: partial, responsive, layered, and slightly dangerous.

That is the thing I am trying to build.

Not just a story with a website attached.

A story whose architecture is part of the story.

Start Here

Read the first public chapter:

DOXASCOPE — The Next Place | المكان التالي — Enter The Mist

ماذا يبقى منك بعد الرحيل؟ تجربة كشف تدريجي من عالم رواية المكان التالي. The Mist does not judge. It only asks.

doxascope.com

Watch the first scene film:

From the first electron to the last thought:

one story.

The Playbook - To Build A World

A. F. Sadek — Tue, 14 Apr 2026 08:46:16 +0000

I couldn't find the tools I needed, so I built them. Then I built the thing.

Phase 0 - In the beginning, there was no beginning...

This started as scattered notes. Ideas on paper, loose questions, fragments of a world that wouldn't leave me alone. That was about twenty years ago.
I do software engineering by trade. Arabic speaker. I've worked in project management, in tech, in systems. And for two decades, alongside everything else, I've been building something I couldn't explain to anyone in a single conversation.
The short version: a fictional universe that spans a novel, a web game, a website, and the early blueprints for a TV series and comic. All connected. All independent. All built from the same philosophical core.
The long version is the one I want to tell. Not about the universe itself (that has to wait; it's full of spoilers I'll take to my grave before revealing early), but about what it takes to actually build something like this alone.

Start with an axiom. One idea that is true at every scale of your world, from particle physics to character psychology to political structure to game mechanics. Not a theme. A law. If your axiom doesn't constrain you, it's not an axiom. If it doesn't generate consequences you didn't plan, it's not deep enough.

The Novel Problem

It started as a novel. Bilingual, Arabic is the source language, English follows as a parallel draft, not a translation. Two different books wearing the same plot.
The first problem was finding a writing tool that supports Arabic properly. RTL layout, proper typography, the ability to track characters and locations and world rules while writing. I tried everything. Markdown editors. Scrivener-style tools. Novel-writing software. Added RTL to Manuskript. None of them handled Arabic without fighting me.
So, I built this because I needed it. Nobody else was going to.

Write the world bible before you write the story. Derive the factions, the physics, the geography, the economy, and the power structures from the axiom, not from plot convenience. When two systems contradict each other, the axiom wins. When the axiom produces something uncomfortable, keep it.
Write the story in the language it thinks in. Translate later as a parallel work, not a copy. The source language carries things the target language cannot, and that asymmetry is a feature.

The Game Problem - The Framework

At some point, the novel's philosophical framework outgrew prose. The ideas needed to be experienced, not just read. So I started designing a web game.
The game needed its own design document, its own mechanics, its own validation system. I extracted the philosophical skeleton from the novel, the questions it asks about belief, truth, and consistency, and distilled them into interactive systems. Fifteen philosophical conflicts. Four modes of interpreting reality. An endgame that doesn't tell you what's "correct", it shows you what you chose, and what that reveals.
To validate that the system worked before putting it in front of real players, I built a separate tool: a historical profiling simulator. You feed it documented decisions made by real historical figures — Napoleon, Galileo, Curie — and the engine generates a psychological profile. Then you compare the output against what scholars actually say about that person.

The demo is complete. Not deployed yet.

Extract the interactive framework from the fiction, not the other way around. The game, the experience, the simulation — they are lenses on the same axiom, not adaptations of the story. They must stand alone and connect to everything.
Every tool you build becomes infrastructure for the next layer. The tool is not a detour; it is the road.

The Media Problem

The game needed assets. Images, audio, video. I'm one person. I don't have a studio. What I do have is patience and a willingness to test every AI-assisted media tool that exists. I spent months — I've lost count of how many — evaluating and building personal production pipelines. Image generation. Video composition. Audio synthesis. Voice generation with quality control.

I ended up with a set of workflows that let me produce above-average media assets across every format I need. Not perfect. Above average. Consistently. Solo.

For the social media presence, I built an automated reels pipeline. It takes a text beat, generates audio via edge TTS, runs Whisper transcription for quality assurance (I require a 1.000 QA score — perfect transcript match — before any reel goes public), generates timed karaoke subtitles, and composes the final video. Arabic and English variants. Each reel under 59 seconds. I've even recorded the first batch with my own voice.

The pipeline is a Python script with a PowerShell launcher, running locally.

Build production pipelines for every medium you need — image, audio, video, text — and accept "above average, consistently" as the quality target. Perfection is for teams. Consistency is for solo operators.

The Website Problem

I needed a place to put all of this. Not a blog. Not a portfolio. A revelation engine. A website that controls exactly how much of the universe is visible at any moment, with information that can only be unlocked forward, never backward.

So I built that too.
339 tests passing. ~38,600 lines of code across about 250 files.
One developer.

DOXASCOPE — The Next Place | المكان التالي — Enter The Mist

ماذا يبقى منك بعد الرحيل؟ تجربة كشف تدريجي من عالم رواية المكان التالي. The Mist does not judge. It only asks.

doxascope.com

Deploy through a revelation architecture — a system that controls how much of the world is visible at any moment, releases information monotonically, and treats the audience's discovery as a designed experience, not a marketing event.

The Coordination Problem

My workspace currently tracks 113 projects. Most are idle or frozen, experiments, tools, personal projects, and archives from the media pipeline journey. About 14 are actively maintained. The main creative container and its sub-projects are the core.

I coordinate across multiple AI agents: different models for different tasks, routed by complexity and capability. There's a shared context bridge that stays current, a PM layer with automated GitHub sweeps across repositories, and a handoff system so any agent session can pick up where the last one left off without losing state.

I built a memory filesystem for cold-start recovery. I built a shadow export system for feeding project context into retrieval-augmented notebooks. I built commit tracking scripts, backup pipelines, and a coordination document that any new session — human or AI — reads first to understand the current state of everything.

Manage the entire operation as a workspace, not a project. Track everything. Automate what recurs. Route work to the best available tool or agent/or team if you have, by task, not by loyalty. Document for your future self; the most important collaborator you will ever have.

The Patience Problem

Some might see it as distraction. A dead end where projects go to collapse. But I am patient. I have been building for years.
I'm building because I have something heavy to lay down. Not to prove anything. Not to disprove anything. This universe asks a question that I think deserves a world built around it. I can't say what the question is without spoiling everything.

But I can say this: every tool I built, every pipeline, every automation, every agent coordination system. They all exist to serve one thing. A story written in Arabic first, because that's the language it thinks in. Published bilingually, because the story breathes differently in English. Experienced through a website that controls its own revelation. Playable through a game that asks you the same questions the novel asks its characters.

If the work lands, or if it doesn't, I built something real. The tools exist. The pipelines work. The code is tested. The words are written.

And somewhere in that stack of projects and 20 years of fragments, there's a universe that I think has something to say.
It'll say it when it's ready.

And know this: no one will care for a long time. Build anyway. The axiom holds or it doesn't. The audience arrives or it doesn't. The work is the work.