Ember

• 

Inspiration

We document our meetings, our code, and our finances—but we rarely preserve the moments that change who we become.

The day you finally start a company. Graduating from university. Beginning again after failure. The conversation that changes everything.

These moments shape us, but they're often forgotten because life moves on.

We built Ember to preserve them.

Ember is not a journal. It's a future-self vault that helps people capture meaningful moments through guided conversations, seal them away, and rediscover them when the time is right.

What it does

Instead of asking users to stare at a blank page, Ember starts a thoughtful conversation powered by GPT-5.6.

From that conversation, Ember creates a structured memory artifact containing:

A meaningful title A Spark that captures the essence of the moment A personal letter to your future self An immutable Ember Promise written by the user A factual Time Snapshot Memory Keywords for future retrieval

Users then choose a future date and seal their Ember.

When it unlocks, Ember doesn't immediately reveal the letter. It first invites the user to remember who they were before showing the Time Snapshot, Promise, and letter, turning the experience into a moment of reflection rather than simply opening saved text.

How we built it

Ember is built with:

Next.js 15 TypeScript Tailwind CSS Supabase-ready architecture GPT-5.6

One of our biggest architectural decisions was separating responsibilities:

The application owns the experience—conversation flow, sealing, vault, unlocking, and reflection. GPT-5.6 owns the language—guiding conversations and generating thoughtful memory artifacts.

This separation keeps the experience predictable while allowing the AI to focus on what it does best.

How GPT-5.6 is used

GPT-5.6 is central to Ember.

It powers:

Guided conversations instead of blank text boxes Structured memory artifact generation Personalized future letters Reflection after an Ember is unlocked

Rather than acting as a chatbot, GPT-5.6 helps transform fleeting experiences into meaningful memories while following Ember's editorial voice and product philosophy.

How Codex accelerated development

Codex was used throughout the project—not just to generate code, but to accelerate the entire development workflow.

It helped us:

Scaffold the Next.js architecture Build reusable UI components Structure routing and application flow Iterate on the Vault and unlock experience Refactor and debug features Maintain development velocity while we focused on product quality

By reducing implementation overhead, Codex gave us more time to refine the emotional experience, AI voice, and product design.

Challenges

Our biggest challenge wasn't technical—it was editorial.

It would have been easy to build another AI journal.

Instead, we wanted every interaction to feel intentional, human, and emotionally honest.

We created a documented product philosophy, froze feature scope early, defined Ember's voice, established editorial standards, and built quality guardrails to prevent generic AI responses.

The result is an experience designed around ceremony rather than productivity.

What we learned

We learned that AI creates the most value when it enhances a carefully designed experience instead of becoming the experience itself.

We also learned the importance of scope discipline. By freezing the product early, we spent the remainder of the hackathon improving quality, storytelling, and user experience instead of continually adding features.

What's next

Ember v1 focuses on delivering a complete Create → Seal → Unlock journey.

Future plans include:

Authenticated cloud vaults Cross-device synchronization Richer Time Snapshots Search using Memory Keywords Voice memories Long-term life timelines

Our guiding principle will remain the same:

Ship memories, not features.

Built With

• gpt5.6
• nextjs
• tailwindcss
• typescript