MVP | My Verbal Promises
A private promise memory for the twenty seconds after a conversation. It remembers what was agreed, not the whole meeting.
Overview
Most meeting tools preserve the conversation. MVP starts after it. When a call ends, the product asks one question: What was agreed?
The user speaks for roughly twenty seconds or types a short recollection. The source is saved first, then separated into promises made by You, promises made by Them, and requests that were never accepted as commitments. Dates and conditions are retained only when they were actually stated.
The result is not another transcript folder. It is a relationship-based ledger with an owner, context, source and lifecycle for every promise.
- Voice capture with a typed fallback
- Immediate browser save before processing
- You / Them / Request separation
- Active, Done, Changed and No longer relevant states
- Relationship timelines and promise search
- Calendar handoff and installable PWA shell
Product Logic
The first design decision was also the most important: save before structuring. A slow model response should never be able to erase a fresh memory. The interface therefore gives an immediate receipt, then resolves people, actions and dates in the background.
The schema is deliberately strict. “Can you send this tomorrow?” is a request until the user says yes. A vague Friday stays vague. An older commitment is never silently closed because a later note sounds similar.
That restraint shaped the visual system too. Warm paper, dark ink, a small coral accent and compact controls keep the product calm enough to use directly after a real conversation. The screen has to lower the cognitive load, not announce the technology behind it.
Trust
No bot joins the meeting. No third party is recorded. The user decides what becomes memory, and the original recollection remains visible beside the structured version.
Optional context such as rushed, pressured or anxious is entered by the user and kept for their future self. It is never inferred, treated as evidence or allowed to change the extraction.
AI accelerated the build. Judgment decided what the product was allowed to remember.
Try the working prototype
The public portfolio demo runs safely in the browser with sample data and local persistence. Typed capture, supported-browser speech recognition, review, search, promise states, people trails and calendar handoff remain interactive; no private API key or judge credential is included.