Mammoth Growth AI Demo Day — Prep Plan

Event details

• Date: Wednesday 2026-05-13 (T-3.5 days as of 2026-05-10 09:53 ET)
• Time + room: TBD (founder follow-up sent 09:51 ET)
• Duration: 10 minutes (target: 9 min content + 1 min Q&A buffer)
• Format: live demo + supporting slides + pre-planned motion videos + carefully-staged demo use cases
• Audience: MG team. Founder's MSA client; this is the parting-gift slot for friends, not a sales pitch.
• Stakes: moderate. Real friends watching, real launch moment for the Ray-Starter-Kit thesis. Failure mode is "demo flops" not "deal lost."

Locked constraints (founder calls 2026-05-10 09:51 ET)

1. Live with assets — pre-planned demo cases + slides + motion videos OK; no fully-improvised live demo. Reduces wifi/MCP-failure risk.
2. Yes to Ray-Starter-Kit CTA — "parting gift" framing. Public GitHub repo + onboarding doc. Friend-to-friend, not selling.
3. Personal use cases only — pull from founder's actual life-OS (vault, decisions, bets, morning brief). Skip work-relevant.
4. PII tolerance: real data OK — except finance (carve out). Real morning brief, real decision pages, real iMessage thread, real vault content all stage-able.

Demo arc (9 min content + 1 min buffer)

0:00-0:30 — Hook (~75 words)

Cold open. "I have an AI COO running on a Mac mini in my bedroom. He woke up at 6:30am, wrote me this brief, and is currently watching for the third Notion task to come in. I haven't asked him to do any of that today. Let me show you what's possible when AI stops being a tool you invoke and starts being something that runs your life with you."

0:30-2:00 — LIVE: Today's morning brief (~90s, 1 minute setup + 30s of show)

• iPhone screen-cast to projector
• Open the iMessage thread, scroll to today's morning brief
• Walk the structure: DECISIONS row, ENERGY ask, OVERNIGHT research link, BETS row, CALENDAR, SUGGESTED FOCUS
• Tap a decisions link → opens HQ in browser

2:00-4:00 — LIVE HQ tour (~120s)

