> For the complete documentation index, see [llms.txt](https://docs.insuraviews.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.insuraviews.com/releases/release-notes/cycle-39.md). # Cycle 39 ### New Features **Search: One Box, Two Ways to Find Answers** * Type once, then search filings for a filterable, exportable list or ask the AI Assistant for an explained answer with sources. * Accessible through the "Search or Ask AI" button in the top left

**Notifications: Significant Filings** * Flag filings with rate changes above or below the industry average, or outside a range you set.

New 'Significant Filings' option in Global Notification Settings

**Notifications: AI Summaries in Your Digest** * Each notification email now opens with a short summary of what happened across your filings, with a brief summary on each significant filing so you can decide what’s worth opening.

Notification Email with the new "What's New" description of the filings in the email

**Search: Simpler Recency Controls** * Narrow results to the dates you need with the date range filter and sort by effective or submitted date.

Demonstration of setting Date Range filter, and it remaining when changing Date Range type

### **Improvements** **DOI Reviewer Profile - Referenced Filings** * Filings referenced in the DOI Reviewer Profile now align with the filtered scope of the page, and the filings included are guaranteed to have objections listed

### **Bug Fixes** **INS-3033:** Fixed an issue where the Product History tab would show the incorrect filing type for all filings --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.insuraviews.com/releases/release-notes/cycle-39.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.