Notes · from the person building Mneva
Holding a promise.
A reminder fires on time. A promise matters at a moment. They are not the same thing, and building for the second is much harder.
Everyone is carrying open loops. The call you said you would make. The decision you keep postponing because both answers cost something. The worry underneath both, which has no due date at all and therefore fits in no to-do app ever built. These loops are the real weight of a life — heavier than the calendar, because the calendar at least admits what it is holding.
The tools we have for this are mostly clocks. A reminder is a clock with a label: it fires at 4 p.m. because you guessed, last Tuesday, that 4 p.m. would be the right moment. Sometimes it is. Mostly the reminder arrives while you are driving, or mid-argument, or in exactly the mood that made you postpone the thing in the first place — and you swipe it away, and now the loop is still open and you have taught yourself to ignore its bell.
The other tool is the streak: turn the loop into a game, score the keeping of it, shame the breaking of it. Streaks work brilliantly for the things streaks are for. But a promise to send your friend something honest before her birthday is not a habit to gamify. A worry about your father's health does not want a progress bar. Scoring these things does not hold them; it flattens them into chores, and people quietly stop telling their tools about anything that matters, because the tool will only turn it into homework.
Mneva's position — it is called Holding inside the product — is that an open loop wants three things a clock cannot give. It wants to be kept in your own words, so that what comes back is what you actually said, not a machine's abbreviation of it. It wants to come back at a moment rather than a time: when the birthday is two days out, when the decision's deadline is real, when you mention the person the promise was for. And it wants to be closable — done, or deliberately let go — because a loop you have decided to release is finished, and a tool that keeps nagging at a released loop has stopped serving you and started farming you.
That last part is a rule, not a mood: either answer closes the loop, and nothing nags twice. "I did it" closes it. "Let it go" closes it just as well, with no guilt screen on the way out. The keeping is never a score, a streak, or a chore — there is nothing to lose by telling Mneva the truth, which is the only condition under which people tell their tools the truth at all.
Mneva is in early access, and this — like everything on this site — is stated with its seams showing: what is built is labelled built, and what is coming is labelled coming. But if you want to know whether a tool understands what you are carrying, ask it one question: what happens to the promise I told you about, on the day it matters? Mneva is being built to have the right answer.