114 lines
4.9 KiB
Markdown
114 lines
4.9 KiB
Markdown
# Presentation Ideas Scratchpad
|
|
|
|
Raw ideas and scenarios for future AI presentations. Capture now, refine later.
|
|
|
|
---
|
|
|
|
## Presentation #1: MCP in Practice (OpenShift/GitOps)
|
|
|
|
**Audience:** Internal Axway team (small, reports to Conan)
|
|
**Tone:** Serious content, Simpsons humor, relatable frustration → payoff arc
|
|
|
|
### Core Thesis
|
|
The value of MCP isn't "AI can run kubectl" — it's **flipping the discovery loop**.
|
|
|
|
- **Without MCP:** Human works *for* the AI (copy-paste errors, run commands, provide context, be the middleware)
|
|
- **With MCP:** AI works *for and with* the human
|
|
|
|
### Narrative Arc
|
|
|
|
1. **What is MCP?** — Open standard, Anthropic 2024, gives tools to AI
|
|
2. **Why MCP? (Without)** — Grandpa Simpson walks in, sees GPT, walks out
|
|
- *Pitch:* Complex problems without tool-bearing AI = frustrating, time-consuming, upside-down. People "bounce off" AI for real work.
|
|
3. **Why MCP? (With)** — Setup for the payoff
|
|
4. **Tools for the demo** — openshift-mcp, gitea-mcp, argocd-mcp
|
|
5. **Prompt Engineering** — "Intent vs. Instruction" / "Ambiguity is the enemy of automation. If you don't define 'safe'… the AI will."
|
|
6. **DEMO** — Three scenarios, progressively impressive:
|
|
- **Scenario 1:** "Run a healthcheck of my cluster"
|
|
- AI examines multiple resources
|
|
- Key: produces **INSIGHT**, not just dry information
|
|
- **Scenario 2:** "Is my NAS slower than it should be?"
|
|
- AI launches ephemeral test pod (permitted via system prompt)
|
|
- Reasons against hardware expectations (2-bay 5400RPM, 1Gb network)
|
|
- **Scenario 3:** "Lock down security in this namespace"
|
|
- AI investigates current posture
|
|
- Plans path to privileged-v2
|
|
7. **Summary** — *(to be drafted)*
|
|
- Land the loop-flip insight
|
|
- "What you didn't see" — all the commands, errors, iterations handled silently
|
|
8. **Closer** — Homer spinning in chair (callback)
|
|
- "Taking us out of the discovery loop leaves us free to be productive elsewhere"
|
|
|
|
### Demo Technique
|
|
During demo: **actually do other work** while AI runs. Makes the "frees you up" point concrete — audience watches AI work, watches presenter work, realizes neither needed the other.
|
|
|
|
### Key Moments
|
|
- "Holy shit, it just figured it out" — if presenter had these moments building the demo, audience will too
|
|
- Transition from "tech demo" to "I want this"
|
|
|
|
---
|
|
|
|
## Presentation #2: Ideas (TBD)
|
|
|
|
**Context:** Axway heritage — Sopra Group → Sopra Steria. Enterprise software, API management, governance. Audience cares about security, compliance, "don't let the AI rm -rf."
|
|
|
|
### Option A: Security / AI Gateway
|
|
- Take the security line further than system prompts
|
|
- Show how an **AI Gateway** solves remaining concerns:
|
|
- Rate limiting
|
|
- Action allowlists
|
|
- Audit trails
|
|
- Policy enforcement
|
|
- Narrative: "Your enthusiastic AI colleague needs guardrails in enterprise"
|
|
|
|
### Option B: Hyper-Agentic First, Then Governance
|
|
- Go full agentic — show the power (browser control, cross-platform nodes, compound tool use)
|
|
- *Then* pivot: "And this is how you keep your enthusiastic colleague from doing something you didn't want"
|
|
- AI Gateway as the answer to the "wait, but what if..." concerns the demo just raised
|
|
|
|
### Potential Beats
|
|
- Show the Apple Notes/Reminders cross-platform demo (container → Mac node → AppleScript)
|
|
- Browser automation
|
|
- Multi-step reasoning with real consequences
|
|
- Then: governance layer, audit, policy, enterprise controls
|
|
|
|
---
|
|
|
|
## Loose Ideas (Capture as they come)
|
|
|
|
### Cross-Platform Automation Demo (Apple Notes/Reminders)
|
|
**Already documented above — usable for Presentation #2 "hyper-agentic" section**
|
|
|
|
- AI in secure container reaches out to Mac node
|
|
- Original tool (memo CLI) too interactive
|
|
- AI adapts: discovers AppleScript as native alternative
|
|
- Creates notes/reminders via osascript
|
|
- "Figures it out on its own" moment
|
|
|
|
### Meta-Demo: The Session Itself
|
|
The conversation that led to this scratchpad is itself demo-worthy:
|
|
- Casual experiment → discovery
|
|
- Presenter mentions "might use this for a demo"
|
|
- AI offers to capture it (not requested)
|
|
- Writes structured doc to the right repo
|
|
- That's working *with* someone, not commanding a tool
|
|
|
|
---
|
|
|
|
*Add ideas below as they emerge*
|
|
### The 3x Multiplier (Key Talking Point)
|
|
|
|
Common framing: "AI will replace all our jobs" — scary, paralyzing, defensive.
|
|
|
|
Better framing: **"The person leveraging AI will outcompete the person who isn't."**
|
|
|
|
**Example from practice:**
|
|
- Conan wanted to do a manual task (building muscle memory)
|
|
- Asked AI: "While I'm doing this, write an MD with X, Y, Z bullet points and anything else you see fit"
|
|
- Result: well-structured doc + *additional valuable points the AI added on its own*
|
|
|
|
**The math:**
|
|
- 2x = doing two things at once (parallel work)
|
|
- 3x = parallel work + AI's *additive* contribution (compounded output)
|
|
|
|
This is the multiplier people miss. You're not just parallelizing — you're getting value you didn't explicitly ask for. |