weatherreporter/docs/roadmap/future.md

Future Roadmap

This roadmap contains project work that is not implemented. Current behavior is documented outside docs/roadmap/.

Deferred: Automatic Storm Monitoring

Manual Storm Report generation is implemented through weatherreporter generate storm --start TIME --end TIME. Automatic storm-event evaluation remains deferred.

Proposed direction:

1. detect candidate events deterministically from alerts, forecast discussion, weather story context when available, hourly thresholds, and material forecast changes;
2. evaluate candidates through Scriptorium or another narrow evaluator adapter;
3. persist storm lifecycle state;
4. generate or update Storm Reports only when a meaningful event is present;
5. suppress ordinary low-impact thunder or rain chances.

Possible lifecycle states:

• none
• monitoring
• active_report
• escalated
• deescalating
• resolved

Acceptance criteria before implementation:

• scheduled reports and manual Storm Reports remain stable;
• candidate detection has fixture coverage;
• evaluator failures are inspectable and do not create noisy report output;
• manual Storm Report generation remains available.

Deferred: Alternate Runtime Integrations

These ideas are not current behavior:

• native LLM client inside weatherreporter;
• database-backed state;
• public HTTP API;
• multi-location selection;
• daemon mode;
• multi-user authorization;
• plugin system.

Each item needs its own design note before implementation. Non-roadmap docs must not describe these as available behavior.