Why operators run a morning brief before email

Opening email first hands your morning to whoever shouted loudest overnight. A command brief inverts that: your operation speaks first — deals aging, revenue logged, leads found, journal mood, energy level — then you decide.

mxstermind briefs stream over SSE from Gemini with Groq fallback. They are grounded in Supabase: open deals, client count, MRR, brief streak, leads this month, and personal context from yesterday's journal.

Focus action chips parse from the brief text — one-click jumps to the deal, role, or venture the brief names. Today's #1 action bar sits above the stat grid so priority is visible, not buried.

brief_streak increments when you complete a brief before the 36-hour window closes. StreakAtRisk warns you before you lose it. DailyPullBanner nudges you when last_brief_at is over 20 hours ago.

Week recap on Sundays summarizes leads, revenue, and streak — with a one-click draft post for Content Studio. Celebrations fire on milestones: first lead, first deal, streak-7, first revenue.

The brief is not a static template. Brief v2 pipeline scores deal health, injects pattern insights on Mondays, and surfaces RelatedInsights from semantic search when embeddings are enabled.

Command runs the professional brief by default. Personal command at /app/personal/command runs a separate stream focused on energy, identity steps, and life goals.

Mode switch in the sidebar keeps both contexts one click away without duplicating accounts. Journal entries from the prior day feed into the professional brief when relevant.

Auto-brief on return is configurable in settings. First visit of the day triggers shouldAutoBrief from last_brief_at — you land on Command and the brief starts.