> For the complete documentation index, see [llms.txt](https://labark.gitbook.io/labark-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://labark.gitbook.io/labark-docs/readme.md).

# Welcome

Welcome to the **LabArk** operation manual.

This system helps researchers manage the full lifecycle of an animal study — registering protocols, setting up experiments, creating studies, and recording experimental data — all in one place, with built-in support for IACUC compliance and the 3Rs principle.

#### How this manual is organized

The four chapters under **Operation Method** follow the natural workflow of using the system:

<table><thead><tr><th width="92.3359375">Step</th><th>Chapter</th><th>What you'll do</th></tr></thead><tbody><tr><td>1</td><td>Registration / Login</td><td>Create your account and sign in</td></tr><tr><td>2</td><td>Experiment Setup</td><td>Configure protocols and parameters</td></tr><tr><td>3</td><td>Create a Study</td><td>Define animals, groups, and timeline</td></tr><tr><td>4</td><td>Experimental Data Entry</td><td>Record observations and results</td></tr></tbody></table>

#### How to use this manual

* New to the system? Read the chapters in order — each one builds on the previous step.
* Looking for a specific task? Use the sidebar to jump straight to the chapter you need.

#### Need help?

* **Technical support :** <team@darev.io>

***

*Version 1.0 · Last updated: May 2026*


---

# 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://labark.gitbook.io/labark-docs/readme.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 `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.