Create a draft handoff for a fictional Missouri hail briefing. You will learn how the eight capabilities contribute and which missing evidence prevents publication. This is a paper exercise: it sends no messages and computes no ranks.
Read the capability overview and keep the report release contract available. Use a scratch document. Every identifier and time below is fictional; no named county is being assessed by this exercise.
-
In Storm Forecast, record
forecast_issuance: null. A report can begin without a stored outlook. Write “preparation context unavailable,” not “no storm forecast” or “all clear.” -
In Storm Alert, record
exercise-warning-1, revision1, issued at18:00 UTC (exercise). A user opens a notification before associated MRMS evidence exists. Record evidence as pending and retain the warning context. -
In Storm Radar, add a fictional observation at
18:02 UTC, received at18:05 UTC. Record the three-minute receipt lag. Leave its native source, units, and quality checks unresolved rather than inventing verified data. -
In Storm Map, select that frame in history mode within regional analysis
exercise-window-1. A later frame arrives; record one buffered update without changing the selection. Leave physical-storm identity null: the selected window might contain multiple storms. -
In Storm Impact, record Missouri →
exercise-county-1→exercise-work-area-1as a proposed path. Boundary releases and the approved weather-exposure rule are missing, so no ranking or starting marker is ready. Parcel data is also absent, but is not the blocker for this area briefing. -
In Storm Report, create draft
exercise-report-1. Record the source, geography, rule, reviewer, and authorized-recipient gaps. Keep publication and delivery pending. A warning or a radar pixel alone cannot turn this draft into an instruction to canvass during dangerous weather. -
In Storm History, save this exercise draft's reference as a proposed entry. Its evidence is unresolved: a saved ID alone does not preserve a frame. In Storm Replay, leave playback unavailable until a verified manifest and frames exist. Record that replay must never send the fictional notification or publish the draft. Add the missing retention and time-mode decisions to the same review task.
kind: storm-report-exercise
status: fictional-draft
forecast_issuance: null
warning_id: exercise-warning-1
warning_revision: 1
analysis_scope_id: exercise-window-1
physical_storm_id: null
selected_observation_time: "18:02 UTC (exercise)"
received_at: "18:05 UTC (exercise)"
view_mode: history
buffered_updates: 1
proposed_path: [Missouri, exercise-county-1, exercise-work-area-1]
boundary_release: null
ranking_mode: weather-exposure-priority
ranking_snapshot: null
ranking_state: unavailable
parcel_release: null
replacement_probability: null
report_id: exercise-report-1
published_revision: null
history_state: evidence-unresolved
replay_state: unavailable
replay_mode: evidence-timeline
delivery_state: not-requested
field_assignment: on-hold
next_action: Resolve source, geometry, rule, reviewer, and recipient gaps.Compare your draft with this artifact. A teammate should identify why it cannot be published, explain why missing parcels do not block an area report, and find the pilot acceptance criteria. The exercise is complete when those distinctions are clear; the product pilot still needs working generation, review, delivery, and mobile use with real evidence.
For runnable MRMS behavior, use Inspect a local benchmark. For implementation, use Review a product change with the report's acceptance criteria.