How Everything Connects
This is the architecture of Twill Brain — how emails, CRM contacts, meetings, tasks, and deals are all wired together.
The Connection Map
Email Thread
└──► Person Note (03-CRM/People/)
├──► Meeting Notes (02-Meetings/) — who was in the room
├──► Company Note (03-CRM/Companies/)
├──► GitHub Tickets (04-Projects/) — what was committed to
├──► action_items[] — what's still open
└──► next_follow_up — when to re-engage
Example: ISO Relationship
Incoming email from a new ISO lead → Remi finds and creates:
03-CRM/People/John-Smith.md
status: lead
importance_score: 7
relationship_type: ISO
source: Email
action_items:
- "Send deck by end of week"
- "Schedule intro call"
next_follow_up: 2026-03-28
last_contact: 2026-03-21
Two days later, they have a call → Morty creates:
02-Meetings/2026-03-23-John-Smith-Intro.md
attendees: [[Nader-Atrchin|Nader]], [[John-Smith]]
action_items:
- [ ] Nader: Send onboarding deck
- [ ] John: Review pricing model
The Person note auto-links back:
03-CRM/People/John-Smith.md
meetings: [[2026-03-23-John-Smith-Intro]]
last_contact: 2026-03-23 ← updated by Morty
action_items:
- "Send onboarding deck" ← carried forward
Base Views (open these in Obsidian)
| View | File | What it shows |
|---|---|---|
| People Pipeline | People-Pipeline.base | All contacts by status, importance, follow-up date |
| Action Items | Action-Items.base | Everyone with open tasks — sorted by urgency |
| Companies | Companies.base | All companies, grouped by type |
Asking Morty Questions
This actually works. Morty reads the vault before answering. Example questions:
“What are my highest priority relationships to action today?”
Morty searches People notes where importance_score ≥ 7, next_follow_up ≤ today, or action_items non-empty. Cross-references recent meetings in 02-Meetings/ and recent emails in 07-Emails/. Returns a ranked, context-aware list with specific action items.
“What did we discuss with [person] last time?”
Morty searches 03-CRM/People/[name].md → follows meetings: links → reads meeting transcript → summarizes.
“Who are the ISOs we haven’t talked to in 30+ days?”
Morty queries People notes where relationship_type == ISO and last_contact is more than 30 days ago.
“What’s the status of the EMS deal?”
Morty searches companies + people tagged EMS → pulls meeting notes + email threads → gives a full status summary.
Reliability: High — as long as agents write back to the vault after every interaction (which is now enforced as protocol). The more consistently agents update last_contact, action_items, and next_follow_up, the better the answers.
Email ↔ CRM Connection
07-Emails/Nader/Partner-ISO/_index.md lists all email threads.
Each thread’s From: and To: fields are wikilinked to their Person note. Click a sender → their Person note → see all meetings, action items, deals.
The daily sync cron (6AM PST) pulls new emails and updates last_contact on the relevant Person note automatically.
Task / Action Item Protocol
Action items live in TWO places simultaneously:
- Person note (
action_items:frontmatter) — “what do I owe this person?” - Meeting note (
## Action Itemssection) — “what was committed to in this meeting?”
The Action-Items.base view surfaces all open action items across all people in one place.
Deadlines live in Person note frontmatter:
deadlines:
- date: 2026-03-28
item: "Send NDA to John"
- date: 2026-04-01
item: "Follow up on pilot proposal"The Daily Flow
- Morning: Ask Morty “what relationships need attention today?” → pulls from Action-Items view
- During calls: Morty writes meeting note, auto-links attendees, captures action items
- After calls: Morty updates Person notes —
last_contact,action_items,next_follow_up - Evening: Nader digests updates in vault (graph view shows new connections)
- Remi: Continuously scans for new leads → creates Person notes → sets initial scores