You have 35 minutes to complete seven stages for the Ember Events telemetry platform. The clock runs across the full design: requirements, volume, ingestion, replay behavior, data model, aggregation, and release. Work with the stated numbers and keep the completed board between stages. Each later stage requires something new.
The platform receives sensor readings continuously. Its users need provisional results within 30 seconds and a way to rebuild the last 14 days after a calibration change. Five-minute network delays are normal, so a fresh result can still need correction. The assessment rewards a complete, checkable path over an elaborate diagram. Preserve event identity, keep additive totals behind averages, and state how readers move to a rebuilt version. If the timer expires, the mock records unfinished work; the starting design still needs each checked requirement.