# Adom Native Browser Extension (nbe) - demo video script

**Audience & goal.** The primary viewer is a **Chrome Web Store / Edge Add-ons reviewer** deciding
whether to approve an extension that requests `debugger` + `<all_urls>` + `cookies` + `nativeMessaging`.
Every clip must read as: *a legitimate AI development-environment company, with real electrical-engineering
workflows, using exactly the browser capabilities those workflows require.* Tone: confident, professional,
matter-of-fact. No hype, no "hacking past" anything — just an AI doing an engineer's work in the engineer's
own browser, with the on-screen reason each capability is needed.

**Format.** Six ~30 s clips, each recorded **through the extension's own WGC recorder**
(`nbrowser_record_start {method:"wgc"}`) against a Chrome window driving the live app — proving the
recording feature on the same surface it demos. In-page captions via `nbrowser_caption`. Per-clip TTS via
`adom-tts say` (house voice). Muxed, reviewed in `video-post storyboard`, concatenated, hero'd, uploaded.

**House voice:** `en-US-AndrewMultilingualNeural`. **Per-clip target:** 28–32 s, narration ±15%.

**Recurring caption chip (bottom-left, every clip):** `Adom · AI dev environment · driving real Chrome`
**Recurring capability tag (bottom-right, per clip):** names the Chrome capability being shown + why.

---

## Clip 0 — Cold open / who we are (≈12 s, optional lead-in)
- **Caption:** "Adom — an AI development environment for electronics."
- **Narration:** "Adom is an AI development environment for the electronics industry. Engineers build and
  test web-based instruments and design tools all day — and our extension is the AI's hands inside their
  own browser. Here's what that looks like."
- **Driver:** title card / the hero, slow fade into Clip 1.

## Clip 1 — Web oscilloscope (the lead) (≈30 s)
- **Capability tag:** "chrome.debugger — drive & read a live web app"
- **Captions (sequence):**
  1. "A real web-based oscilloscope, running in Chrome."
  2. "The AI sets the timebase…"  3. "…drags the trigger to CH1-rising…"  4. "…and reads the measurements back."
- **Narration:** "This is a browser-based oscilloscope. Watch the assistant bring up the instrument the way
  an engineer would — it sets the timebase, drags the trigger to channel one rising, and reads the live
  measurements straight off the screen. It does this through Chrome's DevTools protocol — the same debugger
  capability a developer uses to inspect and drive a web app while building it."
- **Driver:** open scope (proxy URL) → `nbrowser` set timebase, set trigger, read VPP/FREQ → caption each beat.

## Clip 2 — Chip-fetcher: build your CAD library (≈30 s)
- **Capability tag:** "cookies + <all_urls> — your real signed-in tools"
- **Captions:** 1. "Sourcing CAD for a whole BOM." 2. "The AI drives the dashboard…" 3. "…symbol, footprint,
  3D model, datasheet — per part." 4. "Your library, assembled."
- **Narration:** "Designing a board means sourcing CAD for every part — symbol, footprint, 3D model, and
  datasheet. The assistant drives our chip-fetcher dashboard in the engineer's own signed-in browser, working
  down the parts list and pulling each component's full bundle into the library. That's why the extension uses
  your real session and cookies — so the tools you're already logged into just work."
- **Driver:** open chip-fetcher dashboard → scroll the 71-part grid → open one chip's detail (3D + symbol +
  footprint) → caption.

## Clip 3 — Adom Symbol: schematic symbols, live (≈30 s)
- **Capability tag:** "scripting + debugger — generate & preview"
- **Captions:** 1. "A schematic symbol, generated from a datasheet." 2. "Pins grouped by function." 3. "The 3D
  package, right on the symbol." 4. "Previewed before it lands in your library."
- **Narration:** "Here the assistant generates a schematic symbol for a converter chip — reading the datasheet
  pinout, grouping the pins by function, and embedding the 3D package right on the symbol — then previews it
  live in the browser so the engineer can check it before it goes into the library."
- **Driver:** open adom-symbol live → show the ADS1262 symbol → toggle a layout option / hover a pin → caption.

## Clip 4 — Web EDA / CAD: try a change, see it routed (≈30 s)
- **Capability tag:** "debugger — drive a live design tool"
- **Captions:** 1. "A schematic, edited in the browser." 2. "Re-run the autorouter…" 3. "…inspect the nets." 4.
  "Design iteration, hands-free."
- **Narration:** "This is a browser-based EDA tool. The assistant edits the schematic, re-runs the autorouter,
  and inspects the resulting nets — turning 'try this change and tell me what breaks' into something it just
  does, in the same session where the engineer's libraries already live."
- **Driver:** open tscircuit viewer → schematic tab → trigger re-run → switch to PCB/3D → caption.

## Clip 5 — 3D board review (≈30 s)
- **Capability tag:** "debugger — inspect a live 3D view"
- **Captions:** 1. "Review the actual board in 3D." 2. "Frame the camera…" 3. "…hide a part to see the traces."
  4. "A PCB review, in a browser tab."
- **Narration:** "Before a board ships, the engineer wants to look at the real layout. The assistant opens the
  3D board viewer, frames the camera, and hides a component to see the traces underneath — making a PCB review
  a conversation in a browser tab instead of a context-switch into a separate desktop tool."
- **Driver:** open tscircuit 3D → orbit camera → hide a component → caption.

## Clip 6 — Adom Chipsmith: does the part fit? (≈30 s)
- **Capability tag:** "debugger — validate before fab"
- **Captions:** 1. "Does the 3D model match the footprint?" 2. "Drop the chip on its pads." 3. "Check the fit
  visually." 4. "Catch it before the PCB does."
- **Narration:** "Finally — before a part goes onto a board, its 3D model and footprint have to line up. The
  assistant drives our chip-on-pads validator to seat the chip and check the fit visually, catching a
  mis-seated or wrong-variant model before it ever reaches the PCB. Real engineering, in your real browser —
  which is exactly why Adom asks for full browser control."
- **Driver:** open chipsmith → frame the chip-on-pads → caption.

---

## Production checklist (per the demo-recording skill)
- [ ] Script approved by John ← **we are here**
- [ ] Per-clip record via `nbrowser_record_start {method:"wgc"}` (background window — non-disruptive)
- [ ] In-page captions via `nbrowser_caption` during each take
- [ ] Per-clip TTS via `adom-tts say` (house voice), muxed to `<clip>-narrated.webm`
- [ ] `video-post storyboard` review with John (mandatory gate)
- [ ] Concat → final.webm (`-g 30 -keyint_min 30` for wiki seek) → hero frame
- [ ] Upload final + hero to the wiki page; embed in README/showcase