Portfolio
Back to selected projects

AI emotional narrative product · Plan V1.0

Life Exchange

Let both versions be fully seen without interrupting each other

Designed for two people who know each other but struggle to explain an experience. Private expression, separate confirmation, and shared narrative help both sides revisit the same event or period of life.

  • Dual Narrative
  • Privacy Design
  • AI-assisted Expression
  • Next.js + Supabase
Life Exchange cover showing two people revisiting a shared experience on a bridgeLIFE EXCHANGE / V1.0
01

Problem framing

Some experiences remain untold because there is no uninterrupted space

Instant chat invites reactions before a story is complete, while diaries remain private. Generic AI may generate text but rarely defines consent, visibility, and publishing boundaries for two people.

01

Interrupted expression

Questions, defenses, or emotion can redirect a story before either person explains it fully.

02

Unshareable material

Private notes preserve details but lack an appropriate way to organize and deliver them.

03

Unclear permissions

AI may help with language, but it cannot consent, publish, or expose the other person's private content.

02

Dual-perspective model

Two choice axes create four narrative paths

Choose an event or a period of life, then decide whether to complete it alone or invite the other person. Select a combination to see how its flow and outcome change.

Flow view

One event · Both

One specific event
Independent submissions
Hidden until both submit
Shared story / picture book
Current flow
A
B
  1. 1Separate expression
  2. 2Independent submit
  3. 3Shared nodes
  4. 4Dual confirmation
03

Privacy by design

Protect expression before building shared understanding

In dual mode, both narrative tracks remain invisible to each other before submission. Shared output appears before source drafts, whose visibility follows rules confirmed in advance.

ABefore submission · Private

Each person sees only their draft, AI suggestions, and confirmation state. The other person cannot preview, rush, or edit it.

A + BAfter both submit · Shared

The system builds a shared story from locked snapshots while preserving common clues, both viewpoints, and unresolved differences.

04

Product decisions

Make understanding the outcome, not a relationship score

A

AI organizes, users decide

AI asks, structures, and drafts candidates; users confirm everything that is published.

No judgment, diagnosis, or relationship scoring.
B

Solo journeys can finish

A user can complete a personal story without waiting for an invitation to be accepted.

No streaks, rankings, or pressure loops.
C

Shared output preserves difference

The result includes common ground, A's view, B's view, and what remains unresolved.

No invented dialogue, motives, or reconciliation.

Structured PRD · V1.0

Product requirements document

This web reading version is organized from the complete PRD. The plan still awaits open-question confirmation before engineering breakdown; the current demo and formal-product boundaries are stated separately.

Context and positioning

Life Exchange is a desktop-first web product for two people in an existing relationship. It turns hard-to-explain experiences into readable personal or shared stories, while explicit submission, visibility, and confirmation rules protect both people's boundaries. Its goal is to help both sides see, not force agreement.

Target users and core needs

Two people in a close relationship

Tell the same event completely without turning an instant conversation into an argument.

People in a long-term relationship

Organize multiple moments across a shared period and compare different timelines.

Someone who starts alone

Finish their version first, then decide whether to invite, send, or reveal source content.

Product goals

  • Reduce the pressure of starting
  • Keep AI optional and require confirmation
  • Keep dual narratives independent before submission
  • Accumulate a life period through time and events

Non-goals

  • No stranger matching or public community
  • No instant chat or endless reaction feed
  • No relationship diagnosis, scoring, or advice
  • No streaks or participation pressure

Four product combinations

ModeExpressionReveal timingCore output
One event · Only meCompleted alone

Sent after author confirmation

Personal story / picture book

One event · BothIndependent submissions

Hidden until both submit

Shared story / picture book

A life period · Only meOngoing solo record

Author decides after organizing

Personal timeline / picture book

A life period · BothIndependent timelines

Shared after both submit

Dual timeline / shared book

End-to-end flow

  1. 01
    Set the rules

    Choose scope, participation, delivery, and visibility before creating the relationship space.

  2. 02
    Express privately

    Write independently, optionally use AI, and confirm the source material for generation.

  3. 03
    Submit and lock

    Dual mode locks separate snapshots; neither source is visible until both submit.

  4. 04
    Build shared output

    AI drafts a shared story that preserves differences; both people review and confirm separately.

  5. 05
    Read and archive

    Read, respond, and reveal source drafts according to the agreed policy; resolve disputes before archive.

AI role and privacy boundary

AI assists expression; it is not a relationship judge. It can only organize user-confirmed material and cannot bypass publishing or access rules.

  • Never send or consent for users
  • Never invent dialogue, motives, or reconciliation
  • Keep generated passages traceable to sources
  • Allow rejection, regeneration, and dispute flags

MVP and current demo boundary

The current demo is a base-flow sample for one event, not evidence that the complete PRD is implemented. A formal MVP still needs server-side state, real identity and relationship spaces, dual snapshots, and Supabase RLS.

Retain
Current event writing, organization, preview, and reading components.
Add
Life timeline, dual snapshots, shared generation, proofreading, and dual confirmation.
Refactor
Replace browser-state permissions with a server state machine and Supabase RLS.

Proposed validation metrics

These are proposed metrics, not claimed production results.

Create
Rule setup and creation completion
Express
First valid content and AI candidate adoption
Collaborate
Invitation acceptance, dual submission, and effective days
Read
Open, completion, and lightweight response
Confirm
Dispute flags, regeneration, and dual confirmation

Current prototype

Experience the current one-event foundation

The demo opens in a new tab. It demonstrates the current product direction without presenting the planned dual state machine, life timeline, or full permission model as finished features.Open the Life Exchange demoExternal site · exchange-life.786383431.workers.dev
exchange-life.786383431.workers.dev

Current boundaryThis demo is a foundation sample for the formal plan. Device requirements, login conditions, and the complete recommended path are still pending confirmation.

Product questions worth observing

  1. 01How expression starts

    Notice how the product lowers the pressure of beginning one story.

  2. 02How AI participates

    Check whether AI offers structure without taking over user decisions.

  3. 03How output is read

    Observe the transition from private expression to a readable story.

Back to homepage projects