> For the complete documentation index, see [llms.txt](https://docs.openconstitution.us/global-statutes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openconstitution.us/global-statutes/open-bank/open-bank-protocols/insurance.md).

# Insurance

This page describes the Insurance Protocol of Open Treasury.

Open Treasury funds are held in different forms of Financial Instruments.

Few e.g are Current accounts in a bank, or a Central bank, Trading accounts, Loan accounts with ESGs, Impact Funds, Institutional Funds.

{% hint style="info" %}
These instruments are extended both a deposit insurance and if any loans against the Treasury Assets have been availed, then a Credit Secure Coverage is adhered to, before any Fund appropriations, allocation actions are initiated in connection with the Open Treasury.
{% endhint %}

Note: Insurance Protocols listed here are independent of the Insurances accorded to Foundation citizens e.g Professional Indemnity, Health Insurance coverage. 

Here, Insurance protocols mean surety protocols to cover the Fund appropriation actions.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openconstitution.us/global-statutes/open-bank/open-bank-protocols/insurance.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 `build a script that syncs our docs to a CMS` 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.