> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/broker/policy-management/claims-tracking.md).
# Claims tracking
In the event of an incident, we are committed to full transparency at every stage of the claim. That's why you can access all the information on your past and ongoing claims (reference, filing date, status, etc.) from the **Claims** tab of your Broker Space.
The possible statuses are:
* `Filed`: Stoïk's assistance service has been informed that a suspected or confirmed cyberattack is underway;
* `Open`: the cyberattack is confirmed, Stoïk's incident response team is mobilized;
* `Rejected`: the cyberattack is not confirmed or does not fall within the scope of Stoïk's incident response team;
* `Investigation`: Stoïk's incident response team is investigating the claim;
* `Remediation`: Stoïk's incident response team is remediating the information system;
* `Legal`: the incident is closed from a technical standpoint, but actions are still ongoing on the legal side (damage assessment, expert appointment, etc.);
* `Closed`: the incident is fully closed.
---
# 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.stoik.io/broker/policy-management/claims-tracking.md?ask=&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.
