Pranafy · Slack huddle + remote

Jonny x Grok Bot

Pranafy floor · CoS in the cockpit · Assistant + Ops on Slack

Tonight: you talk. Work lands. Closed loop once.

Thu Sep 17, 2026 (PT) · with Carson

Presenter

Keys (draw + navigate)

Key	Action
`←` `→` / arrows	Prev / next slide
`Esc` or `O`	Overview
`F`	Fullscreen
`B`	Toggle chalkboard
`C`	Toggle notes canvas (draw on slide)
`X` / `Y`	Cycle pen colors
`Del`	Clear current board / canvas
`Backspace`	Delete all chalkboard drawings
`?` or help below	Pen buttons also bottom-left

Touch / mouse: pen icons bottom-left. Right-drag wipes.

Product split

Grok vs Grok Bot

	Grok (app)	Grok Bot
Job	Conversational LLM	Operators / small team
Feel	Chat, voice Q&A, images	Named Bots, computer, connectors, routines
URL	x.ai/grok	x.ai/bot
When	“Explain this” / quick ask	“Do this work in my real tools”

Use Grok for a conversational LLM. Use Grok Bot for operators: named roles with a computer, connectors, routines, roster like a small team. (product-design paraphrase, not a livestream quote)

Official anchors

Bots, not conversations

“The main objects in Grok Bot are Bots, not conversations.” Designing Grok Bot

“Grok Bot is an agent with a computer.” Grok Bot 101 (Matt Palmer)

“A chief of staff sits on top, with a specialist for each lane…” Introducing Grok Bot

Bots keep going if you close the laptop. Work lands in Slack List, Calendar, Gmail draft.

Say this once

Seat map

Seat	Where	Owns
CoS	Cockpit only	Route, prioritize, call specialists, pull you for judgment
Assistant	Slack floor	Cal + Gmail triage, drafts, meeting prep
Ops	Slack floor	Tasks, Lists/Canvas, Social Pulse, status
Personal	Grok personal lane	Personal inbox/cal only
Dr Eggbot	Meta (optional)	Create/tune other Bots when asked

Grok app = conversational LLM. Not the operator roster.

Hard rule

Why CoS stays OUT of Slack

On Slack Pranafy Assistant
Pranafy Ops

Cockpit (not Slack faces) CoS
Personal Assistant
Dr Eggbot

CoS is your router and judgment partner. If it also posts in Slack, you get noise, double faces, and you become the middleman again.

Narrow Slack triggers. Never “every message.” Approval before outbound posts.

Closed loop

How work flows

Talk to CoS (type or voice)
CoS routes to Assistant / Ops
Specialists do the work in real tools
Evidence comes back (List, Canvas, link)
You approve anything external

Also fine: @assistant / @ops in Slack when the floor should be visible.

Starts (101): chat · routine/trigger · another Bot

Demos · Ops

Ops: open tasks + Social Pulse

A · Open-task scan (prefer CoS)

Route to Ops. Scan Pranafy Slack for open tasks on me + agent debris. Prefer Slack List. Canvas if List fails. Evidence only. Do not invent tasks.

B · Social Pulse x4

Route to Ops. Draft Social Pulse digests: nervous system regulation; men's work; breathwork; relationships/fatherhood. Draft only. Do not publish.

Slack variants: @ops … (same asks, floor-visible)

Demos · Assistant + Personal

Week-ahead + lane split

C · Assistant week-ahead

Route to Assistant. Week-ahead: calendar + Gmail decisions-only. Draft replies. Do not send. Protect practice blocks.

D · Personal Assistant (Grok, not Slack)

Show personal vs Pranafy this week. Keep lanes separate. Hand Pranafy-shaped items to CoS as one-liners. Do not post in Pranafy Slack.

The win

Closed loop

Voice-dump to CoS
CoS routes checklist to Ops
Ops posts evidence (List / Canvas / links)
Point at it: talk → route → work → evidence

Capture this voice dump as tasks. Route actionable Pranafy items to Ops as a checklist. Bring evidence for each. Do not mark done without evidence. Pull me only for judgment or external send.

Trust ladder

Once → skill → routine

Do it once until the result is good
Save the method as a skill
Only then make a routine (schedule or Slack trigger)

“Start with a one-time task. Make it reliable, save the method as a skill, and only then automate it.” Docs: Skills and routines

Automate prep first. Keep send / publish / delete / pay behind your OK.

Avoid

Anti-patterns

Avoid	Do this instead
Fresh ChatGPT-style chat every time	Return to a named Bot
One “do everything” Bot	CoS + specialists
You as router between tools	CoS orchestrates; you judge
Automate before it worked once	Once → skill → routine
“Every Slack message” listeners	Narrow match + approval
CoS as a Slack face	Assistant + Ops on the floor
Invented proof / fake “done”	Evidence links / List rows

Jonny

Your role

VP Content / Vitality Guide / Maui

Bots protect practice time (calendar hygiene, ops checklists, scheduling drafts, Social Pulse prep). They do not replace on-camera work, guide presence, or ceremony craft.

If a Bot eats creative time: tell CoS “Protect practice. Cut noise.”

Soft close

One habit

Morning voice dump to CoS. Let it route. Approve the risky edge.

Draft-only until you say send
CoS out of Slack
List first, Canvas fallback
No invented metrics or testimonials

You talk. Work lands.

If anything wobbles

Fail-safes

Draft-only for email, client-facing Slack, calendar notifies
Do not bloat Slack with CoS
If List fails → Canvas. Do not stall
Do not invent proof
Shared computer: no secrets another Bot should not see

Already set: Google / Gmail / Calendar · Assistant + Ops on Slack · Hookdeck narrow triggers · Personal + Dr Eggbot