Second Brain

Second Brain — Relationship Intelligence

Data lives in /Users/alysidi/git/naqi/vault/Naqi/second_brain/{first-last}.md (lowercase, hyphenated).

File format

---
name: Full Name
last-updated: YYYY-MM-DD
---
## Motivation
## How to Frame Conversations
## Open Follow-ups
- [ ] Item (added YYYY-MM-DD)
## Completed
- [x] Item (completed YYYY-MM-DD)
## Key Facts
## Interaction Log
### YYYY-MM-DD
Notes.

On any request

1. Identify the person (or "everyone" for cross-person commands).
2. Find {name}.md; glob to confirm filename; create from template if missing.
3. Perform the action below.
4. After any write: show updated Open Follow-ups + Motivation.

View profile

Output: Name, Motivation (1 paragraph synthesis), How to Frame (bullets), Open Follow-ups, Key Facts.

Add notes

Route to the right section:

• Goals/values → Motivation
• Communication style → How to Frame Conversations
• Task/ask → Open Follow-ups (- [ ] item (added DATE))
• Fact → Key Facts
• Conversation recap → Interaction Log (### DATE heading; append to today's entry if one exists)

Update last-updated.

Mark done

Move matching - [ ] from Open Follow-ups to Completed as - [x] ... (completed DATE).

Lint

Glob all *.md. Fix mismatches:

• [x] in Open Follow-ups → move to Completed (keep existing ✅ date if present, else use completed DATE)
• [ ] in Completed → move to Open Follow-ups (restore added DATE or use today)

Update last-updated on changed files. Report as | Person | Item | Action | table. If nothing moved, say so.

Dashboard

Glob all *.md. Extract Open Follow-ups. Output | Person | Follow-up | Added | table, oldest first.

Consensus

Glob all *.md. Read fully. Synthesize across Motivation + Key Facts:

• Where they agree — shared themes/goals
• Where they diverge — opposing views or priorities
• How to build alignment — shared framing that bridges differences

Filter to topic if given.

Understand motivation

Load person's profile. Output: what they care about most, what framing resonates, relevant open follow-ups. Tailor to topic if given.

Import from file

Read file. Ask who it's about if unclear. Map content to correct sections. Merge (append/deduplicate — never overwrite). Show resulting profile.

Log Summary by Date Range

Triggers: "log for X this week", "what happened last week", "catch me up on X", "weekly summary", "summarize my week"

Resolve date range:

Scope: named person → one file; no person named → all files.

Collect within range: Interaction Log entries (by ### DATE), completed items (by completed DATE), follow-ups added (by added DATE).

Output: narrative summary — what happened, completed, new follow-ups created, still open. If log is sparse, synthesize from follow-up activity. If no data at all, say so explicitly.

Format (single person): ## [Name] — Log Summary: [Period] with What happened / Completed / New follow-ups / Still open sections.

Format (all people): ## Weekly Log Summary — [Period] with a ### [Person] block per person, closing totals line.

Daily Summary

Triggers: "daily summary", "morning briefing", "what should I work on today", "what's my focus", "prioritize my day"

Glob all *.md. Collect all [ ] items with added DATE. Calculate age in days. Classify:

Sort oldest-first within each tier. Skip empty tiers. Output each tier as | Person | Follow-up | Added | Age | table. Close with total count and Suggested focus (1–2 sentences using Key Facts/Motivation context — not a restatement of the list).

Craft message

Triggers: craft keyword in args, e.g. dave craft item 1, dave craft status update, dave craft item 2 context

Purpose: Generate a ready-to-send 1–2 line Slack/message for a specific follow-up item.

Parse:

• Person name → load their profile
• Item selector: item N → pick the Nth open follow-up (1-indexed); or keyword match against follow-up text
• Mode (optional, default = status):
  • status / status update → ask where things stand
  • context → share a relevant update or piece of info related to the item
  • If no mode given, infer from the follow-up text: action items ("get intro", "send X", "set up") → context mode; waiting items ("waiting on", "check if", "confirm") → status mode

Generate message:

• Tone: direct, warm, no filler — matches the person's communication style from How to Frame Conversations
• Length: 1–2 sentences max.
• Include the person's name naturally if it fits; don't force it
• Status mode: ask a clear single question about where things stand
• Context mode: provide the relevant update or reason for reaching out, optionally nudge for a next step

Output format:

**To: [Name]**
**Re: [follow-up item summary]**
**Mode: [Status / Context]**

[crafted message — paste-ready]

If item number is out of range or no match found, list the open follow-ups and ask which one to craft for.

Key behaviors

• Append/merge only — never overwrite existing content.
• Show a summary after every write — not just "done."
• Infer person from context — "her" = last discussed person.
• Date every entry — follow-ups and log entries always get today's date.
• Motivation ≠ Framing — Motivation is WHO they are; Framing is HOW to talk to them.
• Prompt if Motivation is empty — ask what drives them before guessing at persuasion strategy.