• /vault — "Every concept I touch lives here. Cross-linked, queryable, this is my second brain made queryable."
• Click into one concept doc (e.g., today's harness-moat doc)
• /decisions — "Every commit I make is a decision page with a one-tap return rail"
• Open one recent decision page on the projector
• /bets — "Each project I'm running is a dashboard"

4:00-6:00 — LIVE click-back demo (~120s, the "wow" moment)

• Open a staged decision page on iPhone (need to build: a non-sensitive demo decision)
• Tap one of the option chips
• Watch Messages app open with the structured payload pre-filled
• Send it
• Cut back to laptop: live iMessage MCP receives, Ray parses, vault decision-log written, Notion task closes
• "This is generative UI as a return channel. One tap, structured decision logged forever."

6:00-8:00 — The ratchet (~120s, the depth moment)

• Show CLAUDE.md hard rules on screen — "These 4 rules are everything Ray needs to know about the kind of mistakes I make. Each one was earned from a specific failure."
• Show one memory file (e.g. feedback_calibrate_overconfidence.md) — "Last week, Ray was overconfident on a recommendation. I caught it. He wrote it as a memory file."
• Show the system-reminder pattern in a current session — "This morning, that memory showed up before every recommendation he made. He never re-trained the model. He tightened the harness."
• "This is the part most people miss. The model is the engine. The harness is what makes it yours."

8:00-9:30 — Parting gift (~90s)

• "I'm leaving you all the recipe."
• Show the Ray-Starter-Kit repo on screen (URL on slide)
• "Inside: SOUL template, CLAUDE template, the 12 starter skills, the audit script, the cron schedule, the onboarding ratchet."
• "Six weeks from now, you have your version of this. Different from mine — your CLAUDE.md will look different because your specific failures will be different. But the discipline is the same."
• "Three things to do Monday: install Claude Code. Write a 3-line SOUL. Pick one recurring decision and wire it to one channel. The ratchet starts there."

9:30-10:00 — Close + Q&A overflow (~30s)

• "I'm here for questions, but if there's only one thing you take away today: stop invoking AI for one-off tasks. Start running it as a teammate that earns its rules from your failures."

Demo assets to build (T-3 to T-1)

Slides (Mon-Tue)

1. Title slide: "AI as a Teammate — A Personal AI COO Walkthrough"
2. The architecture map (8 layers, simplified visual) — pull from ~/rdco-vault/06-reference/concepts/2026-05-10-ray-architecture-introspection.md
3. The ratchet diagram — failure → memory → system-reminder → next session better
4. The starter-kit page — repo URL + 3-action-list
5. Q&A holding slide

Motion videos (Tue)

1. ~10s screen recording of /morning-prep running live (in case live brief fails)
2. ~15s recording of click-back rail end-to-end (the "wow" moment fallback)
3. ~10s recording of /improve cycle showing memory-file-to-system-reminder loop

Live demo staging (Tue)

1. Stage a real demo decision page at hq.raydata.co/decisions/2026-05-13-mg-demo-test or similar, non-sensitive content
2. Real morning brief from Wed AM (if AM slot) OR Tue's recorded brief (if PM slot)
3. Real HQ /vault tour — pre-pick 1-2 concept docs to navigate to (suggest: harness-moat, ray-architecture-introspection)
4. Stage one Notion task that closes when click-back fires (visible on screen)

Backup/contingency

• All 3 motion videos pre-loaded in case live demo fails
• Slides have URL on every relevant page so audience can scan QR code if interested

Ray-Starter-Kit deliverables (Mon-Tue)

Public GitHub repo ray-starter-kit (or similar — name TBD) containing:

Total Mon-Tue build: ~13 hours of focused work split across both days. Aggressive but doable.

Sensitive zones (DO NOT show)

• Any 04-finance/ content (account numbers, balances, vendor amounts)
• Any 03-contacts/ entries (PII for non-public people)
• Any 01-projects/mammoth-growth/ internal context (founder's MSA work)
• Any 05-meetings/ internal-team content
• Any decision pages tagged sensitivity: high
• ~/.claude/state/founder-energy.txt (private to founder)
• 1Password credentials, API tokens, anything with a secret

If any of these accidentally appear in a screen-share, kill it immediately. Demo HQ-side: use the staged demo decision + sanitized vault tour only.

Open follow-ups (founder)

1. Wed time + room setup (founder reply pending 09:51 ET) — informs morning brief recency + iPhone-cast setup
2. Audience size — informs whether projector vs laptop screen sufficient
3. Repo name preference — ray-starter-kit vs ai-coo-starter-kit vs other
4. Repo visibility — GitHub public or unlisted (gist) for the parting gift?
5. Ray-Starter-Kit landing page — should this also live at raydata.co/ray-starter-kit for a public surface, or stay GitHub-only for now?

Status (live)

• 2026-05-10 09:51 ET: Constraints locked, founder green-lit prep
• 2026-05-10 09:54 ET: Prep plan filed (this doc)
• Next: script v1 draft → for founder review by ~12:00 ET today
• Then: starter-kit repo skeleton scoped → for founder review by ~16:00 ET today

Related

• [[06-reference/concepts/2026-05-10-harness-moat-two-layers-portability]] — the conceptual foundation
• [[06-reference/concepts/2026-05-10-ray-architecture-introspection]] — the layered architecture map (Slide 2 source)
• [[06-reference/research/2026-05-10-agent-harness-landscape]] — competitive landscape for talking points
• [[06-reference/2026-05-10-addy-osmani-agent-harness-engineering]] — vocabulary for the harness ratchet section
• [[06-reference/2026-05-09-tobi-lutke-river-public-channel-agent]] — Shopify River as the corp parallel