3.3 KiB
Real demonstration script — review draft
Target duration: 90 seconds, plus the existing animated introduction if desired. This document is a shot plan; it is not a claim that the recording has already been made.
Readiness
Use the existing isolated Debian test VMs. Verify their current boot and node identities, normal user session, exact intended package and its verified identity, runtime readiness, owner-approved manual ChatGPT connection and selected node. Keep the foreground tunnel terminal out of the task workspace. A community-candidate demonstration requires that candidate's own checked installer and release evidence; historical RC7 acceptance is not a substitute. No new community recording or VM acceptance is claimed by this shot plan.
A host reboot can leave the VMs stopped and requires a new manual tunnel connection. Restore the documented VM lifecycle first. Do not reset login credentials, approve a different account, or record secret-entry screens.
Use a new nonce in every demo path. The data must be synthetic and the chosen paths must not already exist.
0–15 seconds: the instruction starts in ChatGPT
Show the selected test node label. In ChatGPT, request: "On the selected test node, create a new demo directory under my home with a unique suffix. Write a short installation checklist in notes.txt. Report its path, byte count and SHA-256. Use only new demo files."
Show the actual tool call and backend result. Record the original timing; label any editing or speed changes in the finished video.
15–35 seconds: the instruction becomes visible in the console
Show the official FrameBridge console with FBTERM activity and its Bash pane. Display the newly created file and its checksum from that same selected node. Keep the complete native frame available and preserve the connection between the request, job identity, file and visible result.
Do not render a transcript as if it were a screen capture.
35–55 seconds: independent work
Use a second ChatGPT conversation for a separate task in another new directory: create and summarize a tiny synthetic CSV. Keep the first conversation's checklist task independent.
If both conversations are genuinely active at the same time, record that overlap. If execution is queued, show the queue honestly. Do not imply certified isolation or fake simultaneous actions with an edited split-screen.
55–80 seconds: another request, a graphical result
From ChatGPT, request a graphical action in the same test environment. A single conversation controls the shared desktop. Show a full authentic screen image, the action and its actual result.
Open or attach the same persistent terminal session from the graphical desktop and display the checklist created at the beginning. Verify that the session/profile is the same rather than presenting a newly created terminal as continuity.
80–90 seconds: evidence
Show the installer filename, verified SHA-256, supported Debian version and a brief invitation to review the project. Keep installation details and account entry in the separate tutorial.
The current music draft can accompany the edited presentation after its ownership and use are checked separately from the blog-text license. Record application and console evidence separately, then combine them with the clearly labeled animation.