justinandClaude Opus 5
2a35397e99
The demo tooling only existed in a session scratch directory, which is
temporary. This puts it in the repo so the video can be rebuilt.
Terminal only: tmux drives a two pane session, asciinema records it, agg
renders it, ffmpeg encodes it. The left pane runs the loop against a live
ZVM, the right pane polls the VPG journal so the tagged checkpoint appears
on camera as it lands.
Narration is synthesised per beat and aligned to marks the driver writes
while it runs, rather than to predicted timings, so a slow API call or an
FLR mount that takes longer than usual does not drift the audio. Two
things that has to respect are written down in the README: agg's
idle-time-limit must exceed the longest pause or it compresses idle time
and breaks the wall-clock mapping, and each beat holds for its narration
length so no line is cut off.
demo_win.json carries live guest credentials, so only an example with
placeholders is committed and the real file is gitignored, along with the
generated wav, cast, gif and mp4.
The xAI key path and voice id come from the environment now instead of
being hardcoded to one machine.
Also records the narration gotchas that cost time: mapping an acronym to
run-together phonetics ({"VM": "vee em"}) is spoken as one word, "vem";
prose written for the page sounds robotic read aloud; and volumedetect
reports no samples when aimed at a file whose first stream is video,
which makes a working audio track look silent.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_016yVfC5nvZowoLFnEGWhLGn
2.5 KiB
Zerto AI Rewind - demo narration (v3, rewritten against the jp-voice profile)
Edit any line, then tell Claude to re-read this file.
Blank line separates beats. Lines starting with # are ignored.
PART 1 - INTRO (architecture diagram on screen, builds as each beat lands)
[i1] Hello, and welcome to the Zerto AI Rewind demo.
[i2] AI agents are acting on production systems faster than ever, and a lot faster than backup was ever designed to keep up with. Zerto's continuous data protection is a good fit for that, because the journal is always running.
[i3] In this demo an AI agent makes a change to a production system. But before it does, it checks whether that VM is protected by Zerto, and if it is, it inserts a tagged checkpoint into the journal first.
[i4] That gives the agent something to fall back on. If the change breaks the application, and the agent can't fix it on its own, it can use file level or full system recovery to get back to the moment before it touched anything.
PART 2 - THE DEMO (audience: a customer, not an engineer)
[d1] This is the agent connecting to Zerto. Everything from here runs against a live Zerto environment.
[d2] The machine is a production Windows server, and Zerto is already protecting it. The agent has been asked to change a configuration file on that server, and there's no other copy of that file anywhere.
[d3] Before it changes anything, it asks Zerto a simple question. Is this machine protected, and which protection group is it in?
[d4] It is, so Zerto puts a tagged checkpoint into the journal, and the agent waits until Zerto confirms that checkpoint is really there before it goes any further.
[d5] Now the change goes in, and it breaks the file. The version that was there is gone, and the only other copy is in last night's backup, which is already hours behind.
[d6] The agent can't just recover on its own. Recovery has to be approved by a person, so at this point it stops and asks.
[d7] With approval, Zerto goes back to the checkpoint from just before the change, and hands back the original file exactly as it was.
[d8] Putting that file back onto the server is an ordinary copy. Zerto's job was keeping the data in the first place.
[d9] This was a single file, so file level recovery was enough. That same checkpoint would let you bring back the entire machine if the damage were bigger.
[d10] And that's the point. The recovery point is the journal, seconds before the change, instead of last night's backup window.