Prepared for Michael Smorenburg · Confidential capability brief
"Your life should not disappear when memory, time, or death takes it away."
A voice-first life capture engine. A person speaks, and a living archive of their life takes shape, ready to become books, audio, letters and legacy.
MyLife Story is a modular, AI-driven autobiographical assembly platform. A person speaks naturally, the system understands and structures what they say, and a living archive of their life grows from every conversation. It is a voice-first life capture engine, and it becomes whatever a life needs it to be.
People do not fail to record their life story because they cannot write. They lose it because memory fades, time runs out, and the people who hold the stories pass on. MyLife Story is built for that fear.
Memories arrive out of order, across many sessions, a childhood home here, a lost friend there, a turning point years later. MyLife Story resolves them onto a single timeline, where every person, place and theme links to the memories that mention it.
Exact dates are optional. Decades, approximate ages and "sometime in the seventies" are all welcome, and the system can spot the gaps and ask about them.
The opening of the story, with room for an uncertain date.
The home by the bay, and the deck a father built by hand.
MyLife Story is delivered as discrete modules on one shared archive. Each does its own job, and together they take a life from the first spoken memory all the way to a finished book or audio memoir.
Welcomes the person, shows how far their story has come, and puts the next interview and their finished outputs one tap away.
The heart of the product. A patient AI interviewer asks, listens and adapts to what is said, in guided, free-flow and emotional follow-up modes, by voice or by typing.
A chronological map of a life, from birth and childhood through homes, work, travel, losses and turning points, with room for approximate dates and decades.
Builds a profile of everyone mentioned, their relationship, era, linked stories and emotional tone, then offers to assemble their chapter.
Holds the meaningful places of a life, their city and era, the people and events tied to them, and the images that bring them back.
Surfaces the deeper threads of a life, survival, love, loss, migration, reinvention, faith and resilience, reflectively and never psychoanalysing.
Generates books, audio, letters, tributes and exports from the archive. This is where value is unlocked, and it has its own showcase further down.
Stores photos, scans, letters, certificates, voice notes, video, diaries and clippings, then tags, transcribes and links each to the right story, person and date.
Every extracted fact is editable. A person can correct a date, name, place or emotional reading, merge duplicate people, mark a memory private, or flag it for follow-up.
Manages users, subscriptions and usage, tracks interview, transcription and output volume, storage and system health, and supports exports and abuse control.
A person speaks and sees their words transcribed live, while the interviewer reads its questions aloud in a warm, patient, unhurried voice built for older speakers and many accents.
After every session it returns a summary, the people, places, dates, events, emotional tone, story importance, a likely chapter, follow-up questions, gaps and privacy flags, with validation so malformed output never breaks the app.
The danger is building a pretty chatbot that produces one long, unusable transcript. The power is structure. MyLife Story never stores a life as one blob of text. It turns every memory into data the system can use again, which is what lets a single conversation become a timeline, a person's chapter, a themed memoir and an audio version, all from the same source.
From a single archive, the Output Studio produces a full range of emotional and commercial outputs, from a short life sketch to a complete autobiography, an audio memoir, a tribute or a full family archive. The same conversation, turned into whatever a person and their family need.
Outputs span entry, premium and human-assisted tiers, so the same archive serves the person, their family and the institutions that hold many lives. Beyond the individual, MyLife Story is built to capture lives at scale, before they are lost.
"Capture the life stories of residents before they are lost."
A life story is the most personal thing a person can hand over. These commitments are designed into the product, not bolted on, and they matter as much as any feature.
A person can mark any memory private, exclude it from a book or the family version, delete it permanently, or export everything. Sensitive subjects are handled with care, and something can be preserved privately without ever being published.
Every screen is built so a person feels heard, respected, unhurried, proud and in control. No sterile forms. Meaning is reflected back warmly, never overreached.
The AI proposes, the person decides. A wrong date, name, place or emotional reading can be corrected, merged, hidden or confirmed at any time.
The system interviews and assembles, but the person always owns the truth of their own life. Nothing is published or shared without their say.
How the AI is used, how transcription works and where data is stored are stated plainly. Consent is explicit, and the archive can be downloaded or deleted in full.
A person's own account is preserved as the source. Structure is layered on top of it, it never overwrites what was actually said.
MyLife Story is a voice-first interview engine wrapped around a structured archive. Delivering it well depends on a small set of capabilities, each with a simple first version and a stronger second one.
The danger is a pretty chatbot. The opportunity, and the real intellectual property, is the structured memory extraction and legacy production engine behind the conversation. The interview screen is the doorway. The archive and the Output Studio are the product.
A diary app stores text. A chatbot answers and forgets. MyLife Story listens, understands, structures and keeps, then turns one life into many enduring things. The value is not the talking. It is everything the talking becomes.
The MVP is deliberately small: sign in, an interview screen, voice to text, AI follow-up questions, saved transcripts and summaries, basic people, place and event extraction, a simple timeline, a short generated biography and a text export. From there, capability is added one phase at a time, each building on the one before.
Auth, dashboard, the interview module, database tables and transcript saving.
Microphone input, live transcription, AI question playback and a typing fallback.
Dynamic questioning, session memory, follow-up logic and topic modes.
People, places, events, themes and timeline entries from every session.
Summaries, short biography, chapter outline and export.
Uploads, AI tagging and linking media into the story.
Subscriptions, paid exports and premium packages.
These phases describe sequence and dependency, not a calendar. The MVP ships first, and each later phase builds on the one before.