**Bead document** from Bead: Incident Viewer Taos Engine App · [canonical source](https://redfish.acequia.io/guerin/.agents/cbf8b027-e80c-4b9f-8eb3-91d40af072d5/decisions.md) · discussion: Talk: Incident Viewer Taos Engine App
Open decisions are Stephen's headgates; resolved ones move to the log with their date.
## Open - **D6 — santafe.live deploy target: root vs subpath.** The viewer currently deploys to the `santafe.live/` **root**, which co-tenants a pre-existing "set space time" app (recovered to `santafe.live/set-space-time/` by #set-time-space after our `index.html` overwrote it — note 15, dock 2026-06-16). Move the viewer to a subpath (e.g. `santafe.live/incident-viewer/`) so the two apps stop colliding at `/`, or keep root + a no-root-cleanup guard? Until decided: **no root-cleanup on santafe.live.** - **D4 — alertLive FMV projection shape.** Project FMV clips into alertLive events as N keyframe imageMeta entries (pose sampled from KLV) or one entry at start pose? (AL-1, note 06.) - **D5 — replace hand-written viewer-3d/incidents.json with the STAC projection?** (Fixes 3 wrong Palisades start times; original kept as history either way.) - **D2 — fmv-pose extension schema.** Stub now (`fmv:telemetry` asset pointer); full 6-DOF pose-stream schema is #catalog deliverable 2. - **D3 — Sandy cameras provenance.** If no archived 2026-05 alertwildfire state exists, accept current camera poses (cameras are fixed) with a provenance note?
## Resolved - **2026-06-12 — Palisades ToA: DEFERRED** (Stephen: "don't worry about palisades toa for now"). No progressionMaker run, no derivation. The viewer's progression layer is catalog-driven, so whenever a Palisades progression Item appears it lights up with zero code changes. - **2026-06-12 — D1: STAC home of record = `https://simtable.acequia.io/incidents/stac/`** (Stephen). Synced + verified (160 files, anon GET 200). Bead `artifacts/stac/` remains the workshop original / release source. - **2026-06-12 — D3 moot:** both camera snapshots are incident-time (WP-C finding) — no provenance caveat needed. - **2026-06-11 — Method:** adopt devops file-state machine + epic-step for this bead's build work (Stephen: "use this going forward"). - **2026-06-11 — Catalog substrate:** STAC (decided upstream in #catalog/#incident-cataloging; carried here). - **2026-06-11 — Build location:** STAC built in bead `artifacts/`, OFFERED for binding — never written into `incidents/**` directly (cataloging-incident rule).