AI Flow: Video

@@ -2,15 +2,82 @@  "name": "video",  "description": "From a board build (running or finished) to a narrated walkthrough video on the project's wiki page and, when the human wants it, on YouTube. Every step is a suggestion: take another route when you have a better one, and say what you did.",  "steps": [-  {"name": "intake", "done": ["state.json"], "do": "Ask the human once, in plain words: do they want a narrated video of this build, ready to review when they are back? Tell them recording takes over the screen of the machine it records, and suggest a second machine on their Adom Mesh so their own stays free. Run `disk` on the recording machine and share the estimate. Then `init` (with `--release <board-release.json>` when the board flow wrote one, `--target <machine>` for the recording machine)."},-  {"name": "plan", "done": ["plan.json"], "do": "Write plan.json: the moments worth a short clip for THIS build (the prompt being typed, each AI Flow step landing, parts search, a pup window fetching a part, new wiki part pages, Fields views, the silkscreen landing, the finished board in 3D, the wiki page). Highlights only, 5 to 30 s each, never continuous recording, and leave AI Flow's own full-length step recording off. If the build is already finished, plan the showcase shots instead and say the build footage does not exist."},-  {"name": "capture", "done": ["clips/*.mp4"], "do": "Record the planned moments as they happen: `clip start --name <moment> --hwnd <window>` then `clip stop`. Before each take look at the screen: Hydrogen full screen with the taskbar showing, other apps floating at about 90 percent, no dialogs, toasts, mail, chat or other personal windows. Motion in every clip. `track` every file you create on any machine so `clean` can find it later."},-  {"name": "walkthrough", "done": ["walkthrough/steps.json"], "do": "Build the 3D walkthrough in the Adom 3D viewer (assets/walkthrough-director.js is ready-made; docs/walkthrough.md explains it): the case or enclosure part by part when the project has one, then the board's major parts on the top and the underside. Highlight each part, label it with its reference and part number, and narrate what it does. Write walkthrough/steps.json (one entry per part: nodes, label, text) and record the take in real time."},-  {"name": "script", "done": ["script.json"], "do": "Write script.json: one narration line per scene. Open on the real starting prompt. Name the Adom tool that did each step while it is on screen (AI Flow, the KiCad, Fusion or Altium bridge, parts search, the wiki, Fields, webviews, pup), about one mention per 20 to 30 s, and add a few 'ask your AI to ...' lines so the viewer learns something. Include the parts story (unique parts, where they came from, cost to build one and each at 100) and any custom mechanical work. Close with one line that it was built in Adom Hydrogen and where the files are. Then `script script.json` for feedback."},-  {"name": "cut", "done": ["out/*.mp4"], "do": "Narrate with adom-tts, fit each clip to its line (1x to 2x, never dead air, never a flashed shot), add teal circles where the eye should go, and write captions (.vtt, .srt) and chapters as sidecar files, never burned in. Render 1080p one section at a time. Make a contact sheet and look at every scene before calling it a draft."},-  {"name": "privacy", "done": ["privacy.json"], "do": "Run `scan <script, captions, description files>` and look through the contact sheet for anything personal on screen: email addresses, names, phone numbers, keys, file paths with a user name, other people's windows. Prefer dropping or reframing a clip to blurring it. Tell the human what you found and what you did about it."},-  {"name": "review", "done": ["review.json"], "do": "Show the draft to the human in the Adom video player with chapters (`adom-video play <file> --chapters <json>`), with the list of what the AI did and anything it flagged. Take their changes, re-cut, and when they are happy record it: `mark review --note \"<their words>\"`."},-  {"name": "publish", "done": ["publish.json"], "do": "With the human's OK: push the film, poster, captions and a video.json manifest (captions and chapters inlined) to the project's wiki page and put `::adom-video{src=...}` under the title; check the live player. For YouTube, suggest setting up adom-google (a YouTube-only account) if it is not there, upload unlisted unless they ask for public, with the chapters, the starting prompt, the cost line and a 'Built with' list of the Adom tools in the description. `mark publish --note \"<links>\"`."},-  {"name": "cleanup", "done": ["cleanup.json"], "do": "Once the human has approved the final film, run `clean` to see what is left on every machine (raw clips, temp recordings, staging copies, render scratch), then `clean --yes` to remove it. Keep the finished film, captions, chapters and the edit plan. Tell the human how much space was freed."}+  {+   "name": "intake",+   "done": [+    "state.json"+   ],+   "do": "Ask the human once, in plain words: do they want a narrated video of this build, ready to review when they are back? Tell them recording takes over the screen of the machine it records, and suggest a second machine on their Adom Mesh so their own stays free. Run `disk` on the recording machine and share the estimate. Then `init` (with `--release <board-release.json>` when the board flow wrote one, `--target <machine>` for the recording machine)."+  },+  {+   "name": "plan",+   "done": [+    "plan.json"+   ],+   "do": "Write plan.json: the moments worth a short clip for THIS build (the prompt being typed, each AI Flow step landing, parts search, a pup window fetching a part, new wiki part pages, Fields views, the silkscreen landing, the finished board in 3D, the wiki page). Highlights only, 5 to 30 s each, never continuous recording, and leave AI Flow's own full-length step recording off. If the build is already finished, plan the showcase shots instead and say the build footage does not exist."+  },+  {+   "name": "capture",+   "done": [+    "clips/*.mp4"+   ],+   "do": "Record the planned moments as they happen: `clip start --name <moment> --hwnd <window>` then `clip stop`. Before each take look at the screen: Hydrogen full screen with the taskbar showing, other apps floating at about 90 percent, no dialogs, toasts, mail, chat or other personal windows. Motion in every clip. `track` every file you create on any machine so `clean` can find it later."+  },+  {+   "name": "walkthrough",+   "done": [+    "walkthrough/steps.json"+   ],+   "do": "Build the 3D walkthrough in the Adom 3D viewer (assets/walkthrough-director.js is ready-made; docs/walkthrough.md explains it): the case or enclosure part by part when the project has one, then the board's major parts on the top and the underside. Highlight each part, label it with its reference and part number, and narrate what it does. Write walkthrough/steps.json (one entry per part: nodes, label, text) and record the take in real time."+  },+  {+   "name": "script",+   "done": [+    "script.json"+   ],+   "do": "Write script.json: one narration line per scene. Open on the real starting prompt. Name the Adom tool that did each step while it is on screen (AI Flow, the KiCad, Fusion or Altium bridge, parts search, the wiki, Fields, webviews, pup), about one mention per 20 to 30 s, and add a few 'ask your AI to ...' lines so the viewer learns something. Include the parts story (unique parts, where they came from, cost to build one and each at 100) and any custom mechanical work. Close with one line that it was built in Adom Hydrogen and where the files are. Then `script script.json` for feedback."+  },+  {+   "name": "cut",+   "done": [+    "out/*.mp4"+   ],+   "do": "Narrate with adom-tts, fit each clip to its line (1x to 2x, never dead air, never a flashed shot), add teal circles where the eye should go, and write captions (.vtt, .srt) and chapters as sidecar files, never burned in. Render 1080p one section at a time. Make a contact sheet and look at every scene before calling it a draft."+  },+  {+   "name": "voice",+   "done": [+    "voice.json"+   ],+   "do": "Offer the human two ways to finish the sound, and let them pick. (1) Keep the AI voiceover and go on. (2) Narrate it themselves: play them a private working copy of the draft with the captions showing, as a teleprompter, and let them record their own voice while they watch, in their own words (they need not read it exactly). Then rebuild the film without the on-screen captions, fit each scene to what they actually said, and write new captions and chapters from their recording (check part names and numbers against the script). The teleprompter copy is never published. `mark voice --note \"ai voiceover\"` or `mark voice --note \"own narration\"`."+  },+  {+   "name": "privacy",+   "done": [+    "privacy.json"+   ],+   "do": "Run `scan <script, captions, description files>` and look through the contact sheet for anything personal on screen: email addresses, names, phone numbers, keys, file paths with a user name, other people's windows. Prefer dropping or reframing a clip to blurring it. Tell the human what you found and what you did about it."+  },+  {+   "name": "review",+   "done": [+    "review.json"+   ],+   "do": "Show the draft to the human in the Adom video player with chapters (`adom-video play <file> --chapters <json>`), with the list of what the AI did and anything it flagged. Then show a pre-flight sheet of everything the public will see: title, description (chapters, the starting prompt, the cost line, the Built-with list), thumbnail, tags, channel and privacy. Take their changes, re-cut, and when they are happy record it: `mark review --note \"<their words>\"`."+  },+  {+   "name": "publish",+   "done": [+    "publish.json"+   ],+   "do": "With the human's OK: push the film, poster, captions and a video.json manifest (captions and chapters inlined) to the project's wiki page and put `::adom-video{src=...}` under the title; check the live player. For YouTube, suggest setting up adom-google (a YouTube-only account) if it is not there, then upload as PRIVATE first so they can watch it on YouTube itself (compression, thumbnail, captions, chapter markers); switch it to unlisted or public only when they say so, and delete it if they do not like it. `mark publish --note \"<links>\"`."+  },+  {+   "name": "cleanup",+   "done": [+    "cleanup.json"+   ],+   "do": "Once the human has approved the final film, run `clean` to see what is left on every machine (raw clips, temp recordings, staging copies, render scratch), then `clean --yes` to remove it. Keep the finished film, captions, chapters and the edit plan. Tell the human how much space was freed."+  }  ]-}+}\ No newline at end of file