October 12, 2025
Oni is not a “memory layer platform” pitch. It is a personal journaling agent: asynchronous, memory-aware conversation for life tracking. You message it casually (low friction, like texting). It decides what matters (not everything is stored the same way). It remembers over time. And it comes back to things intelligently. That last piece is the wedge.
Most journaling tools store and maybe summarize. Oni is built to track narrative arcs and re-engage when it actually matters.
What Oni is
Oni = asynchronous, memory-aware conversation for life tracking.
- Message casually: no required structure. “I had a weird convo with my manager today” is enough.
- Interpretation is invisible: entities (manager, job), themes (stress, conflict), emotional tone, and “open loops” get extracted from plain language.
- Selective memory: salience matters. Recurring themes, emotional spikes, and unresolved situations rise to the top; noise does not.
- Structured store, not raw dumps: memory looks more like “Work → Manager → tension increasing” or “performance review stress (three mentions over two weeks)” than a chat log.
- Re-engage: the product either works here or it does not.
Without follow-ups that feel human and timely, Oni is just ChatGPT with memory or a nicer notes app. With them, it becomes a system that maintains continuity in your life narrative. That is rare.
The loop
Everything rests on a tight loop:
1. Capture (frictionless)
SMS and WhatsApp via Twilio. No forms. You send voice-of-thought messages when you actually have them.
2. Interpret
The system pulls entities, themes, tone, and candidate open loops from unstructured text.
3. Select
This is where most apps fail. Not everything becomes memory. You need salience: emotional intensity, repetition, unresolved state. Too much stored → noisy and annoying. Too little → it feels dumb.
4. Store
Structured chronicles, not append-only logs. The goal is a selective chronicle of what matters for your story over time.
5. Re-engage
Examples of what “good” looks like:
- “Hey, how did that conversation with your manager go?”
- “You mentioned feeling burnt out last week. Still feeling that way?”
- “Last time you were excited about the gym routine, did you stick with it?”
That is not journaling as storage. That is continuity.
A concrete arc
Day 1: “Thinking of quitting my job honestly.”
Day 3: “Had a rough meeting today.”
Day 10, Oni: “You’ve mentioned your job stressing you out a few times. Is this something you’re seriously thinking about changing?”
Day 25: “You were considering leaving your job earlier this month. Has anything changed?”
That pattern is the bar: references specifics, respects timing, feels like someone noticed.
The hard parts
Selective chronicle is the core technical and product problem. Heuristics have to balance emotional intensity, repetition, and open loops without drowning the user.
Follow-ups must feel human, not robotic reminders or generic nags. Timing beats copy: too soon is annoying, too late is irrelevant. You end up thinking about decay, priority queues for open loops, and when silence is the right answer.
Tone sits between therapist (too heavy) and productivity coach (too transactional). The target is closer to: a good friend who remembers things you forgot you said.
Positioning (sharp edge)
Not: “AI journaling app.”
Closer to: text a system that remembers your life and follows up when it matters.
Core surface area I’d keep for a v1:
- Text-first interaction (SMS / WhatsApp)
- Memory extraction (mostly invisible)
- Follow-up engine (visible value)
- Occasional reflection summaries (weekly / monthly)
How this connects to a broader memory story
Oni is a strong v1 for personal capture and recall: one clear product before folding in calendar, tasks, external content, or other systems. The Memory Layer idea grows from something that already proves continuity and trust, not the other way around.
The test
If someone would feel weird when Oni stopped messaging, you built something that matters. If not, it is still just another tool.
Next places to nail in the build: memory schema (what exactly gets stored), follow-up trigger logic (when Oni speaks), and tone rules (how it speaks). That is the product.