get_filing_dossier

ai.serff/ca-rate-filings · Verify this server

**Use this to see the full REGULATORY POSITION of a filing in one call — current CDI status, who is reviewing it, the entire objection history, filer contacts, and lineage to predecessor filings. NOT the tool if the question is about rating mechanics, base rates, factor tables, or actuarial numerics.** For those, chain into `get_filing_summary` (actuarial narrative), `search_actuarial_embeds` (numerics), or `search_filing_embeds` (paragraph-level body). Right questions this answers in one shot: - "Where does FARM-134879410 stand at CDI right now?" — status, pending/closed, live objections, who's on it - "Give me the full paper trail on this filing so I can audit how it progressed" - "Was this objected to? Approved? Withdrawn? Who reviewed it?" — the `derived` block answers at-a-glance - "Show me the objection thread + carrier lineage + references for this SERFF" — all sections inline Composes `get_filing_summary`, `get_filing_correspondence`, `get_filing_references`, and `get_filing_lineage` in parallel for one SERFF id and returns the union along with a derived at-a-glance block. Each sub-fetch is independent — a missing summary or errored lineage still leaves the rest intact (each section carries a per-section `error` field on failure). Wrong surface for: - Search — start with `search_filings` / `search_summary_embeds` / `search_correspondence_embeds` to find the SERFF, then dossier from there - Caseload / aggregate views — use `list_email_workload` for "which reviewer is on the most Pending filings" Returns `{ serff, meta, derived, summary, correspondence, references, lineage }`. The `derived` block carries `{has_summary, correspondence_file_count, correspondence_chunk_count, has_objections, cdi_reviewer_emails, reference_count, lineage_depth}` — enough for a client to render a status card without walking every sub-payload.