MEMORY & CONTROL

Continuity without
a hidden scrapbook.

Memory should make a conversation more useful, not make the user wonder what the system knows.

NO MYSTERY PROFILE

Useful context.
Visible to you.

The design goal is simple: continuity should not require a hidden scrapbook. A memory should be understandable, correctable, and removable.

DESIGN INTENT

A visible memory model.

01

Notice

The product can identify a detail that may help a future conversation.

02

Ask or show

The candidate memory is surfaced instead of being silently buried.

03

Review

You can see what is kept and why it may be useful.

04

Edit or remove

You can correct a detail or remove it when it no longer belongs.

05

Start over

Account and deletion controls are planned as first-class product actions.

LAUNCH NOTE

Claims will match the shipped product.

These screens describe the intended product direction. Exact retention periods, export formats, deletion timing, and subprocessors must be documented before public testing.

Private preview

A conversation that keeps its place.

SomeoneFor.Me is being prepared for a small adult beta. The waitlist is not connected in this design preview.

See the preview