Mahd Qureshi

Engineer. Toronto.

I'm 21 and usually somewhere between a neural network, a game mechanic, a film idea, and a math rabbit hole. I like hard problems, small teams, and fast feedback.

I grew up across several countries and moved on my own to boarding school in Canada as a teenager, which mostly means I've had a lot of practice at being the new person in the room. I'm on my fifth language. Progress is steady in the way glaciers are steady.

01 / Now

What I'm working on now

  • Shipped v0.2 of Continuity Engine. The v0.1 README listed four things as next; all four are in. Turns out publishing a roadmap is an effective way to make yourself finish it.
  • Building an iOS product I'm not naming yet. Voice interface. Most of the work so far has gone into teaching it to wait for the end of a sentence, which humans manage without being told.
  • Reading more mathematics than I have any professional excuse for.

02 / Selected work

Selected work

Continuity Engine

v0.2 · JavaScript · zero dependencies · zero API calls

A deterministic character-continuity engine for interactive stories that remembers choices, updates emotional state, and explains what should happen next.

Most AI character prototypes hand memory and narrative decisions to a model, which makes the resulting path hard to replay or inspect. I wanted to test a narrower question: can character continuity be small, deterministic, and inspectable instead?

Every choice becomes an immutable event, and current state is rebuilt by replaying them — reproducible rather than quietly mutable. Emotional state decays toward a per-character baseline over simulated time:

A constrained beam search then proposes a three-beat narrative path. The same events always produce the same result, and you can expand the decision trace to see why.

  • event sourcing
  • beam search
  • property-based tests
  • architecture decision records
  • CI

iOS product unreleased

In progress · Swift · TypeScript · Postgres

A native iOS app with a voice interface, backed by a TypeScript API. Private while it's still being built.

The hard parts have been on the input side. Hearing a whole sentence including its pauses, instead of cutting someone off at the first silence. Dropping the wake-word dependency so the thing can actually run on a phone. Keeping a demo environment alive long enough to be useful, and reporting clearly when it breaks.

Happy to talk through the architecture directly.

03 / How I work

How I work

  • No filler repos. One project at a time. It goes public when it's actually good.
  • If it isn't reproducible, I don't trust it yet.
  • Write the docs and the tests as part of shipping, not after.
  • Say the honest version of what a thing does, including what it doesn't.

04 / Off the clock

Off the clock

Basketball, volleyball, track, and skateboarding — roughly in order of how often each one has injured me.

Otherwise: film, games, and mathematics. Ask me about any of the three and you should expect to lose an hour.

05 / Build with me

Build with me

I'm building my own things and I'm looking for people to build them with. If you're working on something hard and small — or you want to be, and you're looking for someone who'll actually ship it — tell me about it.

I read everything. I reply to anything specific.