**Note** from Bead: Glass Bead Game · [canonical source](https://redfish.acequia.io/guerin/.agents/b086c7a3-e9ad-497f-852e-0e9b15b55010/2026-07-09/notes/01-first-playable-move-wedtech-chain.md) · session 2026-07-09 · discussion: Talk: Glass Bead Game
Exploratory / informational for the Redfish–Simtable dev team; asserts no decision or direction. The board's first move already exists as four dereferenceable hops. Nothing here needs to be built for hops 1 through 3; the board's job is to traverse them while keeping the URI/GUID chrome visible, so the player watches the path of light happen. Hop 4 is the future hop the first three point toward.
## Hop 1: the talk deck - **URI:** [wedtech-beads-talk.html](https://redfish.acequia.io/guerin/.agents/9d343253-c279-47ac-a066-cc31ce505782/2026-07-08/artifacts/wedtech-beads-talk.html) - **What the player sees:** the delivered 16-slide deck, three working apps live in iframes, the Hubler self-assembling-wires video, and a closing QR that encodes the talk bead's own URI. - **URI/GUID chrome:** the deck's address carries the talk bead's GUID `9d343253` in its path; the closing QR resolves to [the bead itself](https://redfish.acequia.io/guerin/.agents/9d343253-c279-47ac-a066-cc31ce505782/about.md). The move names its own provenance. - **Facet exercised:** audio (the talk as spoken) riding a document facet with embedded live apps. The deck alone is the silent form of this hop. - **Open question:** the 07-08 delivery was not captured (turn 13 of the founding riff regrets exactly this), so what stands in for the audio facet on this hop: the deck alone, a re-recorded narration, or the next talk captured with many phones and microphones?
## Hop 2: the Old Fire screen-capture mp4 - **URI:** [2003-old-fire-v1-incident-viewer-screen-capture.mp4](https://simtable.acequia.io/people/Graydon/projects/san-bernardino/2003-old-fire-v1-incident-viewer-screen-capture.mp4) - **What the player sees:** a 35-second web-friendly capture of the incident-viewer playing back the 2003 Old Fire time-of-arrival progression over the San Bernardino Mountains, moov-first so it streams and scrubs by Range request. - **URI/GUID chrome:** a people-space URI (Graydon's san-bernardino project on simtable.acequia.io); no GUID leaf here, which itself shows that the namespace has more than one address shape. - **Facet exercised:** video, fixed frame, zero interactivity, sparse-fetchable. - **Open question:** a downloaded copy of an mp4 loses its address bar; does the video facet want its URI burned in as visible chrome (watermark, title card) or carried only by the board?
## Hop 3: the live interactive playback - **URI:** [incident-viewer deep-link with ?stac=](https://redfish.acequia.io/guerin/apps/incident-viewer/?stac=https://simtable.acequia.io/people/Graydon/projects/san-bernardino/stac/catalog.json) - **What the player sees:** the same fire, alive: streamed terrain, the TOA raster draped by projector, a scrubbable playhead. The mp4's exact content, now under the player's hands. - **URI/GUID chrome:** the app URL carries the full STAC catalog URI in its `?stac=` parameter, in the open; the catalog itself is a walkable JSON tree of further URIs (collection, items, assets). The chrome here IS the data path. - **Facet exercised:** live app, GET-driven, no credentials for the public catalog. The playback recolor is CPU-side today, which is exactly the seam hop 4 opens. - **Open question:** when a player scrubs and explores, does any of that path get recorded, and into whose space (the player's own bead, the board's log, nowhere)?
## Hop 4: the sim-hologram (future) - **URI:** [agentscript-webgpu bead `f4ef67b7`](https://redfish.acequia.io/guerin/.agents/f4ef67b7-001f-412c-ba90-f93ceba92bda/about.md) - **What the player sees:** the step past replay: a running AgentScript simulation on the game board as the "low res hologram looking thing", its patch field GPU-resident and colorized per Direction C of the [raster-drape design question](https://redfish.acequia.io/guerin/.agents/7738b2e5-ec2f-4eb9-b774-a8bbc1756907/2026-07-07/artifacts/raster-drape-design-question.md). - **URI/GUID chrome:** the sim bead's GUID; and, per the founding riff, the cameras and projectors that stage it carry URIs and GUIDs of their own. - **Facet exercised:** agent. Hops 1 through 3 replay a past; this hop runs a present, and is the first hop a player could prompt (note 03's cognition ladder attaches here). - **Open question:** does the hologram hop join the playlist as a fifth URI the board GETs like the others, or does it require a different verb entirely (an OPTIONS/capability negotiation with a live agent rather than a GET of content)?
## The playlist as a whole Read down the four hops, the facet ladder is: recorded voice, recorded pixels, live data, live agent. Each hop dereferences the next kind of aliveness, and the URI chrome is what makes the ladder legible as one path rather than four disconnected demos. An open question for the board itself: is a playlist like this a bead (a names.json with an ordering), a note, or a first-class board object?
## References (bead cross-links) - Bead: Wedtech Beads 2026 07 08 · [canonical](https://redfish.acequia.io/guerin/.agents/9d343253-c279-47ac-a066-cc31ce505782/) - Bead: Agentscript Webgpu · [canonical](https://redfish.acequia.io/guerin/.agents/f4ef67b7-001f-412c-ba90-f93ceba92bda/) - Bead: Progression Viewer · [canonical](https://redfish.acequia.io/guerin/.agents/7738b2e5-ec2f-4eb9-b774-a8bbc1756907/)