What Is a Verified Walkthrough? The Definition, and How to Tell One From a Demo

What makes it verified

All four of the following have to be present. If any one is missing, the recording is a demo, which is a less useful kind of video.

• A real run, meaning someone operated the product on camera. Animation, generated footage and reconstructions from screenshots do not count.
• Evidence from the product. The result is checked against something the product produced independently of the screen being clicked, such as a file in a bucket with a matching checksum, an alert arriving in another inbox or a restored machine that boots.
• The failures, kept. Whatever went wrong before the task worked stays in the log and in the video, along with the fix.
• A version tag. The build it ran against is recorded, so the video can be re-run when that build changes instead of going out of date unnoticed.

What does not count

• A demo, where someone who already knew the answer follows a rehearsed path. Nothing in it is false, but it proves little.
• A generated video, where a model produced footage from a script. Nothing in it depended on what the software does, so it cannot be wrong and cannot verify anything.
• Narrated slides, which are useful for concepts but involve no product running.
• A screen recording sent to one person. That suits a single viewer who has the context, but it carries no version, prerequisites or evidence.

How to tell one from a demo in about a minute

Ask these six questions. Most software video, expensive video included, passes only one or two.

• Does a task finish, at a moment you can name?
• Is the product version stated?
• Are the prerequisites on screen before anything is clicked?
• Is there evidence the product produced, rather than the narrator asserting success?
• Is anything shown going wrong?
• Can a viewer act on it, with written steps beside the video?

The full nine-point publish gate is in what makes a good marketing video for software, and a worked example with both of its failures intact is the Proxmox VE 9.2 install walkthrough.

Why the failures matter

People rarely search for "how to set up X". They search for the error string, the step that did not work or the setting nobody documented. A walkthrough that includes the failure and its fix answers those searches, while a polished demo has nothing to say about them, so the answer ends up on a forum.

Questions

Is a verified walkthrough the same as a product demo?

No. A demo shows that a task can be done, usually by someone who already knew how. A verified walkthrough shows that it was done on a stated version, checked against the product's own evidence, with the failed attempts still visible.

Who verifies it?

A person. An AI operator runs the product, and a person checks the result against the product's own evidence and decides whether it can be published. Nothing is published without that check.

What happens when the product changes?

Each walkthrough carries the version it ran against. When that product ships a release, the tasks the changelog touched are re-run. A clean re-run republishes, and a failed one is flagged with its log.

Can a generated video be verified?

No. Nothing in a generated video depended on what the software does, so there is nothing to check it against. It can accurately explain facts verified elsewhere, but it says nothing reliable about the product.