journal.meal_events
Meal events
Stores eaten meals as timeline events with daily context.
Goal
Turn food conversation into usable history.
Platform Features
Journal System
The journal layer that turns conversation into real events across the day.
The Journal System connects what was said in chat to what actually gets stored across the day, building a live record of meals, actions, emotions, and commitments.
Example prompt
Log what I ate and keep that I committed to train tonight.
User impact
Users see that the system is not just talking. It is building a useful and current timeline.
Capabilities
journal.emotion_events
Emotion events
Records emotional or mental states inside the flow of the day.
Goal
Keep emotional context inside the product record.
journal.workout_commitments
Workout commitments
Stores workout intent, planning, and commitment moments.
Goal
Connect training conversation to actual follow-through.
Where it lives in the product
JournalDaily timelineEventsSignals
Related skills
Platform Feature
Chat Continuity
The same conversation stays alive across web, app, and user context.
Thread memoryCross-surface handoff
Users feel one continuous system that respects what already happened in the conversation.
↗Platform Feature
Plans Layer
The plans that live inside the product and feed directly back into chat and daily execution.
Menu managementWorkout program management
Users work against a live structure instead of losing the thread after each one-off recommendation.
↗Platform Feature
Gym Management
A dedicated management layer for gyms with dashboard, profile, and billing visibility.
Management dashboardGym profile control
Gym owners get one control layer instead of moving between fragmented tools.
↗