> For the complete documentation index, see [llms.txt](https://docs.enzyme.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enzyme.finance/enzyme-blue-protocol/github-repo.md).

# GitHub repo

All audited, deployed contracts are located in the `current` branch of our public repo: <https://github.com/enzymefinance/protocol>

Unaudited code is located in the `next` branch of our private repo (must request access).

## Contracts

All contracts used for both production and testing are located in `contracts/`

`mocks/` - Mock contracts used only by tests

`persistent/` - Production contracts that will not be changed after their first deployment. These are contracts available to be used across multiple releases, e.g., the overarching structure that facilitates fund migration from an old release to the current release.

`release/` - Production contracts whose lifetime does not extend beyond this release.

`test/` - Other contracts used only by tests

## Tests

All tests are in the `tests/` directory.


---

# 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.enzyme.finance/enzyme-blue-protocol/github-repo.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.
