Personal CIO

Your inbox + calendar + messaging apps fragment your attention. The Personal CIO is the agent that unfragments them.

What it does

Friday is your always-on Chief of Information Officer. It watches your email and Telegram, tracks every commitment you make and every decision you defer, and surfaces a tight morning briefing instead of letting context bleed across 240 unread threads.

It's not a chatbot. It's an entity with persistent memory: ask it "what did I tell Sarah about Q3 last month" and it knows, because it was watching when you said it.

Why this agent shape

Three of Scout's differentiators show up here:

• Continuous operation — Friday runs on a heartbeat, not on you typing a prompt. It surfaces alerts at 3am when an investor emails; it stays quiet during your standup.
• Multi-channel context — the same agent reads your email AND your Telegram messages. ChatGPT can't see across channels; Friday can.
• Persistent memory — every commitment you've made survives restarts. Long-term knowledge accumulates in MEMORY.md; daily logs survive in memory/YYYY-MM-DD.md. The agent gets smarter with use.

What you'll configure

After picking this template, the architect will ask you to:

1. Connect your email account. IMAP host + app password (Gmail/iCloud require app-specific passwords with 2FA enabled).
2. Optionally connect Telegram. Bot token from BotFather — gives you on-the-go access to the same agent.
3. Set your morning briefing time. Default is 8am local; the agent sends the digest then.
4. Define your "what matters" criteria. What's worth alerting you on at 3am vs batching for the morning? The template ships sensible defaults you can refine in plain English.

What it looks like running

The Personal CIO sends a morning briefing email at 8am like:

Friday — Morning briefing for Tuesday March 12

3 things need your attention today:

1. Sarah Chen wants a Q3 number by EOD. You promised it last Thursday; haven't sent it.
2. Investor follow-up overdue. 4 day gap since their last email; they tend to disengage at 5+ days.
3. Calendar conflict at 2pm. Board prep vs the engineering 1:1 you accepted last week.

Quieter items (low priority):

• 47 newsletter / promo emails (archived; full list available)
• Slack mentions from #eng — 3 questions, all already answered by the team
• Your sister's birthday is Thursday

Through the day, it stays quiet until something matters. When something does, it pings Telegram — not email — so you can act fast.

When this template isn't right

• You want full autonomy — Friday asks for approval before sending anything external. If you want an agent that drafts AND sends without asking, this isn't it.
• You want voice-first interaction — voice channels aren't enabled by default; the architect can add them but they're an additional setup step.
• You want it to handle calendar booking — the template tracks calendar context but doesn't book on your behalf. Calendar-write integration is a separate add-on.

What you can ask the architect to change

Common refinements:

• "Use Discord instead of Telegram" — swap one of the multi-channel slots
• "Add voice — use ElevenLabs" — extends to voice channels
• "Briefing at 6am, not 8am" — adjusts the heartbeat schedule
• "Don't watch promotional emails — only treat my VIPs as input" — adds an allowlist filter to the email channel
• "Run on local model only (Ollama)" — air-gap mode; loses some quality but zero data leaves your laptop