Outbound · bot to you. Telegram is the default — every notification, every brief, every confirmation goes through Telegram. SMS via Twilio is the fallback when Telegram is unreachable. Voice replies are wired through Cloudflare Workers AI: send a voice note, it transcribes via Whisper, processes the command, and replies in voice via MeloTTS. The portal at ops.hookstreetservices.com is the read-only briefing surface plus interactive Scope and the covered-call teaching tool — that's where rich content lives because Telegram can't render anything bigger than text.
Inbound · you to bot. Text Telegram routes through a Cloudflare Worker proxy (handles a 302 redirect issue with the Apps Script webhook), hits routeCommand_ in the bot's Apps Script, returns a response. SMS to the Twilio number takes the same path. Voice notes go to Whisper for transcription, then into the bot brain. And the portal's home page has tap-to-act buttons — Mark DONE, Defer one day, Add proof, Skip — which POST to the Worker's /inbox endpoint and write back through the same bot command pipeline.
| Sheet | What the bot does there | Status |
|---|---|---|
| Personal Command Inbox | The bot's home sheet. INBOX capture · Action_Queue · Memory · Brain_Feed · Context tab (24 facts) · Transcript · Pulse_Log · Outbox · Mildred_Start. | Read + write, primary |
| MIS v2 | fn=peekoverlay for Scope · fn=performance for the dashboard P&L · fn=snapshot nightly · all the dashboard rendering · commands SETCOST, SETMARGIN, IDEA, THESIS, Q, NOTIFY route through the MIS bridge. | Read + write via HTTP bridge |
| Monthly Obligations v1 (BOS canonical) | Read-only — partial access. Used by the morning brief once that's wired (Stage 14 prep). | Read-only, partial |
| LevSMS sheet | Independent brain with its own router. Sees inbound SMS, handles approvals, owns the schedule database. | Not connected to the command-inbox bot |
| Everything else (CM Invoice · Eden Gardens OS · Mom's Wholesale OS · Mildred's 5 sheets · BOS-v2 stale snapshot · Calculator) | Nothing. | Intentional disconnect |
| Sheet | Connect? | Reasoning |
|---|---|---|
| Eden Gardens OS | Eventually, yes | Live $65K client. Weekly real-money decisions. Wait until the ontology layer ships so it slots in cleanly instead of becoming another loose schema. |
| CM Invoice System | No | Mom's autonomous tool. You don't make decisions in it day-to-day. |
| Mildred's 5 sheets | No | She owns them. Connecting them = her work flows into your queue = friction, not value. |
| Mom's Wholesale OS | Eventually if it stabilizes | Same logic as Eden but lower urgency. Wait for the operating model to harden first. |
| HookStreet-Business-OS | Partial via Obligations v1 (already done) | Don't add more entry points to the same system. Deepen the existing one instead. |
| Calculator (STR underwriting) | No | Tool you use occasionally, not a decision-feed. |
1. Eden Gardens OS read access. When you text the bot "EDEN", it can tell you what's open without you opening the sheet. Tax bill status. Asher's response state. Outstanding invoices. This is value because Eden is the highest-dollar active client AND a paper-only sheet today.
2. Monthly Obligations v1 deeper read. So the morning brief can tell you "$2,179 autopay fires tomorrow, Chase 7792 has $X balance, you're clear for the month" without you checking. Right now the brief skips this because the read is partial.
Neither is urgent enough to do before Sunday. Both go in the queue I described in the 200-ticker prep doc — they're behind dashboard caching, the Scope refactor (pending your mockup pick), and the Schwab Positions CSV import.