crmlisted

# Network CRM (Obsidian-native) Alex's CRM lives entirely in Obsidian. Each People/ note has YAML frontmatter with CRM fields. The Exobrain reads frontmatter to compute overdue status, surface follow-ups, and manage the network. **Dashboard**: `/Users/alexhedtke/Exobrain/Network CRM.base` **People notes**: `/Users/alexhedtke/Exobrain/Areas/Relationships & Community/People/[Name].md` ## Category Frequencies | Category | Frequency (days) | |----------|-------------------| | A | 14 (every 2 weeks) | | B | 21 (every 3 weeks) | | C | 45 (every 6 weeks) | | D | 90 (every 3 months) | | potential | no frequency -- tracked for future outreach | ## Frontmatter Schema Frontmatter holds only CRM-operational fields. Contact details live in the `## Contact` section (see below). ```yaml --- category: A # A / B / C / D / potential / null frequency: 14 # days (defaults from category, but user can override) last_contact: 2026-03-30 platform: Signal # preferred outreach method (optional) expertise: AI safety # optional how_we_met: BlueDot # optional why_interesting: ... # potential contacts only reached_out: false # potential contacts only --- ``` **Alex edits frontmatter directly in Obsidian.** The Exobrain must always read the current frontmatter before computing status -- never cache or assume values. If Alex changed a category or frequency manually, honor it. ## Contact Card Every People note MUST have a `## Contact` section immediately after the fron