Demo: [Use case]
Start here. [One sentence: what a customer watches happen, and how long it takes.]
| Length | [e.g. 30 minutes (25 + 5 for questions)] |
| Audience | [The customer role. Be specific — "Linux and platform sysadmins", not "IT"] |
| Reader | The Ansible pre-sales engineer presenting it |
| Needs a live environment? | [No — every artifact is committed / Yes, and here is what to prove first] |
| Status | [Ready to present / Draft / Needs assets] |
The four documents
| File | Read it when |
|---|---|
run-sheet.md |
While presenting. Minute markers, what is on screen, exact commands, recovery moves |
talk-track.md |
While rehearsing. The narrative and the actual words, beat by beat |
architecture.md |
When asked "how does that work". The moving parts, the timing table |
objections.md |
Before you go in. What this audience asks, answered from the code |
Present from the run sheet. Rehearse from the talk track. The other two are reference.
The 60-second version
1. 2. 3.
What the demo is actually about is [the argument, not the mechanics. If the answer is "it's fast", find a better one — speed is the least durable claim you can make].
Why it works without a cluster
If you want to run it live
Related
../../plan/— why the automation is built this wayROADMAP.md— what is done and what is not