> For the complete documentation index, see [llms.txt](https://docs.goldfinch.finance/goldfinch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goldfinch.finance/goldfinch/goldfinch-v1/borrower-mechanics/structure-and-legal-considerations.md).

# Structure and Legal Considerations

{% hint style="warning" %}
**Goldfinch provides tools to help participants interact with the protocol, but it is your responsibility to stay compliant with all legal, regulatory, and tax laws for your relevant jurisdiction(s). All protocol participants are strongly encouraged to consult with their own legal and tax counsel.**&#x20;
{% endhint %}

Below are some important structure and legal considerations to take into account as you look to get started on the Goldfinch Protocol, including cashing in and out of the ecosystem, Investor KYC/AML requirements, key mechanics to consider including Debt Facility Mechanics and Transaction Documentation, Senior Pool participation for Borrowers, and Backer transferability of debt positions.


---

# 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.goldfinch.finance/goldfinch/goldfinch-v1/borrower-mechanics/structure-and-legal-considerations.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.
