LogisticsPY Pro — Standalone

## The scenario Operations wants the SLA report turned into a **weekly close**: scanner events arrive throughout the week (some late, some corrected), the service computes outcome category at the moment a consignment becomes decidable, and produces a customer-compensation payable file when the week closes. ## Deliverables 1. **Event ingestion** — `POST /attempts` accepts new scanner events. Late events that change a consignment's outcome trigger a recompute. 2. **Decidability** — a consignment is "decided" when either (a) DELIVERED, or (b) the breach window has passed and no further attempts can change the outcome category. 3. **Weekly close** — `POST /closes/{week}` finalises that week, snapshots the SLA breakdown, and produces `compensation_payable.csv`. Re-running a close is allowed (audit-trailed) until 28 days after week-end. 4. **Structured logs** with consignment-id and route-id on every line. 5. **HTTP surface** — `GET /consignments/{id}`, `GET /closes/{week}`, `GET /runs/latest`, `/health`. 6. **pytest** covering late-event recompute, decidability boundaries, weekly close idempotency. 7. **README + OPS runbook** including "a customer is disputing their compensation, where do I look?" ## Acceptance criteria (summary) late-arriving events handled · decidability rule correct under edge cases · idempotent weekly close · structured logs · pytest passing · containerised · ≥15 conventional commits. Full brief, dataset orientation, and architecture rubric appear inside the lesson once enrolled.