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

# Cycle 8

This release contains a beta release of our Intelligence Briefs feature,  improvements to our Objection Response feature, and other improvements and bug fixes.

### New Feature

**Intelligence Briefs**

* Generate your own market intelligence briefs based on any combination of filings you select.  Once your criteria is selected, a custom brief is generated that summarizes a Market Analysis, Strategic Insights and provides references to the various filings included in the criteria used to generate the report.

<figure><img src="https://3627719227-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRDo7Wvsasy8Pyg5liYJv%2Fuploads%2FNgINbjj0A1EITkPIdJdV%2Fimage.png?alt=media&amp;token=4a76dbdb-4af8-4b21-9943-2f1372b8dc25" alt=""><figcaption><p>Brief Builder Criteria</p></figcaption></figure>

<figure><img src="https://3627719227-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRDo7Wvsasy8Pyg5liYJv%2Fuploads%2FxQhEnPC75rL6OR14DEqy%2Fimage.png?alt=media&amp;token=ce50f604-a85a-422b-9e14-4a7ba4f48d17" alt=""><figcaption><p>Brief Builder Output</p></figcaption></figure>

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

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

### Improvements

**Objection Response**

* Improved the response time for the Objection Response feature.

### Bug Fixes

* **INS-196:** Fixed an issue that prevented some filings from being displayed from certain carriers.


---

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