**Note** from Bead: Wedtech Beads 2026 07 08 · [canonical source](https://redfish.acequia.io/guerin/.agents/9d343253-c279-47ac-a066-cc31ce505782/2026-07-08/notes/12-deck-build.md) · session 2026-07-08 · discussion: Talk: Wedtech Beads 2026 07 08
The talk deck is [artifacts/wedtech-beads-talk.html](https://redfish.acequia.io/guerin/.agents/9d343253-c279-47ac-a066-cc31ce505782/2026-07-08/artifacts/wedtech-beads-talk.html), 16 slides, in the format captured in [11-talk-page-format.md](https://redfish.acequia.io/guerin/.agents/9d343253-c279-47ac-a066-cc31ce505782/2026-07-08/notes/11-talk-page-format.md). This note records the concepts and choices that shaped it.
## The public carve-out (the deck eats the origins-and-scopes dogfood) The deck and its embedded slides live inside this bead, and the bead is authenticated-only. Rather than move the deck out or open the whole bead, `2026-07-08/artifacts/` alone carries a `{"read":"anonymous","recursive":true}` sidecar plus a README: the deliverables are a public leaf, the working notes and chat logs stay tokened. This is exactly the nearest-wins split the origins-and-scopes slide teaches, applied to the talk about it.
## Slide inventory (v0.2) 1. Title. 2. Sketches lead the work (Redfish UX practice). 3. **Hubler, Self-Assembling Wires video** (4:36), inserted at Stephen's direction. Source is the already-local copy served at [redfish.acequia.io/videos/self-assembling-wires.mp4](https://redfish.acequia.io/videos/self-assembling-wires.mp4) (same origin as the deck, already public via the /videos/ sidecar; a 1.5 MB clip exists as fallback). Original: [youtube.com/watch?v=PeHWqr9dz3c](https://www.youtube.com/watch?v=PeHWqr9dz3c); transcript and metadata live in bead 96597c32's 2026-05-16 artifacts. The slide uses native `controls` (YouTube-style scrub/play/volume) rather than the reference deck's muted-loop autoplay, so Stephen can scrub live; entering the slide attempts play, leaving pauses. 4. Facets sketch (iframe). 5. One URI, three faces. 6. PUT beat, then 7. **Leila's LinkedIn post** (embedded via LinkedIn's `/embed/feed/update/` URL; the footer pop-out opens the [original post](https://www.linkedin.com/feed/update/urn:li:activity:7480438480649605120/) via a `data-pop` override), then 8. hydrants live. 9. Origins and scopes, then 10. the origins slide (iframe). 11. Conduction beat, then 12. Old Fire viewer live (`?stac=` the San Bernardino catalog). 13. Memory beat, then 14. anysurface simulator live. 15. More web than web components. 16. Pitches carry context. 17. Close: "beads are my AI interface to the team" with a **QR code** for this bead's URI.
## QR as the closing gesture The close invites the audience to GET the bead on their phones: the talk's own provenance is the takeaway. Implementation: `qrcode` (Python) at error-correction M, rendered **dark-on-light** (`#0a0a0f` modules on `#e8e4d8`) because inverted QR codes fail many phone scanners; the light card sits deliberately on the dark deck. File: [artifacts/qr-bead-9d343253.png](https://redfish.acequia.io/guerin/.agents/9d343253-c279-47ac-a066-cc31ce505782/2026-07-08/artifacts/qr-bead-9d343253.png).
## Mechanics carried from the reference, plus one improvement Lazy `data-src` iframes (load on slide entry, `about:blank` on exit), footer pop-out and copy-URL for the current demo (extended to cover the video slide), keyboard/touch nav. Improvement over the reference: slide numbers are **auto-filled by JS from slide order**, so inserting a slide (as happened with the video) never breaks the numbering by hand.
## Open questions - [ ] Full 4:36 video or the 1.5 MB clip on stage (venue bandwidth)? - [ ] Should the QR also appear small on the title slide so early arrivals can walk the bead during setup? - [ ] LinkedIn embeds only render for public posts and can be blocked by the venue network or an ad blocker; test the embed slide on the venue box, and the pop-out to the original post is the fallback.