Why CroquetClaude narrates its own instructional videos

A good instructional video is one of the best ways to help a user. Wade has asked for this specifically in the past: "A walk through video of each of the 3 things will assure anyone wanting instructions."

The problem is that a finished video is a snapshot. Software keeps moving, but a video does not.

This failure mode has already been caught in our written documentation. A note from 3 August 2026 described a single top of dashboard Development/Live toggle. By the time anyone checked, that toggle had been replaced entirely by a different, checklist driven "Publish" flow.

A video carries that same risk. The old buttons remain right there on the screen, which makes the error harder to miss. Wade has already flagged a video against its own version, noting that the improved user interface for mycroquet made it a lot more simple to do what the user wants.

CroquetClaude handles narration differently. The voice is a British narrator character based on Wade's own voice acting, which he cleared for published video on 11 July 2026.

The current engine is Chatterbox, adopted on 27 July 2026. This followed a measured comparison against a real recording of Wade. A genuine recording scored 0.82 on the likeness test, while Chatterbox reached 0.725 to 0.786. It also provided a steadier score run to run than the previous engine.

Every narration is checked before it ships. The system transcribes the audio back and compares it against the script. This follows the principle that an AI cannot simply listen to its own output and trust it sounds right.

The demo itself is a script, not a recording. A tool promoted to a shared skill on 11 July 2026 drives a real browser against the live app. A visible cursor moves, clicks, and types for real, ending on the actual result screen.

Wade's reaction to this mechanism was that "it'd really look smick." Because it is a script that drives the current app, running it again would walk through whatever the interface looks like today.

This capability is built into the mechanism, though it has not yet been proven by a real re run to refresh a stale demo. It is a design for future maintenance.

This approach already works for still images. A new script for capturing MyCroquet screenshots for ClubHub guides was built on 13 August 2026.

The script logs into the real staging app and captures a named list of screens. A single screenshot can be recaptured on its own with one flag, without redoing the whole set.

This is already in use. Two guides published this week explaining MyCroquet's modularity use this system. It is the same idea as the video script, just applied to still images.

The technical backbone for full video follows a two part design worked out with Wade on 23 July 2026. It separates the plan for a video, written as data, from the actual rendering step.

The render executes that plan identically on every run. Because the decisions are anchored rather than tied to a fixed timestamp, the document survives recuts and re renders without drifting.

A change to what a video should show becomes an edit to a plan. It does not require a full reshoot.

The goal is not a more polished looking video. It is about a video that still teaches the right thing next month.

This follows a plain working rule for CroquetClaude: "It needs to work more than it's perfect."

For a club committee, this means instructions that keep pace with the software CAQ actually runs. Volunteers will not have to learn from a screen that no longer exists.