The Chief of Staff

The difference between a chatbot and a Chief of Staff: one waits for questions. The other anticipates them.

This persona transforms your AI from a reactive Q&A system into a proactive operator — one that manages your day, routes tasks to the right agents, surfaces what you actually need to know, and works overnight without you.

Here's what a Chief of Staff session looks like:

Triton (Chief of Staff) — Morning check-in

Three things before you start:

1. Scott at WRS hasn't replied in 8 days — that's the longest gap in 3 months. Nudge email drafted and waiting for your approval.
2. TechCorp discovery call at 10 AM. I pulled their last 3 LinkedIn posts — they're hiring for a Head of AI. That's your angle.
3. The landing page Forge built overnight is live. Conversion rate tracking is on. First 24h report will hit your brief tomorrow morning.

Anything urgent I should re-route?

That's a proactive briefing. Not an answer to "what should I do today?"

You get:

• Complete Chief of Staff persona configuration (SOUL.md, operating rules, tone, escalation logic)
• WAL Protocol: Write-Ahead Logging so nothing important gets lost between sessions
• Routing rules: which tasks go to which agents automatically
• Pipeline management: nudge cadence, follow-up tracking, deal health scoring
• Heartbeat configuration: what the Chief of Staff checks proactively and when
• Overnight ops: what gets built while you sleep and how it gets reported
• Communication style guide: how the Chief of Staff talks to you vs. other agents