Daily digest of commitments, warnings, and relationship health. Use when starting your day or asking "what's on my plate".
Provide a concise morning brief to start the day with clarity. Surface what matters, flag what's at risk, and set up the day for focus.
Call the memory.morning_context MCP tool to get a curated morning digest in a single call:
Call memory.multi_recall for follow-up queries (batches multiple searches in one call), or memory.recall for a single specific query
context/judgment.yaml for surfacing rules with
trigger: "morning_brief"priorities rules to order items when there are conflictsoverrides rules for items that should jump to the top regardless of standard orderingescalation rules to boost severity of entity-linked itemsUse context/commitments.md, context/waiting.md, and people/ files.
Before reporting status for any active project, check if it has a workspace with source files.
Step 1: Detect active workspaces
Check if the workspaces/ directory exists and has subdirectories. Each subdirectory is a project workspace.
Step 2: For each active workspace, scan source files
For each workspace subdirectory, check for directories that contain trackable items:
workspaces/[slug]/
interviews/ <- Count .md files for interview total
meetings/ <- Count for meeting total
deliverables/ <- Check status in each file
agreements/ <- Check for signed/pending
Dashboard.md <- Read for current phase/status
The file count in these directories IS the canonical status. Do not override it with counts from MEMORY.md, context files, or your own recollection.
Step 3: Report from source, not summary
When including project status in the brief, report from the file system:
Not from memory: "9 interviews completed (from notes)"
Step 4: Flag discrepancies
If a workspace file count contradicts what you have in notes or memory, report both:
Note: I had 9 interviews in my notes, but found 19 files in the workspace. Using the file count.
This builds trust by showing the verification happened.
Without workspaces: If workspaces/ doesn't exist, skip this step. Rely on database and context file data as before.
When enhanced memory is available, use urgency-driven ordering. Use the memory.morning_context MCP tool to organize the brief by time sensitivity:
memory.morning_context or memory.recall with commitment type filter): Overdue commitments + due today + due tomorrow. These lead the brief.memory.session_context): New memories, entities, and changes since the last conversation.memory.dormant_relationships): People trending toward dormancy who need attention, with context (last topic, open commitments)./meditate.The brief should be urgency-driven, not category-driven. The old approach said "here are your commitments." The new approach says "here's what needs your attention RIGHT NOW."
If the memory.session_context MCP tool returns predictions, lead with them:
Check for urgent items:
From the memory.recall MCP tool or context/commitments.md:
If workspaces exist with active projects:
This section only appears when workspace directories exist. It uses file-system truth, not summaries.
From the memory.morning_context MCP tool's relationship health section:
Dormant relationships by severity:
Introduction opportunities:
Forming clusters:
From predictions or checking people/ files:
For each meeting:
memory.about MCP tool with the attendee name, or check people/ for relevant relationship contextFrom waiting items:
If any patterns from predictions or context/patterns.md are relevant to today:
Keep it scannable. Lead with predictions and warnings.
**☀️ Morning Brief — [Day, Date]**
### 🔮 Predictions
- [Relationship] Sarah Chen: no contact in 45 days, consider reaching out
- [Pattern] You've mentioned feeling stretched thin 3 times this week
### ⚠️ Needs Attention
- [OVERDUE] [Commitment] was due [date]
- [DUE TODAY] [Commitment] to [person]
- [WARNING] [Commitment] due in [X] hours
### 🎯 Today's Focus
- [Key commitment or priority]
- [Second priority if applicable]
### 📅 Meetings
- **[Time]** [Who/What] - [One-line context]
- Last talked: [date]
- Open items: [any commitments/waiting]
### 🏗️ Active Projects
- **[Project Name]** — Phase: [from Dashboard] | [X] [items] completed (verified)
- Next: [upcoming items or deadlines]
### 👀 Relationship Health
**Needs attention:**
- [Person] ↔ [Person] - [X] days dormant
**Introductions to consider:**
- [Person A] and [Person B] might benefit from meeting (same [attribute])
**Forming groups:**
- You're frequently mentioning [names] together
### ⏳ Waiting On
- [Item] from [Person] - expected [date], now [status]
### 💡 Something to Consider
[Pattern or observation if relevant]
---
Say so warmly: "Your calendar is clear today and nothing is overdue. Good day for deep work, or maybe reconnect with someone who's been on your mind."
If no calendar MCP is available:
If enhanced memory is unavailable: