Event 2 — West Coast
The Technology Perspective
Canvas SF · 50 Moraga Ave, Presidio, San Francisco · Hybrid-enabled · ~6.5 hours · California prehospital CE via EMSA #127 · Free admission, pay-what-you-feel optional · Emergency vehicle apparatus display outdoors
Audience
Anyone who works on or touches a system that uses AI.
This event is not limited to public safety AI specialists. If you build AI, research its safety properties, govern its deployment, write its product requirements, or work on any system where AI plays a role — this event is for you. First responders are the featured voices. The technology community is here to listen, learn, and leave with an operational reality they cannot get from a benchmark or a demo.
Program Schedule
West Coast — Full Schedule
The apparatus display opens 45 minutes before the program — emergency vehicles outdoors at the Presidio, with ATEC and EMERGENZ staff leading structured practitioner walkthroughs in rotating groups. The apparatus is available again during break and lunch. CE hours documented via Zoom Workplace and issued via Certifier.io.
Emergency vehicles outdoors at the Presidio — ambulance and fire apparatus, provided in-kind by a Bay Area department as a community outreach activity. ATEC and EMERGENZ staff conduct structured walkthroughs for groups of 8–10, explaining the operational environment that AI tools will be deployed into: the ambulance interior, the communication equipment, the documentation workflow, the conditions under which decisions get made. This is the most direct exposure the technology community can get to the operational reality — before the first session starts.
Delivered by an ATEC-connected East Coast practitioner — the continuity link between both events. Opens with what the East Coast found: the specific operational realities, concerns, and unanswered questions that emerged from public safety practitioners across all disciplines. Moves through a structured tour of what working as a first responder actually looks like — decisions made in seconds, documentation happening in moving vehicles, supervision happening through radio — and what that means for any AI system intended for deployment in this environment. Closes by framing the day's central question: what would responsible deployment actually require?
A panel of operational voices — multiple disciplines, multiple roles — speaking directly to the technology community about what would actually be useful, what constraints make most demos non-deployable in their current form, and what the field would pay for if it existed and was validated. Moderated to keep conversation constructive and forward-looking rather than a critique session. Intended to give builders, researchers, and product leaders direct access to a practitioner brief they cannot get from market research.
Second round of apparatus walkthroughs for those who didn't catch the pre-session. Informal engagement between practitioners and technologists encouraged — this is where unscripted conversations happen.
The technical and governance panel. Opens with where AI safety research currently sits and where public safety intersects — and notably where it doesn't. Examines what responsible deployment would require from an AI safety research and governance perspective: pre-deployment validation protocols, automation bias mitigation, adversarial robustness for voice synthesis and spoofed calls, shadow use governance frameworks. Intended to give practitioners access to the research community and give researchers access to a deployment context they have not fully engaged with.
Three parallel tracks. Mixed composition by design — each group ideally includes both practitioners and technologists, but the format adapts to whatever ratio the room presents on the day. Facilitators adjust framing based on actual composition: if a group is heavily technical, the session becomes a practitioner-briefed design challenge; if it is heavily practitioner, it becomes a structured gap and requirements documentation session. No minimum headcount per breakout. All formats produce the same output: 5–7 documented findings or design constraints.
Skew Accommodation Plan
If strongly tech-heavy: The facilitator frames the session as a practitioner-briefed design brief. The one or two practitioners in the room are treated as primary expert voices; technologists work from their input to document constraints, requirements, and failure scenarios. Output is a design brief format: what this tool would need to be to actually deploy.
If strongly practitioner-heavy: The facilitator frames the session as an operational gap documentation exercise. What does AI need to be able to do in this domain? What constraints does the environment impose? What validation would you need to see before trusting a recommendation? Output is a requirements and concerns format: what we'd need before saying yes.
If balanced: Standard mixed format — practitioner voices brief, technologist voices respond and probe, facilitator documents tensions and agreements. All three converge to the same 5–7 findings output.
Rapporteurs from each breakout present findings — approximately 12 minutes each. The moderator synthesizes across West Coast presentations and holds them against the East Coast Summary of Findings, identifying confirmations, contradictions, and new material specific to the technology community perspective. No live voting or intensive audience participation is required. Attendees contribute via a structured web form (QR code distributed at session open and emailed post-event) with 48-hour collection window.
Post-Event Capture Mechanism
A brief web form (3–5 questions, mobile-optimized) is distributed via QR code at session close and emailed to all registered attendees. Questions are designed to capture: (1) key themes the respondent felt were underrepresented; (2) specific findings they most want communicated to the other community; (3) anything they heard that changed how they think about the problem. Responses collected within 48 hours and incorporated into the West Coast Summary before publication. Staff burden is minimal — no real-time transcription or voting infrastructure required.
The moderator presents a draft framework of the West Coast's key themes alongside the East Coast summary. The draft is shared with all registered attendees via email post-event alongside the 48-hour web form. Final West Coast Summary and cross-series synthesis document are published within 5–7 days under EMERGENZ's name as educational and research documents — not advocacy. The series synthesis gives the AI safety research and policy community a structured, practitioner-grounded account of where the field stands and what responsible deployment would require.
