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

# Cycle 5

### New Features

* Added ability to download filing attachments in addition to the original filing.
* Added "Filing Type" filter to the search filter options allowing search results to be filtered based on Rate, Rule, or Form filings.
* Created "List More" option in the filing browser to expand results per page.

### Improvements

* Reduced decimal precision where unnecessary throughout the app.
* Modified the product updates section of filings to use company code instead of product name.
* Improved the UI gauge on the single carrier view
* Added tool tips throughout the app to better describe functionality and labels

### Bug Fixes

* INS-163 - fixed an issue with the filing browser displaying rate impact in the indicated change column.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.insuraviews.com/releases/release-notes/cycle-5.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
