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

# Cycle 9

### New Feature

Objections Summary - Amendments & Attachments

Added a new section to the Objections Summary section of filings to display detailed information about the attachments and revisions to a filing throughout the objection review process.

<figure><img src="/files/tWBWfMeI4uwOYQ1Oo79i" alt=""><figcaption></figcaption></figure>

### Improvements

* Expanded the Brief Builder from 20 to 200 filings per brief.
* Created an "Objection Brief" format specifically focused on objections and responses.<br>

  <figure><img src="/files/yIatIZ1MRd5pMzoLpvr0" alt=""><figcaption><p>Objection Brief</p></figcaption></figure>

{% hint style="info" %}
This feature is still in development.

The Brief Builder is limited to **200 filings**. The results will be sorted by **premium volume** and the top 200 filings will be used to generate the report.
{% endhint %}


---

# 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-9.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.