💡 Emergency colony triage wizard with voice-guided crisis intervention protocols

[github-actions[bot]]

Summary

When a beekeeper discovers a colony emergency (massive mite load, queenlessness, starvation, pesticide exposure), the app activates a voice-guided triage protocol that walks them through assessment, stabilization, and recovery steps in real-time. Uses current colony state, weather, and seasonal context to prioritize interventions. Critically different from post-mortem analysis (Discussion #444) — this is about saving the colony NOW.

Market Signal

Record 55.6% U.S. colony losses in 2024-2025 — the highest ever recorded (Auburn University / Apiary Inspectors of America survey, June 2026). Most losses stem from manageable causes (Varroa, starvation, queenlessness) caught too late. No beekeeping app offers real-time crisis intervention guidance. USDA ARS and Bee Informed Partnership data confirm most losses are preventable with timely action. The 2025-2026 survey shows losses moderating to 39.9%, but this remains historically elevated.

User Signal

Broodly's newbie persona (Hannah) journey highlights decision paralysis at high-stakes moments as the core problem. The PRD's recovery-oriented emotional design ("calm, supportive, never punitive") maps perfectly to crisis intervention. Zero-tap voice guidance is essential during emergencies when beekeepers' hands are occupied with the hive. The existing inspection flow architecture provides the foundation for triage protocols.

Technical Opportunity

Builds directly on the existing voice-guided inspection flow architecture. Triage protocols are branching decision trees — same pattern as guided inspection prompts. Colony state from recent inspections provides context for triage recommendations. TTS announcements guide the beekeeper through each step. No ML required for MVP — purely protocol-driven with voice interface. Synergizes with Discussion #444 (colony loss post-mortem) — triage data feeds into post-mortem analysis if the colony doesn't survive, creating a longitudinal learning loop.

Assessment

Dimension	Score	Rationale
Feasibility	high	Reuses existing voice-guided inspection flow; no ML needed; primarily content/protocol development
Impact	high	Directly addresses the #1 cause of colony loss (late intervention); unique in the competitive landscape
Urgency	high	Record colony losses demand immediate decision-support tools; fall treatment window approaching

Adversarial Review

Strongest objection: Experienced beekeepers already know basic interventions. Triage protocols could be seen as "obvious" information that doesn't warrant app integration.

Rebuttal: Newbie beekeepers DON'T know interventions — that's precisely why 55.6% of colonies are dying. The value isn't the information itself but the contextualized, prioritized, step-by-step guidance during a stressful moment when decision paralysis is worst. A queen loss in July requires completely different responses than in October, and the app has the seasonal/regional context to differentiate. The voice-guided format is critical because during an emergency, the beekeeper's hands are IN the hive — they can't tap a phone.

Suggested Next Step

Design triage protocol decision trees for the 5 most common colony emergencies (high Varroa load, queenlessness, starvation, pesticide exposure, disease) with season-aware branching. Validate protocols with experienced beekeepers and university extension service educators before implementation.