One Persistent World, Viewed Through Email
The wrong idea, stated clearly so it can be discarded
The obvious move — the one that has been tried repeatedly, produces an excellent demonstration and a flat retention curve — is to put games inside email. A quiz in the Tuesday send. A scratch card in the Friday one. A puzzle in the newsletter.
Each of those is a campaign. Campaigns end. A campaign with a game in it is a campaign with a better open rate for three weeks.
Stacked together they become an arcade — a shelf of isolated experiences, each of which starts and ends. An arcade can produce an appointment: a person may return once a day for a daily word game, the way they return to any single-serving habit. But a shelf does not create a life that continues while the customer is away, and one appointment a day is exactly the ceiling the media income line cannot afford.
The right idea
Do not put a game inside an email. Build a world made of email.
The distinction is architectural rather than decorative. In the first model the email is a container that arrives with content inside it. In the second the email is a viewport — a window onto server-side state that is running continuously, whether or not anybody is looking.
Open it and you see what is happening now: the current score, the open challenge, the deadline that expires in forty minutes, what your Circle did while you were away, where your progression stands, what resolved overnight. None of that was decided when the message was sent. It is composed at the moment it is opened.
This is why the L3-to-L4 inflection — composed at send to composed at open — is the enabling condition for the entire consumer thesis and not merely a technical refinement. A static email is a prediction made at send. A Living Email is a decision made at open. Only the second can be a window onto something live.
The Infinite Email Thread
The delivery form follows from the architecture. Not a campaign, and not a series. One permanent thread from one sender, behaving the way a messaging conversation behaves: new episodes append to it, and each new episode returns the row to the top of the inbox. The thread is the container for the relationship; the episodes are its pulses.
Two properties of this are worth dwelling on, because they are what make the model unusual.
Reopening an old episode shows the current world. Because state is composed at open, episode 38 from last Thursday does not show last Thursday. It shows now. The archive is not an archive — every message in the thread is a live door into the same room. No app inbox and no notification stream has this property, and it means the thread accumulates entry points rather than accumulating dead weight.
The inbox is already the notification layer. No app install. No app store. No push-permission dialogue that most people decline. No home-screen real estate to win. The re-entry mechanism is a row moving to the top of a place the person already checks several times a day. For mass consumer reach in a market like India, that is a structurally cheaper distribution position than any application can occupy.

Figure 2 — The world runs continuously; the thread is the viewport; the pulse score decides what earns an interrupt.
The actual hard problem
If the world is running continuously and the thread can be updated at any time, something has to decide when a change is worth interrupting somebody for. That decision is the product.
Not every state change earns a place at the top of an inbox. A Circle member finishing a challenge might. A leaderboard shifting by one position probably does not. A deadline forty minutes out, for a person who has not yet acted, almost certainly does. The M-Agent layer weighs urgency, novelty, social consequence, the person’s stated preference and how recently they were last interrupted, and then decides which state change has earned the scarce right to interrupt. The job of the agent here is not to generate endless content. It is to say no to almost all of it.
This deserves to be blunt internally. The content is not the moat and the mechanics are not the moat. The pulse-scoring model is the moat, because it is the only part that improves with every open, every mute and every ignored interrupt, and it is the part a competitor cannot copy from the outside.
The condition on all of it
Interactive rendering is not universally supported, and a mass consumer product cannot be designed as though it were.
The fallback build is therefore not a courtesy path. For a large share of any real audience it is the primary experience, and it has to work on its own terms: a static render carrying the world’s state as of the moment of send, with a clear return path into the live view. Fallback-first is non-negotiable. A world that exists only in the interactive render is a world most of the market has never seen.
Key points: (a) The email is not the content. It is the window. (b) A campaign delivers something. A world is somewhere you go back to. Only the second one produces attention worth selling.




