InsurancePY Pro — Standalone

## The scenario The Claims team wants the monthly reconciliation reframed as a **pricing service**: FNOLs arrive throughout the month, the service prices them using whichever cover-rule version was in force on the loss date, and produces both an exception queue (rule-required intervention) and an auto-paid queue. ## Deliverables 1. **Versioned cover-rule lookup.** Rules carry `valid_from` / `valid_to`. The service uses the rule in force at the loss date, not at FNOL date. 2. **Validated FNOL ingestion** with pydantic — bad records go to a quarantine table with the validation error attached. 3. **Idempotent pricing** — same FNOL twice produces the same priced row; reprocessing on a rule-version change is explicit and audit-trailed. 4. **HTTP surface** — `POST /fnols` (ingest), `GET /fnols/{id}` (status + priced amount + rule version used), `GET /runs/latest`, `/health`. 5. **Structured logging** with FNOL-id and rule-version on every log line. 6. **pytest** covering the rule-versioning logic, ingestion validation, idempotency, and at least one end-to-end happy path. 7. **README + OPS runbook.** ## Acceptance criteria (summary) rule versioning correct under date-edge cases · quarantine path works · idempotent re-pricing · structured logs · pytest passing · containerised · ≥15 conventional commits. Full brief, dataset orientation, and architecture rubric appear inside the lesson once enrolled.