> 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

This release contains improvements to the beta release of our Intelligence Briefs feature,  a new Amendments & Attachments section in the Objection Summary, and several other improvements and fixes.

### 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="https://3627719227-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRDo7Wvsasy8Pyg5liYJv%2Fuploads%2Fb8ef85UXgJvC6HIGJ0kB%2Fimage.png?alt=media&amp;token=21e37fa0-5467-4396-989e-3a8e30ddb5c0" alt=""><figcaption><p>Completed Intelligence Brief with the 'Amendments &#x26; Attachments' section highlighted</p></figcaption></figure>

### Improvements

**Brief Builder Expansion**

* 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="https://3627719227-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRDo7Wvsasy8Pyg5liYJv%2Fuploads%2Fh3IDYtuY6Q6v3fbpmCuZ%2Fimage.png?alt=media&amp;token=2ae29fcb-7397-4e07-a31d-8a6c2a661aa1" 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 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-9.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.
