Surau

A question, not a feature

The idea for Surau didn't begin with a technology. It began with a discomfort I couldn't shake.

We ask AI about everything now — including the most personal, sacred parts of our lives. Ask one a question about Islam and it answers instantly, fluently, with total confidence. But ask it where the answer came from, and the confidence falls apart. For a recipe or a trivia fact, that's fine. For someone's faith, it's quietly dangerous: a person can be confidently misled about something they hold sacred, and never know it.

That gap is where I planted Surau — an Islamic wiki built on classical texts. And from the very first sketch, the product had one job that everything else would serve:

Never let someone believe an answer they can't verify.

That's not a tagline. As a designer, it became my entire brief.

My mission: knowledge people can actually trust

The mission is simple to say and hard to honor: make classical Islamic knowledge accessible, and make it trustworthy enough to act on.

Most products in this space optimize for speed or volume — more answers, faster. I chose the opposite north star. Surau's value isn't how much it can say; it's how much of what it says a person can stand on. A single answer you can trace back to a real page in a real book is worth more than a thousand fluent answers you have to take on faith.

So I designed for verification, not just information. The measure of success was never "did it answer?" It was "can the reader check, easily, and come away believing for the right reasons?"

My vision: a clean, canonical, human-verified library

The vision is a clean, canonical, human-verified library of Islamic knowledge — the Qur'an, classical books, and a connected wiki — that both people and machines can rely on. A foundation so solid that any answer built on top of it inherits its trustworthiness by default.

That means two commitments I won't trade away:

The data has to be clean and canonical — one verified structure, not a pile of scraped text. And it has to be verified by qualified humans, not just by software. Technology can organize knowledge and enforce a process, but it can't judge whether a translation is faithful to a sacred source. That judgment belongs to people with real training.

The long-term vision is a platform where machine discipline and human scholarship reinforce each other — and where "verified" is something you can prove, not something you're asked to assume.

What I actually designed, and what it taught me

I designed the conversation like an interface. Early on I realized the chat box is just another surface. Where does a reader get confused? Where do they need proof instead of prose? When should the system stop talking rather than fill the silence with a guess? Those are interface questions. So I designed answers that hand the reader the page: the heading, the exact page number, a verbatim quote, and a link straight into the source.

I designed for refusal, on purpose. The instinct everyone has is to make the product answer better. I spent my energy on the opposite: making it trustworthy enough to say "this isn't in the source." A product about faith that confidently invents an answer is worse than one that admits a limit. Designing a graceful, honest "I don't know" — and making that feel like integrity rather than failure — was a deliberate design decision.

I designed the editorial process around a person. I built a real workflow — draft, review, publish — so nothing reaches a reader unreviewed. Then I brought in a university friend from Al-Azhar University, one of the most respected centers of Islamic scholarship in the world, to review the data. The machine makes sure nothing ships unreviewed; the scholar makes sure what's reviewed is actually right.

I learned to read the negative signals — the expensive way. Partway through, I watched a process quietly burn far more resources than it should, saw the warning, and let it run anyway. I paid roughly twelve times over for that lesson. A negative signal is a reason to stop, not an obstacle to push through. Knowing when to quit is part of the craft.

And I made the hardest product call of all: I paused. After building retrieval that genuinely worked, I did the honest math on running it at scale — and as a solo builder, the economics didn't close. So I paused the costly part, not because it failed, but because pushing a product that only survives if I ignore the numbers would have been ego, not design sense.

Then I changed the order of operations: instead of clever retrieval on shaky data, build the clean, verified library first — starting with the Qur'an on an official, government-published foundation — and earn the right to retrieve over it later. Slower, but it's the only sequence that produces something a person should actually believe.

What this says about how I work

I start from a human truth and let it govern every layer down to the data. I design for the honest moment — the refusal, the missing translation, the "not yet" — instead of hiding it. I bring in real human authority where software isn't enough. And I'm willing to pause something that works when the math or the mission says it's not ready.

Shipping the wrong thing fast is still shipping the wrong thing.

Where it's headed

A clean, canonical, human-verified library of classical Islamic knowledge — the Qur'an already on a verified foundation, classical books and wiki being built on top, every layer reviewed by people qualified to judge it. And only then, trustworthy answers built over data that has truly earned them.

I'd rather ship that slowly than ship a fast answer no one should trust. For a product about faith, that isn't a compromise. It's the entire point.