20 Crons Vision

Can the vault serve as the source of truth for these automations? Tested against current state.

Relationship Intelligence

#	Cron	Schedule	Current Vault Readiness
1	Follow-up Radar — scan People notes where `next_follow_up` ≤ today + importance ≥ 7 → DM Nader with ranked list	Daily 8AM PST	✅ READY — all 114 people have `next_follow_up` + `importance_score`
2	Dormant Contacts Alert — flag anyone with `status: active` but `last_contact` > 30 days ago	Weekly Mon	✅ READY — fields exist, need population
3	New Meeting → Auto-update Person — on new Fireflies transcript, update `last_contact` + append meeting link for all attendees	On webhook	✅ READY — meeting notes have attendees, people have meeting history
4	ISO Pipeline Digest — weekly summary of all ISOs by status, importance_score, last_contact	Weekly Fri 4PM	✅ READY — People-Pipeline.base covers this
5	Investor Update Digest — monthly summary of all investor contacts + action items	Monthly	✅ READY — relationship_type = Investor works

#	Cron	Schedule	Current Vault Readiness
6	Processor Integration Status — weekly summary of EMS/Luqra/Priority integration progress (cross-ref meeting notes + GitHub tickets)	Weekly	✅ READY — EMS/Luqra/Priority notes + 04-Projects tickets exist
7	Marketplace Gap Analysis — monthly: which processor types are missing from vault? Score coverage vs. payment market	Monthly	🟡 PARTIAL — need more processor notes; EMS/Luqra/Priority/NMI added, gaps remain
8	Stale Deal Alert — flag Company notes where `status: active` but no meeting in 60 days	Weekly	🟡 PARTIAL — company notes have status, meetings indexed but auto-link not complete
9	New Partner Signal — when Remi adds a new ISO with importance ≥ 8, alert Nader with context	On write	✅ READY — Remi writes to vault, `importance_score` field exists

#	Cron	Schedule	Current Vault Readiness
10	Nader Daily Digest — top 5 emails from `07-Emails/Nader/` needing action, cross-referenced against open `action_items`	Daily 4PM PST	🟡 PARTIAL — email indexes exist, body summaries limited
11	Mike Email Digest — top emails from `07-Emails/Mike/Partner-ISO/` + `Financial/`	8AM + 2PM PST	🟡 PARTIAL — email indexes exist
12	Inbound Lead Detection — scan new emails for unknown senders in ISO/Investor categories → create Person stub in vault	Daily	🔴 NOT YET — needs email-to-person auto-creation pipeline
13	Thread Closer — when a deal/conversation seems resolved in emails, suggest updating Person note status	Weekly	🔴 NOT YET — needs semantic email analysis

#	Cron	Schedule	Current Vault Readiness
14	Open Ticket Summary — count tickets by status in `04-Projects/` → post weekly engineering health to Nader	Weekly Mon	✅ READY — 283 tickets indexed
15	Blocked Ticket Alert — any ticket with `status: blocked` in frontmatter → DM Nader	Daily	🟡 PARTIAL — tickets have status fields, need consistent tagging
16	Ticket-to-Meeting Linker — when a ticket number is mentioned in a meeting transcript, create a link in the ticket note	On webhook	🟡 PARTIAL — ticket notes exist, bidirectional linking needs automation

#	Cron	Schedule	Current Vault Readiness
17	Vault Health Check — count empty/sparse notes, flag any folder with >20% empty files	Weekly	✅ READY — script exists
18	Vault CI Monitor — check twill-brain GitHub Action status → alert rex-reliability on failure	Every 30 min	✅ RUNNING — cron `8c6c8987` active
19	Daily Vault Sync — pull new Fireflies + email refresh + git push	Daily 6AM PST	✅ RUNNING — cron `94860e49` active
20	Weekly Memory Distillation — Morty reads recent daily logs, updates `01-Memory/Morty-Memory.md` with key learnings	Weekly Sun	✅ READY — daily logs exist, MEMORY.md is the distillation target

Currently vault-ready (can run now): 1, 2, 3, 4, 5, 6, 9, 14, 17, 18, 19, 20 = 12 of 20

Needs more data/automation (2-4 weeks): 7, 8, 10, 11, 15, 16 = 6 of 20

Requires new pipeline work (4-8 weeks): 12, 13 = 2 of 20

The vault is already ~60% of the way to being a complete relationship operating system.

The biggest gap: email body content (we have subjects/snippets but not full analysis) and automated person-creation from inbound emails.