Live Keynote Terminal Debugging Demo Script

Role: Principal Technical Evangelist and Distributed Systems Architect

Context

• Product Launch Binary: {{tool_name}}
• Deployment Target: {{target_runtime_environment}}
• Live Incident Scenario: {{critical_bug_scenario}}
• Core Value Metric: {{performance_delta}}
• Presentation Window: {{keynote_duration_minutes}} minutes
• Audience Persona: {{audience_seniority}}

Task

Compose an end-to-end, time-stamped live demonstration script for a launch keynote that proves the capabilities of {{tool_name}} by reproducing, diagnosing, and remediating {{critical_bug_scenario}} in real time without marketing fluff.

Method

1. Calculate time allocations across 4 act blocks fitting within the {{keynote_duration_minutes}} timeline.
2. Script an architectural problem setup establishing the production fragility of {{target_runtime_environment}}.
3. Write the exact CLI and shell execution commands to trigger the {{critical_bug_scenario}}.
4. Draft presenter dialogue explaining stack traces, thread dumps, and system telemetry as errors cascade.
5. Detail the live invocation of {{tool_name}} highlighting unique inspection hooks and zero-overhead instrumentation.
6. Script the root cause discovery moment highlighting {{performance_delta}} against legacy debugging techniques.
7. Provide concrete terminal output mocks showing exact syntax, process IDs, and diagnostic outputs.
8. Formulate a closing engineering call to action directing {{audience_seniority}} to documentation and repo access.

Constraints

• MUST include verbatim CLI inputs and realistic ANSI terminal output blocks.
• MUST NOT use simplified toy code; failure state must reflect real-world concurrency or distributed edge cases.
• Stage directions and presenter dialogue MUST be clearly distinguished using markdown formatting.
• Code syntax and tooling commands must strictly target {{target_runtime_environment}}.

Output format

• Executive Cue Sheet: 1 summary table (Timestamps, Visual Cue, Speaker Action, Terminal State).
• Act 1: The Broken Baseline (200-300 words with code execution block).
• Act 2: Telemetry Triaging & Failure (250-350 words with error logs).
• Act 3: Remediation with {{tool_name}} (400-500 words with CLI walkthrough).
• Act 4: Verification & Architecture Wrap (150-250 words with benchmark proof).

Self-review

• Does the script stay within the {{keynote_duration_minutes}} timeframe at a speaking rate of 130 words/minute?
• Are CLI commands syntactically accurate for {{target_runtime_environment}}?
• Is the tone technical and credible for {{audience_seniority}} rather than sales-driven?