> 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-4.md).

# Cycle 4

### New Features

* Added Filing Type as filter to the search page.

### Improvements

* Added specific filing detail to DOI reviewer summaries.
* Optimized grouping in the left navigation pane for better usability.
* Enhanced the Rating Factors section for improved viewing.
* Improved the login page to better align with the Insuraviews brand identity.
* Account profile photos are now displayed directly within the app.
* Links are dynamically generated wherever SERFF tracking numbers appear throughout the app.
* Combined the Filing and Forms browser to eliminate redundancy; use the Filing Type filter to differentiate between Rate, Rule, and Form filings.

### Bug Fixes

* Improved performance of Objections Response feature.
* Fixed an issue that caused incorrect results to appear when filtering within the search results page.
* Fixed an issue in the search results page that caused multiple results to be displayed per filing.
* Fixed an issue with labels in the multi-carrier view.
* Fixed formatting issue with objection summaries.


---

# 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-4.md?ask=<question>&goal=<user_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.
