# Paris AI Forum: Hyper-Agentic Demo Ideas

**Goal:** Demonstrate the difference between "Chatting with AI" (Hope) and "Agentic Workflows" (SOP/Action).
**Constraints:** Must be impossible/hard for a standard web LLM. Must show tools, file manipulation, or system state changes.

---

## 1. The "Instant Briefing" (Research Loop)
**Concept:** Turn a vague question into a tangible artifact in < 2 minutes.
**The Prompt:** "I have a meeting with the CTO about [Emerging Tech Topic] in 5 minutes. Build me a briefing pack."
**The Agent Run:**
1.  **Search:** Scours the web for the latest 3-5 credible sources (filtering spam).
2.  **Synthesize:** Writes a structured `EXECUTIVE_BRIEF.md` (Key Trends, Risks, Opportunities).
3.  **Generate:** Uses `presenterm` (or `pandoc`) to auto-generate a PDF/Slide deck from that markdown.
4.  **Deliver:** Pushes the PDF to a shared repo or Slack channel live.
**The "Wow":** Moving from "text output" to "file delivery" without human copy-pasting.

## 2. The "Infrastructure Surgeon" (Self-Healing)
**Concept:** AI that can touch the metal.
**The Setup:** A broken service on a demo OpenShift namespace (e.g., a pod crash loop or wrong env var).
**The Prompt:** "The `demo-app` is down. Fix it."
**The Agent Run:**
1.  **Diagnose:** Runs `kubectl get pods`, `kubectl logs`, `curl localhost`. Identifies the error (e.g., "Port 8080 refused").
2.  **Reason:** "Config map points to 8081, app listens on 8080."
3.  **Act:** Runs `kubectl patch` or edits the deployment manifest.
4.  **Verify:** Runs `curl` again to confirm 200 OK.
**The "Wow":** Breaking the "Read-Only" barrier. The AI *changed state* to solve a problem.

## 3. The "Meeting Artifact Generator" (System Integration)
**Concept:** Turning unstructured voice/text into structured systems of record.
**The Setup:** A raw transcript or audio file of a chaotic meeting.
**The Prompt:** "Process this meeting dump. Update our systems."
**The Agent Run:**
1.  **Parse:** Extracts Action Items, Decisions, and Deadlines.
2.  **Ticket:** Creates actual Issues in Gitea (or Mock Jira) for each action item.
3.  **Schedule:** Generates an `.ics` calendar invite for the follow-up.
4.  **Notify:** Sends a summary message to a Telegram/Slack group tagging the owners.
**The "Wow":** The AI interacting with *multiple* disparate APIs (Git, Calendar, Chat) to orchestrate a workflow, not just summarize text.