**Chat log** from Bead: Image Pose Uxui · [canonical source](https://redfish.acequia.io/guerin/.agents/74c30681-2b0c-48b2-b2a8-9e21190a4926/2026-06-16/chats/2026-06-16-image-pose-uxui.md) · session 2026-06-16 · discussion: Talk: Image Pose Uxui *Verbatim chat log: immutable provenance. The bead's copy is ground truth; wiki edits here are a fork, never the record.*
Verbatim user prompts; assistant turns summarized with pointers. Ground truth for this bead.
## Pre-bead context - IDE had `santafe.live/set-space-time/imageMeta/0a0ce0ad62d7b6f8.json` open (a Santa Fe history image meta record) — the live 2D catalog-manager app this build extends.
## Turn 1 — hatch + spec (verbatim) > start-bead image-pose-uxui > > let's use santafe.live/set-time-place/ as an example app for setting time and place. for now we can > store pose and image as an artifact in your bead as downloads is not available. > > let's use taos-engine with dem and google photorealistic 3d tiles. create a byok area for google key on > startup. or use sample key. we will later track the usage. > > mount-beads that have to do with michael naimark's viewfinder tech talk where he shows the paul > debevec's calibration of the berkeley campanile. 3d geopoint of a the georectified 3d model is overlayed > and appears to translate to the photo. but implementation behind the scenes is the camera is moving. > > the second model to a uv in image might include rotation and translation or lens intrinsics. these can > all be related to soft constraints. > > there's a writeup in a bead about this paper and name of the space in the 90s > > update plan **Assistant:** Read the bead protocol, the live `set-space-time` app (index.html/index.js, the `imageMeta/` + `imagePose/` schema), `#pose-ux-ui` (the design parent, which already frames the campanile approach), and `#ants-in-taos` (working taos-engine + DEM + Google 3D Tiles render pattern). Searched the `.agents/` tree for the Naimark/90s-space writeup — not found locally (flagged as open Q). Asked 3 scoping questions; Stephen chose: **standalone `calibrate-3d.html`**, **direct Google Maps Tiles API BYOK**, **pose output as bead artifact only**. Scaffolded this bead (about/README/bind-startup + directive note + this log). Build plan presented for approval next.
## Decisions (2026-06-16) - Surface: standalone new page `santafe.live/set-space-time/calibrate-3d.html`. - 3D tiles: direct Google Maps Tiles API, BYOK key in startup panel (localStorage) / sample key; usage tracked later. - Pose output: bead artifact only (santafe.live `imagePose/` untouched for now).
## Turn 2 — devops + orchestration (verbatim, arrived mid-scaffold) > use devops .git discipline making the app. also give me a dashboard as you orchestrate agents working > on this. mount relevant beads for devops workflow **Assistant:** Surveyed the devops/orchestration ecology: `#shape-up-studio` (`86bbc504`, the program orchestrator — this build = its P3 Calibration-&-pose pitch; team roles incl. devops + testing), `#agentify-bead` (`d9dfa5e4`, the ratified git-and-beads discipline: ecology-owned source in-bead `repo/`, vendor in `src/`, gc before sync), `#agents-dashboard` (`45761f53`, the `.agents/dashboard.html` + running/ticks/log telemetry), `#home-hosting` (`7049c694`, deploy posture). Mounted all four (names.json + about.md). Adds to the plan: (1) git repo at `<bead>/repo/` with branch-per-step commits; (2) a bead-local orchestration `dashboard.html` (modeled on `.agents/dashboard.html` + the ai-team project.json pattern) fed by `running/` + `log.md` + a per-step `WORK-QUEUE.md`; (3) multi-agent build under the shape-up role charters. Updated plan presented for go-ahead.