💡 Weather-Aware Market Day Intelligence

[github-actions[bot]]

Summary

A three-role weather coordination layer that replaces fragmented phone/email/social-media weather communication with structured market status decisions. Managers declare weather-related market status (open/delayed/cancelled) from a dashboard showing forecast data and historical attendance patterns. Vendors receive early warnings. Customers get proactive push notifications when a followed market's status changes due to weather.

Market Signal

Weather is the #1 cause of farmers market disruptions. USDA market rules require weather policies. Currently handled via phone trees, email, and social media — fragmented and unreliable. No competitor (Seen Markets, Marketspread, Farmish) provides a structured weather-to-market-status decision flow across all three roles. Seen Markets offers basic manager notifications but lacks weather integration and customer-facing alerts.

User Signal

The PRD identifies "failed trips" as the core problem and "confidence-first positioning" as the competitive strategy. Weather-related cancellations without timely notification are the most common failed-trip scenario. Manager persona (Maria) currently handles disruptions via manual coordination. The architecture already plans push notifications (FCM) and manager broadcast capability (FR19, FR10e).

Technical Opportunity

Weather API integration (OpenWeatherMap/WeatherAPI free tiers) feeds a manager dashboard. Manager confirms market status → domain event published through internal/events/ → Firebase Realtime propagates to vendor/customer views → FCM push notifications to followers. Existing architecture (FR10e: market cancellation flow, FR19: market-level updates, FR29-30: notification infrastructure) provides 80% of the plumbing. New work: weather API adapter, manager weather dashboard component, weather-triggered notification templates.

Assessment

Dimension	Score	Rationale
Feasibility	high	Weather APIs are mature and free-tier. 80% of notification infrastructure already planned. Simple manager workflow.
Impact	high	Directly prevents the #1 cause of failed trips — the core problem this app solves. Serves all 3 roles.
Urgency	high	Needed from day 1 of market operations. Weather disruptions happen weekly during storm season.

Adversarial Review

Strongest objection: Why build weather features into a market app when users already have weather apps? This adds complexity without core value.

Rebuttal: The value isn't the forecast — it's the MARKET-SPECIFIC STATUS DECISION communicated across all three roles through one channel. Whether a market opens, delays, or cancels is a human judgment call by the manager that currently requires phone trees and social media. This structures that decision and delivers it instantly to everyone who needs it. The weather data supplements manager judgment; it doesn't replace it.

Suggested Next Step

Create a quick spec for the manager weather status declaration workflow, including the weather API integration pattern, notification templates, and the customer-facing "market status changed" push notification flow.