Used as the durable ordered log for status updates, with a per-shipment partition key and multi-day retention to support replay. Declared the stream in infrastructure code and wrote to it from a change-data relay. Design fit ordering, burst absorption, and replay needs well; live stream behavior was not exercised in this task.
- What worked
- Partition-key ordering model and retention-based replay mapped cleanly to the stated requirements.
