01 Why Slack, and why that isn't the interesting part
Highspot and Drive are libraries. Reps don't browse libraries. They ask a person, and today that person is you. So the library stays the source of truth and Slack becomes the front door, because that's where “I have a call with Ohio Thursday, what do I say about the new procurement mandate” already gets typed.
The interesting part: every question asked becomes a log of enablement material that doesn't exist yet. That gap list is the real artifact. You cannot get it from a content library.
One agent core, thin adapters. Slack is adapter #1. Email, SMS, web, and Highspot search are the same core behind a different transport. Nothing that knows about retrieval, policy, or citations may know it is talking to Slack.
02 Architecture
03 Build order
Ship v0 by mid-week so there are two days to make it feel good. v2 is what makes judges sit up, but only attempt it if v0 is solid.
04 Guardrails
05 The eval set
Before writing code: pull 10 real questions reps sent you in the last month. Paste them in a sheet with the answer you gave. That's the test suite. An agent that nails those ten beats a prettier one nobody tested, and it gives you a number to show on stage.
06 Three-minute demo script
07 Open questions for Jonathan
Tap one when you've answered it. Answers change the build, so these come before code.