**Note** from Bead: Incident Host Mvp · [canonical source](https://redfish.acequia.io/guerin/.agents/8dda0afd-2c9e-4374-8571-1a77ebf30516/2026-07-07/notes/00-mvp-frame-host-and-foragers.md) · session 2026-07-07 · discussion: Talk: Incident Host Mvp
*Working concept extracted from the 2026-07-07 session; verbatim source in [the chat log](https://redfish.acequia.io/guerin/.agents/8dda0afd-2c9e-4374-8571-1a77ebf30516/2026-07-07/chats/2026-07-07-incident-host-mvp-start.md).*
## The gesture 1. **Anyone becomes a Host.** No account with us, no central operator. A person declares an incident and thereby opens a space for it (a group, a catalog root, a set of tokens). This is local-first: the customer is the operator. 2. **The Host invites others to forage.** Invitations carry attenuated capability (scoped tokens), following the existing chain-token and [token-minting pattern](https://redfish.acequia.io/guerin/.agents/c915581b-4179-409e-9e13-085531521fd9/about.md). Foragers bring back imagery, maps, and fire simulations. 3. **The group monitors and reconstructs the incident.** Live monitoring (camera grid, live feeds) and after-the-fact reconstruction (calibrated imagery in the Incident Viewer, TOA rasters, plumes) are two faces of the same accumulating catalog.
## What integrates The MVP composes existing one-page apps rather than rebuilding them; the full parts list with roles is [app-catalog.md](https://redfish.acequia.io/guerin/.agents/8dda0afd-2c9e-4374-8571-1a77ebf30516/2026-07-07/artifacts/app-catalog.md). The seams: - **STAC as spine.** Everything foraged lands as assets in an incident catalog; every viewer reads from it. ("Asset catalogs" in product language; STAC is the implementation term.) - **Acequia groups as membrane.** Join-a-group is already the shared gesture across GeoCamera, CameraMap, and BrowserDAV. - **Foraging as bookmarklet-delivered capability.** The forage collector works on any page; EGP Missions shows the pattern specialized to one third-party site (EGP). New sources mean new specializations of the same collector move. - **Calibration as quality gate.** through-the-lens and image-pose turn found imagery into reconstruction-grade cameras. - **Simulation in both directions.** TOA reconstruction from perimeters (what happened) and Rothermel or AgentScript-in-taos (what might happen, plumes included).
## Open questions (for a sketch round, per house UX practice) - What is the minimal Host gesture: a URL you mint? a BrowserDAV directory you share? a group name you pick? - Where does the incident catalog physically live for a Host with no server (BrowserDAV on their laptop? a parciante node they trust?), and how does it survive their laptop sleeping? - What does the invitation look like to a stranger on a phone (GeoCamera link with a token baked in?) - Is the MVP shell a new one-page app, or Incident Viewer plus a Host panel? - How much of monitoring (camera grid) belongs in the same surface as reconstruction (viewer)? These should be posed as rendered sketches with answerable questions, Debbie-style, before any shell gets built.
## References (bead cross-links) - Bead: Slack Integration · [canonical](https://redfish.acequia.io/guerin/.agents/c915581b-4179-409e-9e13-085531521fd9/)