> For the complete documentation index, see [llms.txt](https://cryonics.gitbook.io/cryonics-project/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cryonics.gitbook.io/cryonics-project/about-cryonics-project/introduction.md).
# Introduction
The aim of our organization is to protect human life. Therefore, a patient in the process of dying must be intervened at the earliest legally possible stage. Since body cryopreservation is not a current medical procedure, the legal declaration of death must be made by a physician or health institution other than our team in order to start the protocol. **Cryopreservation protocols** will be carried out under ideal conditions in each case due to delays in the legal declaration of death, the place of death, logistical and financial problems. **Cryopreservation protocols** should intervene in patients with the lowest possible level of ischemic damage. On the other hand, for many cryonics members (people who have **CRYS** in their possession and have applied), it is more reasonable to be preserved in the worst case than not to be preserved at all.
In order for a cryonics case to be accepted, there are certain prerequisites that must be met before the case can be accepted, including the patient's informed consent, a **cryonics contract**, anatomical donation, and financial arrangements. Last minute applications from non-cryonics members are generally not accepted due to the risk of ethical, legal, or financial problems. The waiting team will be able to accept the case and start patient stabilization only if the patient is a member of the organization and has made financial arrangements, or if the patient who is not a member of the organization has the unanimous consent of three organization officials.
---
# 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://cryonics.gitbook.io/cryonics-project/about-cryonics-project/introduction.md?ask=&goal=
```
`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.